Churn recognition options


You must have an Admin or Owner ChartMogul account to access your data settings in order to modify your churn recognition options. Read more about User Permissions.

There are two churn recognition options available for all ChartMogul customers and one specific to Recurly.  

Under Settings > Data settings > Subscription Analytics, there is a set of options titled "Churn recognition".


  • Always recognize cancellations as churn at the end of the paid-up billing period
    • Churn will always happen at the end of the current paid-up subscription billing period, even if the subscription is canceled immediately in your billing system. This is often considered as a good practice for MRR reporting. One side effect (and a potential benefit) is that your MRR will usually appear to be higher with this setting.
  • Always recognize cancellations as churn at the time of cancellation
    • Churn will always happen in ChartMogul at the time the subscription is canceled/expired in your billing system. This gives you a more real-time view of your forward-looking MRR and is closer to the concept of Committed Monthly Recurring Revenue (CMRR).

Here's an illustration of how these options will affect the date on which your customers will be reported churned.



The behavior of these options works consistently across all billing systems.

  • Churn subscriptions at the time when the cancellation event is triggered/clicked, regardless if subscription is set to cancel immediately or cancel/not-renew at the end of the billing period
    • This option applies to data imported from Recurly only. For data from other data sources, cancellations will be recognized as churn at the time of cancellation. 

If you have imported your data using the Import API, subscription cancellations are always recognized as churn at the time of cancellation, regardless of the selected setting. 

If you alter the churn recognition setting, the change in how ChartMogul recognizes churn in your account will only be reflected going forwards. You will need to re-import your data to make the behavior consistent historically and going forwards.