_Note: this was all moved from [an issue](gitlab#273626) part way through development; as such, a lot of the commentary about it is in [that issue](gitlab#273626)._ ### Hypothesis We can increase the trial to paid conversion rate by highlighting to users what paid features they have limited-time access to via their trial. ### Experiment design A note about eligibility: Only users who have permission to upgrade a namespace will be considered eligible. All users in the control group and ineligible users in the experiment group will receive the same experience that they receive today where all features are enabled during the trial but no indication is given if a particular feature is part of their trial. | Control Experience | | ------ | |  | Eligible users in the experiment group will get the same access to trial features as any other trial user but we will highlight a popular premium feature within the trial by adding a visual indicator that indicates the feature is part of their time-limited trial. For this experiment, we will add this indicator to a popular premium feature, merge approval rules. The user will see the purple badge and when the user hovers over this badge it will cause the module displayed below to open. | Experiment Experience - Merge Approvals | | ------ | |  | ### UX #### Popover to upgrade  #### Popover to compare plan  #### [Design specs](https://www.figma.com/file/VlX4eyYeeQT9Ee75R3HnsU/Highlight-paid-features-during-active-trial?node-id=16%3A3217) ### Experiment goal & tracking The goal of this experiment is to see a statistically significant increase in the trial conversion rate from namespaces in the experiment vs the control. In order to track this experiment, we should place the trial namespace (note, not the individual user) in either the control or experiment groups, with the experiment success metric being converted to a paid account. Within the experiment cohort, we should also add event tracking on the popup module within the experiment utilizing the following events: * Event 1 * Event Name: Merge request badge displayed * Event action: user loads the create MR page in the experiment variant where the purple badge is present on the required approvals section * Event 2 * Event Name: Feature highlight displayed * Event action: user hovers on the purple icon causing the module to open * Event 3 * Event Name: Feature highlight upgrade click * Event action: user clicks on upgrade option within the module * Event 4 * Event Name: Feature highlight compare click * Event action: user clicks on compare option within the module We’ll be tracking these events using frontend event tracking, so each will be tracked as a single point in time. ### Experiment results TBD - Results section will be completed when the experiment results are determined