Apple on November 4, 2026 made retention messages available to every developer with auto-renewable subscriptions, letting apps place a message, an image or a discounted offer on the page that appears when a subscriber taps Cancel Subscription in Apple's own subscription settings. The setup now sits in App Store Connect, open to any app, while the Retention Messaging API, which lets a developer's server pick a message for each subscriber in real time, remains available only by request.

In Short

When someone on an iPhone, iPad, Mac or Vision Pro tries to cancel an app subscription through Apple's settings, the app can now show a short note about what they would lose, a picture, or a cheaper deal to stay. Apple checks every message before it goes live and bans prices or discount wording in the text itself, so any deal is shown in Apple's own format underneath. App makers can set this up in a web dashboard, while picking a different message for each person through a server connection still needs Apple's approval.

What went live on November 4

The announcement came as a short post on the Apple Developer news site titled "Now available: Retention messages for subscriptions," dated November 4, 2026. The post describes retention messages as appearing in the cancellation flow and says they can include text, images or a special offer. It names two routes. App Store Connect handles configuration, including subscriber eligibility and the wait time between messages, while the Retention Messaging API lets developers choose which message each subscriber sees based on subscription details. API access, according to the post, is available by request.

Apple's App Store Connect help documentation sets out the purpose in one sentence. "Retention messages help you re-engage subscribers at the point of cancellation by reminding them of the value your subscription provides," according to Apple. "When a subscriber initiates a cancellation, a retention message can highlight key features, announce upcoming content, or present a promotional offer to encourage them to stay."

The scale is limited by design. "You can create up to 10 retention messages per app and apply each message to one or more subscriptions," the help page states. There is no cap on how many subscriptions one message can cover, but the relationship runs only one way: "A subscription can have only one retention message assigned to it at a time." Selecting a subscription that already belongs to another message moves it, removing it from the earlier message once the change is saved. And deleting a message, according to the help page, cannot be undone.

Who can touch the setup matters for marketing teams. The help page lists the required role as "Account Holder, Admin, App Manager, or Marketing." That is a broader group than Apple allowed for the multiseat purchase options it launched two weeks earlier, which were limited to the Account Holder, Admin and App Manager roles when Apple put developers' subscriptions on sale to schools and firms by default on October 22. A marketing user can therefore write the copy, add offers and submit a cancellation message for review without engineering involvement.

On the same day as the news post, Apple published version 1.6 of the Retention Messaging API. Its changelog, dated 2026/11/04, adds support for a larger universal asset image size and a new error for disallowed characters. It also changes how the two routes interact, which is covered in detail below.

Three versions of one screen

Every retention message in App Store Connect has one required element and two optional ones. "A retention message consists of required text, and two optional components you can configure: an image and one or more retention offers," according to the help page. Which version a subscriber sees depends on what the developer has added and on whether that person qualifies for an offer.

Apple lists three outcomes. The first is "Text only," described as a header and body text with no image or offer. The second is "Text and an image," which is "Shown when you've added an image and either haven't associated an offer, or the subscriber isn't eligible for any associated offer." The third is "Text and a retention offer," which is "Shown when you've associated at least one offer with the message and the subscriber is eligible for the offer."

So the image and the offer compete for the same space. An eligible subscriber sees the offer instead of the image; an ineligible one sees the image. Apple's preview tool in App Store Connect lets developers check both versions, with a menu option for previewing what an ineligible subscriber sees, and switches between a card view and an iPhone or iPad layout.

The page itself belongs to Apple. According to the Retention Messaging API documentation, "The system displays the retention message to the customer after they tap Cancel Subscription on a subscription details page." What follows is a Confirm Cancellation page. On that page, according to the same documentation, a customer "can continue to cancel by tapping Cancel Subscription," can tap Keep Subscription, or, depending on the message, can redeem an offer or subscribe to a suggested plan. The Cancel Subscription button stays on screen in every version.

Images follow strict specifications. The help page lists two supported sizes for App Store Connect, 3840 by 2160 pixels or 5244 by 2950 pixels. The API documentation adds that uploaded images must be PNG files without transparency and should work in both light and dark modes.

Retention offers: who qualifies

