Why Your App Store Subscription Retention Message Does Not Appear

A retention message can be configured in App Store Connect and still be missing from a particular cancellation test. Before judging performance, check that the test matches the subscription, message configuration, and cancellation surface that Apple describes.

Verify the configuration

In App Store Connect, open Subscriptions and then Retention Messaging. Check that the message is assigned to the intended subscription and approved and published for production. Compare the message setup with Apple's retention message instructions. Record the subscription, associated offers, locale, and status shown in App Store Connect. If the message is meant to accompany an offer, verify the offer separately rather than assuming that configuring a message makes every subscriber eligible.

Reproduce the cancellation path

Use a known test account and follow the relevant Apple subscription cancellation flow. Record the device, operating system, storefront, locale, and subscription status. Separate a missing message from a message that appeared but did not display a particular offer. A message that appears in sandbox can still be an unpublished draft, so test visibility does not prove it is live. For real-time API-supplied messages, first confirm that you have been granted the required access, then use the Retention Messaging documentation to check request handling.

Measure outcomes after visibility is confirmed

When the message appears as expected, decide which result to track, such as a completed cancellation or a later renewal. Verify that those outcomes are actually measurable in your data before reporting a rate. If you can see renewals but cannot identify message exposure, report renewals as a separate metric instead of claiming that the message saved those subscribers.