ActivationPal

Voluntary vs involuntary churn in apps

Voluntary churn happens when a subscriber chooses to cancel or not renew; involuntary churn happens when a payment problem ends the subscription. A failed renewal attempt alone does not tell you which outcome occurred or whether access has ended.

Voluntary vs involuntary churn

Voluntary churn starts with a subscriber's decision: they cancel renewal, let a plan lapse, or choose not to continue. A cancellation event can arrive before the paid period ends, so cancellation and lost access are not always the same moment.

Involuntary churn starts with a payment problem, such as a renewal that cannot be collected. The case remains unresolved until later lifecycle events or the provider's current state establish the outcome.

The distinction changes what to investigate. Voluntary cancellations point toward the value, price, fit, or experience subscribers chose to leave. Involuntary losses point toward the payment path and the affected renewals. Combining both into one churn count hides those different causes.

When a failed renewal becomes churn

A payment failure is a renewal event, not proof that access ended. Check later lifecycle events and the provider's current subscription state to establish whether the subscription recovered or ended.

In ActivationPal subscription analytics, connect RevenueCat or Superwall and inspect cancellation, billing issue, uncancellation, renewal, and expiration events alongside app activity. The recorded sequence helps investigate what happened; confirm unresolved cases in the provider's current state.

How to diagnose subscription churn

For each suspected loss:

  1. Read the event type. Identify whether the record is a cancellation, billing issue, uncancellation, renewal, or expiration.
  2. Follow the user's event sequence. Check for later events that change the interpretation of the first one, then confirm unresolved subscription states with the provider.
  3. Investigate the matching path. Review cancellation feedback and the app experience after a cancellation; inspect renewal handling when the sequence begins with a billing issue.

ActivationPal records documented RevenueCat and Superwall lifecycle events alongside app activity. Its subscription analytics also follows trial cohorts through converted, pending, or churned outcomes, with cancelled and expired trials counted separately.

Compare churn across cohorts

For trial churn, compare cohorts by when trials started and follow each group to converted, pending, or churned. Pending trials have not reached a recorded outcome yet; revisit them as later subscription events arrive. For paid subscriptions, use the documented lifecycle sequence to investigate individual outcomes.

For a broader view, read churn analysis for subscription apps and subscription metrics.

Frequently asked questions

Is a cancelled subscription the same as churn?

Not always. A cancellation records a choice to stop renewing, while expiration records the subscription ending. Check the sequence and current provider state before treating cancellation as lost access.

Is a failed payment involuntary churn?

Not by itself. Later lifecycle events or the provider's current state may show that the subscription recovered. Treat the billing issue as unresolved until the outcome is established.

How should I compare voluntary and involuntary churn?

Separate subscriber cancellations from payment-related events, and compare periods with the same follow-up window. Confirm unresolved payment cases with later events or the provider's current state before counting an outcome.

Can subscription analytics show the difference?

ActivationPal lets teams inspect documented RevenueCat and Superwall lifecycle events alongside app activity, and review trial cohort outcomes. Check the subscription provider's current state to resolve an individual billing issue.