In-app message to link to the homepage redesign research survey

Request for recruting customers via In App Messaging

Ensuring a positive user experience for our users is the most important factor to consider when deploying messaging in our product. With that goal in mind, we have put in place the following procedures to ensure that in-app messaging does not result in any negative user sentiment.

What is the purpose of your proposed messaging?

Invite users to fill in a short survey about homepage (dashboard) redesign. The preview of the survey can be seen in Qualtrics

How will you define success?

Getting around 100 responses to the survey.

What type of users do you want to target? (be as specific as you can)

All GitLab users because a major part of the redesign will be trying to customise the content for different roles. Their role is also what we ask about in the survey.

How many impressions you are targeting for your desired user type(s)?

Hard to estimate. 10-100k.

What pages do you plan to deploy your message on?

The GitLab home page (dashboard). The one that opens after clicking on the GitLab logo in the main nav.

What is the average total of unique users accessing those pages per day?

Don't know.

What is the average unique users matching your desired user type(s) accessing those pages per day?

Don't know.

What type of message is needed:

  • Link (copy & CTA)

Link: https://gitlab.fra1.qualtrics.com/jfe/form/SV_cTJSk3VvUU0T0pv?i={{user_id}}

Copy: How can we make your GitLab home page more useful? Let us know in a short survey.

The "Let us know" is the linked part in the copy.

What is the desired content of your message?

How can we make your GitLab home page more useful? Let us know in a short survey.

UX research issue: https://gitlab.com/gitlab-org/ux-research/-/issues/1049

General in-app messaging guidelines

  • Messages must be approved by VP of Product Management @adawar in order to run.
  • We run a maximum of 2 in-app messages at any given time in order to limit the number of messages a user sees in quick succession.
  • Messages run for the shortest amount of time possible.
  • Messages are limited to a single page on the site unless there is a business reason to put it on multiple pages.

Transparency around decision making criteria

The goal will be weighed against in-app message fatigue. Will we have made significant progress on outcomes or will we have frustrated our users?

Edited by Jeff Crow