RevenueCat: Exit Offers in paywalls can lift conversion, but iOS App Review is a real risk
Exit offers (a discounted or alternative plan shown when a user dismisses a paywall) are effective, but Apple may flag them as ‘manipulative’ under Guideline 5.6.
Original article (source): RevenueCat (Charlie Chapman) - “Exit Offers in RevenueCat Paywalls” (published March 6, 2026)
What exit offers are (and why they work)
An exit offer is a secondary offer shown at the moment someone tries to close your paywall, typically:
- a cheaper plan
- a shorter commitment (monthly instead of annual)
- a longer trial
It is the classic “second chance” conversion play, borrowed from e-commerce cart abandonment.
The big caveat: iOS App Review can treat this as manipulation
RevenueCat calls out an iOS gray area: some developers have reported rejections referencing App Review Guideline 5.6 (Developer Code of Conduct), framing exit offers as a “manipulative practice”.
Their read is basically:
- Android: low/no known risk.
- iOS: proceed carefully, expect inconsistency reviewer to reviewer.
Practical implementation notes (RevenueCat-specific)
RevenueCat’s current constraints are operationally useful if you are planning experiments:
- Exit offers can be enabled in Paywall Builder (no code change).
- They only work when using RevenueCat’s presented paywall flows:
- iOS + cross-platform SDKs:
presentPaywall/presentPaywallIfNeeded - Android: enabled via
PaywallDialog/PaywallActivity
- iOS + cross-platform SDKs:
- They do not work if you embed paywalls directly in your UI (e.g., PaywallView / custom composables/components).
The part worth underlining: don’t play games with review
RevenueCat is explicit: do not hide exit offers from App Review and then remotely turn them on later. That is a policy violation with account-level risk.
What to do next (tiny wins)
- If you want the upside without the iOS roulette: test exit offers Android-first, then decide if you can defend the UX on iOS.
- If you ship on iOS: document the intent as “more plan choice” (not a pressure tactic), and keep the offer copy plain and honest.
Read the original: https://www.revenuecat.com/blog/engineering/exit-offers-in-revenuecat-paywalls/
Want help with ASO?
If you want this implemented for your app, check out our services - or run your workflow in APPlyzer.