Apple’s Retention Messaging API: a new ‘save’ moment for subscription cancellations
Apple’s Retention Messaging API lets you show a message, offer, or lower tier right inside iOS subscription settings when a user tries to cancel. Here’s what it is, how it works, and the practical guardrails.
Summary
Apple’s Retention Messaging API creates a new, high-leverage cancellation moment: when a user taps Cancel Subscription in iOS Settings, Apple can call your server and (if configured) show a message, a switch-plan option, or a promo offer directly inside the native subscription management flow.
RevenueCat’s write-up is useful because it spells out the operational reality: you need an always-on endpoint and you have sub-700ms to respond, per Apple.
Source: https://www.revenuecat.com/blog/engineering/apple-retention-messaging-api/
Why this matters (for growth teams, not just engineers)
If you sell subscriptions, cancellations are one of the few moments where:
- the user’s intent is explicit,
- the UX is native and high-trust,
- a small change can move revenue a lot.
This is not a “more push notifications” lever. It is a last-mile retention lever that sits right next to churn.
How it works (the minimum you need to know)
From the source article:
- You configure default retention messages by product + locale.
- When a user taps cancel, Apple calls your backend with transaction info.
- Your backend responds with one of: a message (optionally with an image), an alternate product, or a promotional offer.
- Response time target is under 700ms.
Practical guardrails (so this doesn’t turn into discount spam)
-
Treat it like onboarding copy, not a promo channel
- One clear promise, one piece of proof, one next step.
-
Segment by “why they bought”
- If your app sells outcomes (sleep, strength, language), your retention message should remind the user of the outcome they started for.
-
Prefer plan switches over discounts when possible
- A lower tier often protects LTV better than a blanket discount.
-
Measure the right thing
- Don’t celebrate “cancellations saved” if you just delayed churn by a week.
- Track: cancellation intent → retained at 30/60/90 days, and revenue per retained user.
What to do next (tiny wins)
- Write two retention messages: one value reminder, one plan-switch pitch. Keep both under 140 characters.
- Decide your “no regret” plan switch (monthly → annual, premium → basic) and document eligibility rules.
- Make a simple dashboard: cancellation attempts, save rate, retained at 30 days, and net revenue impact.
Category tag
Retention & CRM
Internal links
- Retention marketing guide: /guides/retention-marketing-guide/
- Mobile subscription strategy: /guides/mobile-subscription-strategy/
Editor: App Store Marketing Editorial Team
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.