Create Gainsight A-B test functionality for Journey Orchestrator
Problem Statement
We currently do not have an ability to A-B test the efficacy of JO series. In order for us to effectively test and prove out the value of journeys, we need to create a consistent framework for A-B testing to be performed.
From discussions with the CS Ops team, Gainsight does not have an out-of-the-box solution. Instead, we will create a company-level field that determines if an account is in which group (control group, open group, and any additional ones we may pursue).
Specifications
-
Create Company level dropdown option field to allow for multiple categories (ie., A
,B
,C,
D`...) -
Create a rule that puts each company into either A or B - Rule Name: Customer Programs A-B Cohort Designations
- Dropdown exists on
Company
Object and currently has two values. - Rule is based on the last character of the SFDC Account ID
- Control group is set to approximately 15% of Companies.
- If we use the first or last GSID character (A-Z + 0-9 = 36 characters), that means 5 characters (15% * 36 = 5)
- Dropdown exists on
-
Build rudimentary report to track Accounts by cohort - report -
@mharris3 to provide labels for each category (i.e., avoid "A" and "B" which is non-descriptive -
@mharris3 to update Onboarding and CI journeys with new filter logic -
Once project is complete, communicate to relevant parties -
Add to Gainsight changelog -
If applicable, update handbook documentation