[Engineering] Pipeline Zero State MVC - copy changes experiment
Overview
The test is a simple copy change to see if not introducing users to GitLab specific concepts at this point will increate first usage of pipelines.
Context:
GitLab CI/CD can automatically build, test, and deploy your code. Let GitLab take care of time consuming tasks, so you can spend more time creating.
Button: Get started with CI/CD
Experiment
Test: 50% traffic, counting user_id's that spin up at least 1 pipeline (successful or not)
Instrumentation
{
category: Growth::Activation::Experiment::PipelineZeroState,
action: 'visited' | 'documentation_clicked' ,
label: hashed<user_id>,
value: namespace_id where the pipeline is ran
}
-- Amount of users per experiment group that saw the experiment (unique)
select count(*) from experiment_users JOIN experiments ON (experiment_id = experiments.id) WHERE experiments.name = 'pipelines_empty_state' GROUP BY group_type;
-- Amount of users per experiment group that created a pipeline (unique)
select count(*) from experiment_users JOIN experiments ON (experiment_id = experiments.id) WHERE experiments.name = 'pipelines_empty_state' AND converted_at IS NOT NULL GROUP BY group_type;
Rollout
- Tracking issue: gitlab-org/growth/team-tasks#289 (closed)
Related to
See Epic and related [UX] issues, gitlab-org/growth/team-tasks#246 (closed)