The offer component is new. Apple calls these retention offers, and its WWDC26 session on the feature, "Explore Retention Messaging in App Store Connect," described them as a new offer type for retention messages. When a subscriber redeems one, the signed transaction and renewal information carry an offer type value of 5, according to that session, alongside the usual offer identifier, discount type and period fields.

"Retention offers are configured at the subscription level," according to the help page. "You can pair an existing offer with a new or updated message without having to reconfigure the offer." There is one condition on visibility: "Because retention offers appear to subscribers only through a retention message, you must associate an offer with a message before subscribers can see it."

The limits and eligibility rules sit in the help page's step-by-step sections. Developers can create up to 10 retention offers for each subscription billing plan type, and all 10 can be associated with a single message. Billing plan type, in Apple's footnote, means either a standard billing plan or a monthly plan with a 12-month commitment for one-year subscriptions.

Eligibility is set with two values. The first, Paid Subscription Duration, is the minimum time a subscriber must have held a paid subscription before qualifying. The second, Wait Between Offers, sets how long a subscriber must wait before redeeming the same offer again. That wait applies to each offer on its own, not to the subscription as a whole, so a subscriber who qualifies for two different offers on one subscription may receive the second without waiting. The help page does not list the values each setting accepts.

The commercial terms mirror Apple's other offer types. Developers choose countries or regions, then one of three discount types: Pay as you go, Pay up front or Free. App Store Connect then calculates prices for every selected country from the default price using the most recent foreign exchange rates, with manual overrides allowed. The offer's reference name and identifier cannot be changed once created; the identifier is what shows up in Sales and Trends reports and in StoreKit transactions.

Who decides which offer appears when a subscriber qualifies for several? Apple does. The WWDC26 session said the App Store selects the best eligible offer. Apple has not published the criteria it uses for that choice.

What the copy cannot say

Every message passes through App Review, and Apple's content rules are specific. Header and body text must comply with the App Review Guidelines like other metadata. The rule with the most practical bite concerns prices: the text cannot reference promotional offers, discounts or specific prices. Apple's own examples of banned wording are a dollar price point, a percentage discount and a free month. The reasoning is that every subscriber sees the text, including those who are not eligible for any associated offer, and App Review rejects messages that mention pricing or offers. The offer itself is rendered by Apple's interface beneath the developer's copy.

Statements about loss are allowed if they are factual. Apple gives losing access to downloaded content and losing access to premium features as acceptable examples. Coercive claims and unverifiable promises are not. Apple's example of a prohibited claim is telling users that cancelling a VPN service will cause a virus infection, and it strongly discourages softer versions, such as suggesting a device becomes more exposed to threats, as well as unsupported superlatives and statistics. It also asks for standard capitalization and punctuation, without all-caps text or repeated exclamation marks.

The Retention Messaging API documentation is more compressed on the same point. "Don't upload content that is misleading or inaccurate," it states.

The pricing restriction echoes a rule Apple applied to App Store marketing earlier this year. Its creative asset best practices, published on August 5, 2026, require artwork that meets a 4+ age rating and excludes specific pricing, discounts, website URLs and copyright symbols. In both cases developer-written copy is kept free of prices, while Apple's own interface displays the commercial terms.

Edits are handled as new versions. Changing an approved message creates a draft that sits alongside the published version, and the published version keeps running until App Review approves the draft. Sandbox testers always see the latest draft. There is no rollback: once a draft is approved it replaces the previous version permanently.

The API route: a message chosen in 700 milliseconds

The Retention Messaging API predates the App Store Connect tools by more than a year and remains the more powerful option. The documentation page still carries a pre-release label: "To learn more about this pre-release and express interest, see Request access to the Retention Messaging API."

Apple describes it as "a server-to-server service that enables you to select which message the system displays to customers when they view a subscription details page and might cancel." Messages and images are uploaded in advance for specific products and locales. According to the documentation, "Your messages remind customers about the features or content they have access to with the subscription, or show them alternative offers."

The API supports four message types, one more than App Store Connect. According to Apple, they are a text-based message that can include bullet points; the same with an image; "A switch-plan message, which contains text and a suggested subscription the customer may choose to switch to"; and "A promotional-offer message, which contains text and a promotional offer to continue service at a discounted price, either at the same or a different tier of service." The switch-plan option, which steers a departing subscriber toward a cheaper or different plan rather than out the door, is available only through the API.

