Data Review: Subscription Platform - Add new events for churn intervention #19945
Description
1) What questions will you answer with this data?
The Subscription Platform team is introducing a new feature that focuses on reducing subscriber churn by offering timely discounts at two key moments, namely during cancellation of an existing subscription and prompting customers to stay subscribed after already cancelling their subscription.
The new Glean events, and related nimbus_user_id metrics, introduced as part of this data review will be used to determine the usage and effectiveness of the features.
2) Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
Yes this is required to meet product requirements. It will be used to measure the effectiveness of the churn reduction efforts.
3) What alternative methods did you consider to answer these questions? Why were they not sufficient?
Engineering already has usage insights into how often the churn reduction feature will be used, via StatsD metrics. However these are not always accurate, do not provide additional querying parameters such as "utm" params, and does not integrate with Nimbus for experimentation.
4) Can current instrumentation answer these questions?
No.
5) List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories found on the Mozilla wiki.
Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.
| Measurement Description | Data Collection Category | Tracking Bug # | Measurement Name |
|---|---|---|---|
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | cancel_interstitial.offer_redeemed#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | cancel_route.churn_content#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | cancel_route.error#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | cancel_route.interstitial_offer#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | cancel_route.standard#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | churn.cancel_redeemed#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | churn.stay_redeemed#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | stay_route.churn_content#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | stay_route.error#nimbus_user_id |
| Nimbus user ID | interaction | https://mozilla-hub.atlassian.net/browse/PAY-3436 | stay_route.standard#nimbus_user_id |
6) Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.
(This collection is Glean so is documented in the Glean Dictionary. | [explain])
7) How long will this data be collected?
This collection will be collected permanently.
subplat-team@mozilla.com will be responsible for the permanent collections.
8) What populations will you measure?
All channels, countries, and locales. No filters.
9) If this data collection is default on, what is the opt-out mechanism for users?
These collections are Glean. The opt-out can be found in the product's preferences.
10) Please provide a general description of how you will analyze this data.
The new Glean events, and related nimbus_user_id metrics, introduced as part of this data review will be used to determine the usage and effectiveness of the churn reduction features.
11) Where do you intend to share the results of your analysis?
This data will be used for creation of Looker dashboards.
12) Is there a third-party tool (i.e. not Glean or not Telemetry) that you are proposing to use for this data collection? If so:
No.
┆Issue is synchronized with this Jira Task