Skip to content

Trial onboarding issues experiment

Alper Akgun requested to merge 276704-engineering-mvc-trial-onboarding into master

What does this MR do?

Trial onboarding learning project growth team experiment for new trial signups

  • Redirects net new users coming from about.gitlab.com to a newly created trial onboarding project

Related to issue #276704 (closed)

Rollout Issue

Testing on GDK

  • Entry point to get the "experiment group" experience http://localhost:3000//-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=free-trial
  • You need a local CustomersDot or otherwise, trials won't apply and an error message will come up.

On your GDK rails console enable the flags:

Feature.enable_percentage_of_time(:onboarding_issues_experiment_percentage, 100)
Feature.enable_percentage_of_time(:trial_onboarding_issues_experiment_percentage, 100)

Screenshots

trial-onboarding-2020-12-15_23.21.56

Get started Onboarding issues
screenshot-2020-12-16-11-38-35 screenshot-2020-12-16-11-39-26

Clarification about trial registration flow and regular registration flow both running several growth experiments.

1. Trial Registration flow (Trial onboarding experiment)

When we start in the trial registration flow, and we're chosen to the trial_onboarding_issues experiment group (e.g. 50% chance in an experiment rollout) we shall have in_trial_onboarding_flow=true. in this case params[:trial] or trial doesn't exist.

2. Regular Signup flow (trial_during_signup experiment) !45147 (merged)

  • When we use the signup fow https://gitlab.com/users/sign_up
  • But the experiment group for trial_during_signup offers a trial form inside during the registration process - but the user can select a trial or not using toggle below which sets params[:trial] or trial to true

screenshot-2020-12-16-21-47-47

This MR must ensure that the two flows are separate. We shouldn't have an extra trial form (trial_during_signup), during trial registration flow.

Creating a projec template

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • Security reports checked/validated by a reviewer from the AppSec team
Edited by Alper Akgun

Merge request reports

Loading