Add source targeting to in-app purchase funnels
Problem
As we continue to work to increase the rate at which users select to upgrade from feature discovery modules we want to target users differently, based on the different paths that are generating the most revenue and know their conversion rates.
Implementation approach
-
CustomersDot/Add source for the orders https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/3443 -
CustomersDot/Fetch source for the orders API -
Gitlab/Add source while calling CustomersDot API as a client -
Gitlab/Add source to in-app funnels -
Data/Add source to sisense https://gitlab.com/gitlab-data/analytics/-/merge_requests/5190
Solution
We should add parameter to in-app purchase links. The monitoring should mimic our trial URL monitoring whereby we could be something as simple as upgrade_source
and the value would be dependent on the location. The majority (if not all) of our in-app purchase CTAs direct the user from a "Upgrade Now" CTA to the billing page that corresponds with that namespace, the user then has to select "Upgrade" from that page at which point they enter the checkout experience.
In this solution, we'd want to be able to monitor:
- If a user came from a specific "Upgrade Now" CTA such as security nav, issue weights etc
- If a user clicks "Upgrade" on the namespace billing page and no "Upgrade Now" CTA source is found then we attribute the source to the namespace billing page.
We would store this URL parameter value at the moment of the click all the way through the checkout experience so we can understand how each source impacts the efficiency rate of checkout and we'd want to be able to tie a particular source to the IACV it generated.