There are two ways to use it. The simpler is to configure default messages, which "are text-based messages, with or without an image or bullet points, that apply to specific products and locales." Defaults cannot carry offers. "To provide retention messages that include offers, use the real-time messaging flow," the documentation states.

The real-time flow is where the API differs most from App Store Connect. According to Apple, "The real-time messaging flow calls your server when an active subscriber views a subscription details page with a Cancel button." The documentation gives two examples of where that happens: the Apple Account Subscriptions page and the subscription details page on the App Store. The call contains a signed payload with the customer's original transaction identifier, the product identifier and the locale. With those, a developer can look up the subscriber in its own systems and decide what to show. The documentation instructs developers to check that the app identifier in each request matches their own app and not to respond if it does not.

Speed is the constraint, and the margin is thin! The developer's endpoint must respond within 700 milliseconds in production, or the App Store server times out and the request fails, according to the API's setup documentation. Before a production address can be registered, the server has to pass a performance test in the sandbox environment with a similar threshold of approximately 700 milliseconds. The endpoint must also use a valid SSL certificate and TLS 1.2.

The setup sequence in Apple's documentation runs to five steps: upload and prepare messages; configure a default message "for every product in each locale, as a fallback"; implement the endpoint and register it in sandbox; pass the performance test and register the production address; then respond to live requests.

Which message wins

Apple's documentation sets a strict order of precedence. "Retention messages that you configure in App Store Connect take precedence over these default retention messages," according to the API overview. And at the top: "Retention messages you select in real time take precedence over default retention messages and retention messages configured in App Store Connect."

Version 1.6, released on November 4, tightened that chain. According to the changelog, the system now always sends a request to the developer's real-time address, whether or not a default message exists. If the server returns nothing, the system falls back first to the message configured in App Store Connect and then to the API's default message, and defaults now fall back to the nearest configured locale when no exact match exists. A real-time response can also now name a message created in App Store Connect, so the two systems can share a single library of approved copy. If none of the three produces a message, no retention message appears.

Limits in the documentation

The API documentation is precise about capacity. Each app can hold up to 2,000 messages and 2,000 images through the API, against 10 messages in App Store Connect. Headers are capped at 66 characters, body text at 144, image alternative text at 150 and bullet point text at 66, all as UTF-8 strings. Full-size images must be 3840 pixels wide and between 160 and 2160 pixels tall; universal asset images, added on November 4, measure 5244 by 2950 pixels; bullet point icons are 1024 by 1024. Promotional-offer and switch-plan messages cannot include images or bullet points.

Rate limits are tight. Most endpoints allow one request per second per app in production, with Configure Default Message allowing 10, and the limits are enforced on an hourly basis. In sandbox, limits are 10% of production. Uploaded messages start in a pending state and become displayable only after App Review approves them; images are checked by Apple separately, and both must be approved before a message can appear. In sandbox, approval is automatic.

Which devices show them

The feature has a hardware boundary. "Retention messages are visible only to devices running iOS 15.1 or later, iPadOS 15.1 or later, visionOS 1 or later, or macOS 14 or later," according to the API documentation. Apple TV and Apple Watch are not on the list, even though Apple's subscription overview page states that subscriptions are available on tvOS and watchOS as well. The messages also live only inside Apple's own subscription management pages, which handle subscriptions billed through Apple's in-app purchase system.

Nearly 16 months from pre-release to general release

The changelog shows how long Apple has been building this. Version 1.0, labelled as the initial pre-release, is dated July 16, 2025. Version 1.1 on September 4, 2025 added environment and signed date fields to requests. Version 1.2 on November 5, 2025 added support for Apple's Advanced Commerce API in responses. The performance testing endpoints arrived in version 1.3 on December 9, 2025.

The 2026 updates broadened the format. Version 1.4 on March 31 added endpoints to configure the real-time address and read default messages, together with bullet points and control over header position. Version 1.5 on April 27 added a billing plan type field so that switch-plan messages can propose monthly subscriptions with a 12-month commitment, the payment option Apple now promotes at the top of its subscription overview page: "Offer subscribers more affordable options with a new payment option: monthly subscriptions with a 12-month commitment." A server update on May 5 moved the recommended domains to api.storekit.apple.com and its sandbox equivalent.

