HomeProduct DocsAPI ReferenceChangelog
RecurlyAPI GuidesRecurly.jsWebhooksAPI ReferenceSupportBook demo
Product Docs

Pause subscriptions: Tracking your Pause impact

Learn how to measure and interpret the financial and retention impact of your subscription pause program in Recurly. Understand how to monitor key performance metrics like unpause rate, pause duration, and voluntary churn rate using subscription exports, analytics reports, and real-time webhook tracking.

Upcoming: Bring your pause strategy questions to our CSMs live. Register for Office Hours →
Retain Retain • Pause Subscriptions

Tracking your pause impact

Three metrics that tell you whether your pause strategy is working — what they measure, how to interpret them, and where to find them.

Navigation Menu

The three metrics that matter

Most of pause's value shows up in three numbers. Track these from day one so you have a baseline to optimize against.

Unpause rate

The percentage of paused subscribers who resume billing before or at the end of their pause period. This is your primary signal of whether pause is retaining customers or just delaying churn.

Primary signal

Pause duration

How long subscribers are actually pausing. This helps you forecast revenue, time re-engagement outreach, and identify whether your maximum pause limit is set at the right level.

Forecast & timing

Voluntary churn rate

Track your voluntary churn before and after enabling pause. A healthy pause program should move this number down over time as pause intercepts cancellations that would otherwise be permanent.

Program health

How to interpret what you see

1

Low unpause rate — adjust before drawing conclusions

An unpause rate below 50% doesn't automatically mean pause is failing — it may mean your pause duration is too long, your mid-pause re-engagement is weak, or pause is being used by subscribers who were going to churn regardless. Check pause duration and re-engagement timing before changing your eligibility rules.

2

Very short pause durations — surface pause earlier

If most subscribers are pausing for the minimum duration and resuming quickly, they likely knew they only needed a short break. That's a good signal — and a cue to surface pause earlier in the subscriber journey so it catches more temporary-reason cancellations before they escalate.

3

Maximum pause duration consistently hit — test a longer window

If a significant portion of subscribers are pausing to the maximum and not resuming, your limit may be cutting off subscribers who would have returned with more time. The 80-day average decision window means a two-cycle monthly pause may not be enough for all use cases. Test extending the maximum and watch whether unpause rate improves.

4

Voluntary churn unchanged after enabling pause — check placement

If voluntary churn isn't moving, pause likely isn't being seen at the moment of intent. Review where the pause option appears in your subscriber experience — if it's buried in account settings but not surfaced in the cancellation flow, most at-risk subscribers will never encounter it.

Give your program at least 90 days before optimizing

The average subscriber takes around 80 days to decide whether to return or cancel permanently after pausing. Drawing conclusions from the first 30 days of data will give you a distorted picture — most of your paused subscribers haven't yet reached their decision point. Run the program for a full quarter before making structural changes to eligibility or duration limits.

Where to find the data in Recurly

1

Subscription exports — pause duration and status

Go to Reports → Subscription Exports. The export includes two pause-specific columns: paused_at (when the subscription entered a paused state) and remaining_pause_cycles (how many pause cycles remain). Use these to calculate duration and build your unpause rate in your analytics tool of choice.

2

Recurly Analytics — subscriber counts

In Analytics → Subscribers, paused subscriptions are counted alongside active subscriptions and are not treated as churned. This means your subscriber count stays intact during a pause program — but watch MRR separately, since paused subscriptions contribute zero to MRR while billing is suspended.

3

Webhooks — real-time event tracking

Use the subscription_paused and subscription_resumed webhook events to feed pause data into your own analytics pipeline, CRM, or BI tool. These give you event-level granularity that the Recurly UI exports don't surface — including timestamps for each pause and resume event per subscription.

Track MRR impact separately for annual plan postponements

If you're using the update_subscription postponement method for annual plan subscribers, those subscriptions continue to contribute to MRR during the postponement period — unlike a true pause. Monitor annual plan postponements separately in your own reporting so you can accurately calculate the revenue impact of your pause program across both plan types.