Experiment Implementation: Experiment: Issues/Merge Request Empty States
Experiment Summary
We know that Issue and MR creation early in a new signup's experience increases the likelihood of them converting to paid.
To verify that, we will test alternative designs to the issues and MRs empty state pages (different layout and inclusion of something visual - in this case a video). Recently the groupfoundations team added Issues and Merge requests as 'Pinned' items on the navigation so we believe that more new signups will find where to get started with Issues and MRs.
Design
- MR empty state Figma
- Issues empty state Figma
- Note: For final
👍 on copy tag @aqualls
Control vs Candidate Experience
Control | Candidate |
---|---|
![]() |
![]() |
![]() |
![]() |
Rollout strategy
This experiment will be rolled out 50/50
Target Population
This experiment is explicitly "targeting" new Trial & Free Signups
- We want to ensure we are only targeting "new" signups so we are not interrupting workflows of existing customers
- Assuming the experiment is successful we will roll out this change to everyone on SaaS. For SM we will find an alternative solution to embedded videos.
Tracking Details
Tracking
We want to understand if someone is engaging with the empty state and its resources
We want to understand if someone is actioning the below on the free registration or trial registration
-
json schema used in
gitlab-experiment
tracking. - see event schema for a guide.
For the MRs empty state
sequence | activity | category | action | label |
---|---|---|---|---|
(Control/Candidate) User renders MR empty state page - question are we able to tell from where? ex. Nav, Learn GitLab, etc. | projects:merge_requests:index |
render_project_mrs_empty_list_page |
project_mrs_empty_list |
|
(Candidate) User clicks play on Merge Request video | - | - | - | |
(Control/Candidate) User clicks New Merge Request or Create a new merge request button |
projects:merge_requests:index |
click_new_mr_project_mrs_empty_list_page |
new_mr_project_mrs_empty_list |
|
(Candidate) User clicks Learn more about merge requests button |
projects:merge_requests:index |
click_learn_more_project_mrs_empty_list_page |
learn_more_project_mrs_empty_list |
For the Issues empty state
sequence | activity | category | action | label |
---|---|---|---|---|
(Control/Candidate) User renders Issues empty state page - question are we able to tell from where? ex. Nav, Learn GitLab, etc. | projects:issues:index |
render_project_issues_empty_list_page |
project_issues_empty_list |
|
(Candidate) User clicks play on Issue video | - | - | - | |
(Control/Candidate) User clicks on Learn more about issues | projects:issues:index |
click_learn_more_project_issues_empty_list_page |
learn_more_project_issues_empty_list |
|
(Control/Candidate) User clicks New Issue or Create new issue button |
projects:issues:index |
click_new_issue_project_issues_empty_list_page |
new_issue_project_issues_empty_list |
|
(Control/Candidate) User clicks on Email a new issue to this project or Email a new issue
|
projects:issues:index |
click_email_issue_project_issues_empty_list_page |
email_issue_project_issues_empty_list |
|
(Control/Candidate) User clicks on Import | projects:issues:index |
click_import_csv_project_issues_empty_list_page / click_import_jira_project_issues_empty_list_page
|
CSV or JIRA | |
(Control/Candidate) User clicks on JIRA integration | projects:issues:index |
click_jira_int_project_issues_empty_list_page |
jira_int_project_issues_empty_list |