Apple then presented the App Store Connect version at WWDC26, held from June 8 to 12. The session said App Store Connect retention messaging was open to all, and that real-time messaging required an interest form. Apple's "Now available" post followed nearly five months later.

What Apple says retention messages do

Apple has published one set of performance figures, presented in the WWDC26 session rather than in the November announcement. Apple defined save rate as the percentage of subscribers who keep their subscription after reaching the cancel confirmation page. According to the session, subscriptions that adopted retention messaging saw an average save rate increase of 1.4 percentage points, which Apple equated to an 82% increase. Promotional offer messages achieved the highest observed result, a 5.5-point increase, which Apple equated to 223%. The presenter added that results varied across developers.

Those figures imply low starting points. By PPC Land's calculation, a 1.4-point gain that equals an 82% increase implies an average save rate of about 1.7% before retention messaging and about 3.1% after. A 5.5-point gain equal to 223% implies roughly 2.5% before and 8% after. Read that way, even the best-performing message type in Apple's data still left more than nine in ten people who reached the confirmation page without their subscription. Apple did not disclose the number of apps, subscribers or territories behind the figures, the period measured, or whether the comparison was a controlled test. The two percentages also imply different baselines, suggesting the samples differ.

The figures matter because cancellation is one of the few moments when a lapsing subscriber is still reachable inside Apple's ecosystem. RevenueCat's State of Subscription Apps 2026 report found that AI apps lose subscribers 30% faster than other apps, with annual-plan retention of 21.1% against 30.7%. Subscriber churn at that scale is the problem retention messages are designed to address.

Apple's share of a saved subscription

Every subscription saved on Apple's cancellation screen continues to generate commission for Apple. The subscription overview page sets out the standard structure: "During a subscriber's first year of service, you receive 70% of the subscription price at each billing cycle, minus applicable taxes. After a subscriber accumulates one year of paid service, your net revenue increases to 85% of the subscription price, minus applicable taxes." Members of the App Store Small Business Program receive 85% regardless of tenure.

Discounts reduce the base on which both parties earn. A retention offer at half price halves the developer's revenue and Apple's commission for the offer period; a free period yields nothing for either. The overview page addresses how offers affect the one-year clock: "Days of paid service include all subscription offer types (introductory, promotional, and offer codes) with paid pricing options (pay as you go, pay up front)." It adds that "Free trials and renewal extensions are excluded from days of paid service."

That list does not mention retention offers, or win-back offers, by name. As of November 7, the overview page also states that developers "can create introductory offers, offer codes, promotional offers, and win-back offers," without naming retention offers as a fifth type, and its description of the Offers dashboard in App Store Connect Analytics lists the same four. Whether a paid retention offer counts toward the year needed for the 85% rate is therefore not spelled out on that page, though the Free option in retention offers would logically fall under the exclusion for free periods.

Commission rates have been moving in some markets. Apple cut the standard Taiwan App Store commission to 26% from October 31 after an antitrust probe, and earlier this year it cut China mainland rates to 25% and 12%, with the lower rate covering auto-renewing subscriptions after year one. Retention offers in those storefronts are discounted from prices that already carry the local rate.

For Apple, the subscription base is large. Apple reported on November 2 that Services revenue rose 10% to $31.573 billion in its fiscal fourth quarter, and finance chief Kevan Parekh said on the call that paid subscriptions exceeded 1.5 billion.

Apple's growing subscription toolkit

Retention messages complete a set of tools that now covers every stage Apple names on its overview page: acquire, retain and re-acquire. "Grow, retain, and re-acquire customers by giving them a free or discounted price for a specific duration for an auto-renewable subscription," the page states. Introductory offers target new subscribers. Promotional offers and offer codes work across stages. Win-back offers, which carry a banner on the page announcing that they are now available, target people who have already left, with Apple displaying them on the App Store, in apps and in subscription settings.

Before retention messages, the in-app version of this moment was the developer's responsibility. The overview page describes it: "If they cancel, you might provide an offer to help win them back and encourage them to resubscribe. Or you might present a survey where they can share feedback about their subscription experience and reasons for cancelling, which can inform your marketing strategy." Those tactics only work when the cancellation starts inside the app. A subscriber who goes straight to Apple's settings bypasses them, and that is the path retention messages now cover.

