Instrument GitLab.com New Subscription Purchase flow (SaaS) - /billing page viewed path
Information to track
Customers can enter the purchase flow on .com
from:
- Billing page
- Pricing page
Event | Description | Location |
---|---|---|
Pageview | Records pageviews for each page in the purchasing flow |
*/billings/ */subscriptions/new? |
Action | Clicks upgrade on Premium | */billings/ |
Action | Clicks upgrade on Ultimate | */billings/ |
Action | Changes plan type | */subscriptions/new? |
Action | Selects or Changes group | */subscriptions/new? |
Action | Changes number of users | */subscriptions/new? |
Action | Clicks Continue to billing
|
*/subscriptions/new? |
Any errors that can be triggered when Continue to billing is clicked should be logged |
backend event? | |
Action | Clicks edit on subscription details module | */subscriptions/new? |
Action | Clicks Continue to payment
|
*/subscriptions/new? |
Any errors that can be triggered when Continue to payment is clicked should be logged |
backend event? | |
Action | Clicks edit on billing address module | */subscriptions/new? |
Action | Clicks edit on payment method | */subscriptions/new? |
Action | Clicks on link next to Tax | */subscriptions/new? |
Action | Clicks confirm purchase | */subscriptions/new? |
Purchase success | backend event | |
Purchase failure along with error reason | backend event |
Questions
-
✔ Can we / should we track if an error is displayed at any point to the customer? For example, once they Continue to Billing, try to click on Continue to Payment, but they cannot proceed because an error is shown? (added to the table above)
Structured Snowplow events to track
- Taxonomy guide
- category - rely on
default
values from Rails, else if it isn't defined on the event use[customers:saas:checkout]
for thedefault
items.
Category | Action | Label | Property | value | helpful context - notes / URL location in app |
---|---|---|---|---|---|
groups:billings:index | render | billing | */billings/ (in screenshots as # 1) | ||
groups:billings:index | click_button | upgrade | premium |
*/billings/ (in screenshots as # 2 Already Implemented | |
groups:billings:index | click_button | upgrade | ultimate |
*/billings/ (in screenshots as # 3) Already Implemented | |
default |
render | saas_checkout | */subscriptions/new? (in screenshots as # 4) | ||
default |
click_button | update_plan_type | [plan type] | */subscriptions/new? (in screenshots as # 5) | |
default |
click_button | update_group | [new group namespace_ID] | */subscriptions/new? (in screenshots as # 6) | |
default |
click_button | update_seat_count | [seat count] | */subscriptions/new? (in screenshots as # 7) | |
default |
click_button | continue_billing | pass value of Success or [failure reason] |
*/subscriptions/new? (in screenshots as # 8) | |
default |
click_button | select_country | [country_value] | */subscriptions/new? (in screenshots as # 9) | |
default |
click_button | state | [state_value] | */subscriptions/new? (in screenshots as # 10) | |
default |
click_button | saas_checkout_postal_code | Postal code value] | */subscriptions/new? (in screenshots as # 11) | |
default |
click_button | continue_payment | pass value of Success or [failure reason] |
*/subscriptions/new? (in screenshots as # 12) | |
default |
click_button | review_order | pass value of Success or [failure reason] |
*/subscriptions/new? (in screenshots as # 13) | |
default |
click_button | tax_link | page URL = */subscriptions/new? the target URL of this link is https://about.gitlab.com/handbook/tax/#indirect-taxes-management (in screenshots as # 14) | ||
default |
click_button | confirm_purchase | pass value of Success: subscription or [failure reason] |
*/subscriptions/new? (in screenshots as # 15) | |
default |
click_button | edit |
subscription_detials or billing_address or payment_method
|
*/subscriptions/new? (in screenshots as # 16) |
User experience reference point
Snowplow event tracking checklist
-
Engineering complete work and deploy changes to GitLab SaaS -
Verify the new Snowplow events are listed in the Snowplow Event Exploration dashboard -
Create chart(s) to track your event(s) in the relevant dashboard -
Use the Chart Snowplow Actions SQL snippet to quickly visualize usage. See example
-
Edited by Gayle Doud