ChartMogul allows you to "split" subscribers — that is, create separate, unique customer records in ChartMogul — when they’ve subscribed to more than one app. Companies that publish multiple apps and want to break down their subscription metrics — such as customer churn rate or customer lifetime value (LTV) — per app find this useful.
Let's have a closer look
First, it’s important to remember how ChartMogul works out-of-the-box. When a customer has multiple active subscriptions and cancels one of these subscriptions, ChartMogul classifies the lost MRR as contraction (rather than churn). Learn more about customer lifecycles in ChartMogul.
Here’s how the customer typically appears in ChartMogul, regardless of how many apps they’ve subscribed to. All of the customer's subscriptions appear under a single entry.
Now, imagine you're a company that publishes multiple apps — App A and App B — and you have a customer who has subscribed to both. The customer then decides to cancel their subscription to App A, and you would like ChartMogul to classify the cancellation as churn (instead of contraction).
ChartMogul makes it possible to do this with the Split subscribers per app setting. As mentioned above, when you enable this setting, ChartMogul creates separate, unique customer entries — one for each app the customer has subscribed to.
Here’s what this looks like:
Note: in order to create unique customer entries in ChartMogul, we append the AppAppleID to the customer external id.
Enabling the "split"
Splitting subscribers per app is not activated by default when you create a new App Store Connect data source, but enabling it is easy. Here’s how:
- Click the data platform icon in the left menu
- Select App Store Connect from the Data Source list and click the gear icon
- Under Data import options, check Split subscribers per app
- Click Re-sync Data to apply the changes
After changing the option, you need to re-sync your App Store Connect data source for the changes to take effect.
Note: Re-syncing your App Store Connect data source will cause any changes you’ve subsequently made to customers and their subscriptions inside ChartMogul — such as manually editing MRR, merging customers, adding custom attributes, or connecting subscriptions — to be lost.