Apple's overview page spends most of its length on acquisition: onboarding, freemium experiences, metered paywalls and promoted in-app purchases that can appear in App Store search results. Retention gets a separate section with a different tone. "For people to stay subscribed to your app, they need to continue getting value out of the subscription," it states. For subscriptions shared through Family Sharing, which allows up to five family members to share access, the WWDC26 session showed that the App Store already tells the subscriber at cancellation that family members will lose access.

The November release also follows several subscription changes in quick succession. On October 13, Apple's revised developer agreement let one subscriber buy app seats for a group, and on October 22 multiseat purchasing went live through Apple Business and Apple School Manager. Offer codes, which Apple extended to consumables, non-consumables and non-renewing subscriptions at WWDC 2025, are now listed on the overview page as available on macOS as well.

Why the cancellation screen matters to marketers

For subscription marketers, the cancellation page has become a placement with rules of its own, managed by Apple, reviewed by Apple and populated with offers whose eligibility Apple enforces. Copy is limited to a 66-character header and a 144-character body, cannot mention a price, and must pass App Review before it runs. Developers using App Store Connect get 10 messages per app; those with API access get personalised selection based on their own data about each subscriber, within 700 milliseconds.

The data is Apple's too. App Store Connect's Subscriptions dashboard, according to the overview page, includes "cancellation reasons" alongside active plans, monthly recurring revenue, retention and conversion rates. The page does not say whether retention message performance or retention offer redemptions are reported there. TikTok Shop has taken a similar route for physical goods, giving US sellers a Subscribe dashboard that tracks why shoppers cancel.

Cancellation flows also carry regulatory risk. Interfaces that make leaving harder than joining are widely described as a dark pattern, and cancellation practices have drawn enforcement attention, as when Adobe disputed an FTC complaint that targeted, among other things, how hard it was to cancel some of its plans. Apple's design keeps the Cancel Subscription button on the confirmation page alongside any message or offer, and its overview page includes a direct instruction: "To ensure a positive experience, always make it easy for people to access the system-provided management UI where they can cancel if they wish." Apple's content rules against coercive claims point the same way. Whether one additional screen in the path is a benefit or an obstacle depends on who is asked, and Apple has not published any measure of how many subscribers leave the flow without either cancelling or keeping their plan.

Then there is the question of scale. Apple's commissioned study found that the App Store ecosystem facilitated $1.4 trillion in billings and sales in 2025, including $149 billion in digital goods and services, the category that covers subscriptions. Small shifts in save rates, applied to a base of that size, translate into material sums for developers and for Apple.

What the documents leave open

Several details are not settled by Apple's published material. The App Store Connect help page's introduction says a retention message can "present a promotional offer," while the configuration steps that follow use a separate retention offer type, and the API's real-time flow uses promotional offers proper. The help page does not list the accepted values for Paid Subscription Duration or Wait Between Offers, and it gives no review time for messages. The API documentation still describes the real-time service as a pre-release requiring an access request, and Apple has not said when, or whether, that will change.

Nor has Apple published adoption figures for the 16 months of pre-release, or any save rate data beyond the averages shown in June. The subscription overview page, as of November 7, does not mention retention messages at all.

Timeline

Summary

Who: Apple, and developers that sell auto-renewable subscriptions through Apple's in-app purchase system, including marketing staff, who can configure messages under the Marketing role in App Store Connect.

What: Retention messages, shown on Apple's Confirm Cancellation page, are now available to all developers through App Store Connect, with up to 10 messages per app, optional images and new retention offers carrying discounts or free periods. The Retention Messaging API, which selects messages in real time and adds switch-plan and promotional-offer messages, remains available by request and received version 1.6 the same day.

When: Apple announced general availability on November 4, 2026. The API first appeared as a pre-release on July 16, 2025, and the App Store Connect version was presented at WWDC26 in June 2026.

Where: In the Apple Account Subscriptions page and on App Store subscription details pages, on devices running iOS 15.1, iPadOS 15.1, visionOS 1, macOS 14 or later. Apple TV and Apple Watch are not listed.

Why: Apple's stated goal is to remind subscribers of a subscription's value as they decide whether to cancel. Its WWDC26 figures show average save rate gains of 1.4 percentage points and 5.5 points for promotional offer messages, from low starting levels by PPC Land's calculation, while every saved subscription keeps generating commission for Apple.