Skip to content
AppDues
Log in
Contact salesSign up

Exit Offers in Paywalls

An exit offer gives a user a second option at the moment they try to close your paywall without buying. Paywalls can show one with no code changes, but two things decide whether it works for you: whether your integration path actually triggers it, and whether Apple will accept it. This guide covers both, in that order.

What an exit offer actually is

Picture the dismissal moment: the user has looked at your paywall and is reaching for the close control without subscribing. An exit offer intercepts that moment and swaps in a different offering rather than ending the flow. What changes is the deal on the table — a cheaper tier, extra trial days, or a shorter commitment — not the fact that the user is being asked to pay.

The classic pairing is a headline annual plan with a monthly fallback behind it. Someone who wanted the product but balked at a twelve-month commitment still has a way in. The tactic has a long history in web retail, where it is used to rescue abandoned carts; on mobile it is a way to keep a hesitant visitor from leaving with nothing.

Setting it up in the Paywall Builder

Configuration lives in the Paywall Builder inside the dashboard. While editing a paywall, you point it at another one of your offerings and that offering becomes the exit offer. The dashboard step needs no code changes, which keeps the cost of trying different win-back strategies low and lets you watch conversion and revenue respond.

Before you build anything, check the integration path, because this is where most surprises come from.

Which entry points trigger the offer

The offer only fires when the paywall is presented through the SDK's presentation functions. If you embed paywall views or components directly into your own UI, the exit offer will not appear at all, no matter how it is configured in the dashboard.

Use the control map below to confirm your app is on a supported path before you spend time tuning the offer itself.

The App Store review question

Exit offers are routine on the web. On the App Store, adoption has been uneven. Some developers report rejections that cite Guideline 5.6, Developer Code of Conduct, which warns against manipulative practices that push users into unwanted purchases. A developer on Reddit shared a rejection notice in which the reviewer objected that a second discount appeared right as they tried to leave the subscription screen, framing that as steering customers toward purchases they did not want.

The guideline text itself does not name exit offers. In Apple's words: "Apps should never prey on users or attempt to rip off customers, trick them into making unwanted purchases, force them to share unnecessary data, raise prices in a tricky manner, charge for features or content that are not delivered, or engage in any other manipulative practices within or outside of the app." Because "manipulative" is a judgment call, the result is a gray area: plenty of live apps use exit offers, while some reviewers reject them under this rule. No comparable rejection reports had surfaced for Google Play submissions, and as of the article's March 2026 publication the practice appeared consistent with Google Play policies. Treat both the rejection pattern and the Android picture as dated observations and re-check current guidelines before you ship.

A practical rollout order

Start on Android. Measure the effect on conversion there before accepting any risk on iOS. The Targeting feature lets you send paywalls with exit offers only to Android users, so the iOS experience stays unchanged while you gather data.

On iOS, the source article's position is that a well-built exit offer is a legitimate marketing tool, but that Apple's current ambiguity makes it something to enable at your own risk. Whatever stance you take, have a response ready in case a submission is rejected under Guideline 5.6.

One line you should not cross: never flip the feature on remotely after approval to dodge review. That breaches the Apple Developer Program License Agreement and can cost you your developer account.

Two different failures, two different fixes

Teams often conflate these, so separate them early:

  • The offer never appears. Almost always an integration problem: the paywall is embedded as a view or component rather than presented through the SDK's presentation functions, or the exit offering was never assigned in the dashboard.
  • The offer appears but a store rejects the build. This is a policy problem, not a bug. It is specific to App Store review and is not fixed by changing SDK calls.

Diagnose which one you have before touching configuration, because the remedies have nothing in common.

Worked example: annual paywall, monthly fallback

Suppose your main paywall sells an annual plan and you want a monthly fallback for hesitant users.

  1. In the dashboard, open the paywall in the Paywall Builder and assign an existing offering that contains the monthly plan as the exit offer.
  2. Confirm the paywall is shown through the SDK's presentation functions on iOS and cross-platform builds; on Android, confirm you are using the dialog or activity classes, where the behavior is automatic.
  3. If the paywall is embedded directly in your UI, move it to a presented flow or accept that no exit offer will show.
  4. Use Targeting to limit the exit-offer paywall to Android while you measure impact.
  5. Only after you have Android numbers should you decide whether the iOS review risk is worth taking.
Exit offer support by SDK entry point
PlatformEntry pointExit offer behavior
iOS and cross-platform SDKspresentPaywall / presentPaywallIfNeededWorks when the paywall is presented through these functions
AndroidPaywallDialog and PaywallActivity classesAutomatically enabled
Any platformManually embedded paywall views or components (e.g. PaywallView, Paywall composable, <RevenueCatUI.Paywall>)Does not work

Behavior described as of the article's March 2026 publication; confirm against current paywall documentation for your SDK version.

Frequently asked questions

Why is my exit offer not showing up?

The most common cause is how the paywall is displayed. Exit offers only fire when the paywall is presented through the SDK's presentation functions (presentPaywall or presentPaywallIfNeeded on iOS and cross-platform, the dialog or activity classes on Android). If you embed paywall views or components directly into your own UI, the offer is skipped entirely. Also confirm an exit offering was actually assigned to the paywall in the dashboard.

Do I need to write code to add an exit offer?

Not for the configuration. You designate another offering as the exit offer inside the Paywall Builder in the dashboard. The only code-side requirement is that your paywall is presented through a supported SDK entry point rather than embedded in your own view hierarchy.

Can Apple reject my app for using an exit offer?

It has happened. Some developers report rejections citing Guideline 5.6, Developer Code of Conduct, which prohibits manipulative practices aimed at pushing users into unwanted purchases. The guideline does not explicitly ban exit offers, and reviewers apply it inconsistently, so the risk is real but not deterministic. Those reports date from the article's March 2026 publication; check the current guidelines before submitting.

Is it safer to launch exit offers on Android first?

That is the sequence the source article recommends. No rejection reports for exit offers had surfaced on Google Play as of the article's publication, so Android is the lower-risk place to measure conversion impact. The Targeting feature lets you restrict the exit-offer paywall to Android users while you evaluate.

Can I enable exit offers remotely after my iOS app is approved?

No. Turning the feature on after approval to avoid review violates the Apple Developer Program License Agreement and can result in termination of your developer account. If you ship exit offers on iOS, they should be part of the build the reviewer sees.