Split subscribers per app for App Store Connect

ChartMogul offers its users the option to split subscribers based on the number of apps they are subscribed to. This is useful in cases when you are a company that publishes multiple apps and want to report on your churn or LTV metrics per app instead of per subscriber. 

To better understand what we mean, here's a simple scenario: 

Imagine that a customer subscribes to Product A and Product B without being aware that both apps are published by the same company. 

If the customer cancels one of the subscriptions (Product A), in the reports, we would like this movement to be a churn. However, since the customer has another active subscription, we would consider this as a contraction.


The image below shows what the customer looks like with the current implementation. If the customer is subscribed to multiple apps as indicated above, all of the customer's subscriptions will be under a single customer profile. 



When the split subscribers per app option is enabled, ChartMogul creates a customer for every unique app the customer is subscribed to. We append the AppAppleID  to the customer id to preserve the customer's uniqueness in the app. This means that when one of the active subscriptions get cancelled, it will be reported as a churn instead of a contraction.



Enabling the setting

This option is deactivated by default when you create a new App Store Connect data source. To enable this feature, click the data platform icon on the left menu to navigate to the Data platform tab and select your App Store Connect data source from the list. 


Once you are in your App Store Connect data source page, the option can be seen under the Data import options:


After changing the option, you need to re-sync your App Store Connect data source for the changes to take effect.

What you need to know:

  • Switching this option ON or OFF will require a re-sync of the data source. Any edits made to the customers  and subscriptions will be removed (i.e. MRR edits, merged customers, custom attributes, connect subscriptions). The reason is because we will need to create a new set of customers from your App Store Connect data and the only way to do this is by importing everything from scratch.