Skip to content
AppDues
Log in
Contact salesSign up

Android Exit Offers: Which Paywall Method Actually Shows Them

A user who taps close on your paywall without buying is a conversion you can still reach. An exit offer is a second paywall shown at the moment of dismissal, usually with a different price, trial length, or plan. On Android, whether that second paywall appears depends less on your dashboard setup than on how you present the first one. This guide walks through the supported presentation methods, the dashboard steps, the SDK behavior behind the transition, and the one common integration pattern that quietly disables exit offers.

What an exit offer is and when it fires

An exit offer is a separate offering with its own paywall design, packages, and pricing. It appears automatically when a user dismisses the primary paywall without purchasing. The sequence is:

  1. The main paywall shows, for example an annual plan at $49.99/year.
  2. The user taps close or swipes to dismiss.
  3. Instead of closing, a second paywall appears with the exit offer, for example a monthly plan at $4.99/month.
  4. The user either subscribes to the exit offer or dismisses again, which closes everything.

The SDK handles the handoff between the two paywalls. Exit offers do not fire after a completed purchase: if the user subscribes on the main paywall, the paywall closes normally and no exit offer is shown.

The presentation method decides everything

On Android, the presentation method is the deciding factor. A paywall shown through PaywallDialog or PaywallActivity can surface an exit offer; a Paywall composable embedded directly in your layout cannot. The supporting table is delivered as an exact module; the reader-facing summary is that dialog and activity launcher support exit offers while the embedded composable does not.

The difference comes from who owns the dismissal. PaywallDialog and PaywallActivity control their own dismiss flow, so when the user taps close the SDK can step in, check for a configured exit offer, and show the exit offering before the paywall actually closes. An embedded Paywall composable lives inside your Compose layout and has no dismiss event of its own, so the SDK has nothing to step in on.

If you are on the embedded composable and want exit offers, switch to PaywallDialog or PaywallActivityLauncher. The migration is small and covered below.

Configuring the exit offer in the dashboard

Exit offers are configured entirely in the dashboard. Once your paywall is presented with a supported method, no additional code is required. The steps are:

  1. Create the exit offer offering. In your project, create a new offering (for example exit_offer_monthly) with the packages you want to show. This can be a discounted monthly plan, a longer free trial, or a different product.
  2. Create a paywall for that offering. Attach a paywall using the Paywalls editor and design it like any other paywall. This is the screen the user sees after dismissing the main paywall.
  3. Link the exit offer to your main paywall. In the Paywalls editor for the main paywall, open the exit offer settings and select the offering you created. This tells the SDK which offering to present on dismissal.

Once linked, the exit offer is live. The SDK preloads the exit offering data, intercepts the dismiss action, and presents the exit offer paywall.

Presenting with PaywallDialog

PaywallDialog is the recommended way to present paywalls in Compose. It shows the paywall as a full-screen dialog on compact devices and a standard dialog on tablets, and exit offers work automatically.

The simplest setup uses setRequiredEntitlementIdentifier to show the paywall only when the user lacks a specific entitlement. The exact code is delivered as a protected module.

For custom display logic, use setShouldDisplayBlock. The exact code is delivered as a protected module.

You do not write any exit-offer-specific code. PaywallDialog takes care of the whole sequence on its own: it fetches the exit offering when the paywall appears, catches the close action, and moves the user to the exit offer paywall when one is linked. Your setDismissRequest callback runs only after the user has closed both the main paywall and the exit offer, or on the first close when no exit offer exists.

If you pair setShouldDisplayBlock with an exit offer, the SDK runs that block again before it shows the exit offer. A false result, such as the user having bought on the main paywall and now holding an active entitlement, means the exit offer is skipped and the dialog closes right away.

Presenting with PaywallActivityLauncher

If your app does not use Compose, or you would rather work with Activities, PaywallActivityLauncher opens the paywall as its own Activity. Exit offers work here automatically too: the SDK opens the exit offer as a second Activity stacked on the first. The exact launcher code is delivered as a protected module.

When the user closes the main paywall Activity, the SDK opens the exit offer Activity on top without extra work from you. A purchase made on the exit offer returns PaywallResult.Purchased; closing the exit offer as well returns PaywallResult.Cancelled. Your onActivityResult callback can handle both outcomes the same way.

To launch without an entitlement check, use launch() instead of launchIfNeeded(). The exact code is delivered as a protected module.

Why the embedded Paywall composable skips exit offers

If you embed the Paywall composable directly in a navigation graph, exit offers will not trigger. The exact non-working pattern is delivered as a protected module.

The Paywall composable renders its content directly in your layout. When the user taps dismiss, onDismiss navigates back via navController.popBackStack(). The paywall has no opportunity to intercept the dismissal and show an exit offer because the navigation happens immediately.

To keep a navigation-based flow and still get exit offers, swap the embedded Paywall for a PaywallDialog inside the screen composable. The exact working pattern is delivered as a protected module.

Users see the same thing either way: a full-screen paywall they can dismiss. The difference is behind the scenes, where PaywallDialog owns the dismiss flow and can therefore hand off to the exit offer.

How the SDK handles the transition

When a paywall loads, the SDK calls preloadExitOffering() in the background. That method checks whether the current paywall's configuration includes an exit offer reference (an offering ID stored in PaywallComponentsData.exitOffers.dismiss.offeringId). If it does, the SDK fetches the offering from the backend and holds it in memory.

When the user taps close, the SDK checks two conditions:

  • Has the user completed a purchase? If yes, close normally with no exit offer.
  • Is there a preloaded exit offering? If yes, present it instead of closing.

With PaywallDialog, the switch is handled by swapping state rather than launching a new screen. The dialog's current offering is cleared, which closes the main paywall, and the exit offering is queued as pending. A LaunchedEffect notices the change and opens the exit offer as a fresh dialog.

With PaywallActivity, the switch is a new Activity launch. The exit offer Activity is the same PaywallActivity class, given the exit offering's ID as an argument, and its result is passed back to whoever started the original paywall.

The SDK also records a paywall_exit_offer event when an exit offer is shown, with the exit offer type (dismiss) and the exit offering identifier. That data appears in Charts, so you can measure how exit offers affect the conversion funnel.

Platform differences

The same structural rule applies across platforms: only presentation methods that control the dismiss flow support exit offers.

iOS. Exit offers work with presentPaywall() and presentPaywallIfNeeded(). They do not work with PaywallView embedded in SwiftUI. Reviewers have sometimes pointed to Apple's App Store Review Guideline 5.6 (Developer Code of Conduct) when rejecting apps that surface an extra offer as the user attempts to leave a paywall. What counts as a manipulative practice is a judgment call, and reviewers do not apply it uniformly: plenty of apps ship iOS exit offers without trouble, while others have been turned down. If you would rather ease in, use Targeting to turn exit offers on for Android users only.

React Native. Calling presentPaywall or presentPaywallIfNeeded can bring up an exit offer. Placing the <RevenueCatUI.Paywall> component inline in your layout cannot, because that inline component never owns the dismissal.

Kotlin Multiplatform. Exit offers are not yet supported in the Kotlin Multiplatform SDK.

Decision checklist before you ship

Use this checklist to confirm your integration will actually show the exit offer.

  • Presentation method. Are you using PaywallDialog (Compose) or PaywallActivityLauncher (Activity)? If you are on the embedded Paywall composable, exit offers will not appear.
  • Offering exists. Did you create a distinct offering for the exit offer with its own packages?
  • Paywall attached. Does the exit offer offering have its own paywall design in the Paywalls editor?
  • Link set. Is the exit offer offering selected in the main paywall's exit offer settings?
  • Display block. If you use setShouldDisplayBlock, does the condition still return true when the exit offer would be shown? If the user already has an active entitlement, the exit offer is skipped.
  • Dismiss callback. Does your setDismissRequest or onActivityResult logic treat the exit offer dismissal as the end of the flow?
  • Analytics. Are you watching for the paywall_exit_offer event in Charts to confirm the exit offer is being shown?
  • Platform scope. If you also ship on iOS, have you reviewed App Store review risk and considered Targeting to limit exit offers to Android?

Why an exit offer might not appear

Three distinct causes can prevent an exit offer from showing, and they need different fixes:

  • Unsupported presentation method. The paywall is embedded as the Paywall composable (or PaywallView on iOS, or <RevenueCatUI.Paywall> on React Native). The SDK has no dismiss event to intercept. Fix: switch to PaywallDialog or PaywallActivityLauncher.
  • No exit offer linked. The main paywall's exit offer settings do not reference an offering. The SDK preloads nothing and closes normally. Fix: create the offering, attach a paywall, and link it in the main paywall's exit offer settings.
  • Purchase already completed. The user subscribed on the main paywall, so the SDK closes normally. This is expected behavior, not a bug. The same applies when setShouldDisplayBlock returns false before the exit offer would be shown.

If none of these apply and the exit offer still does not appear, check whether the platform supports it at all: Kotlin Multiplatform does not yet support exit offers.

Exit offer support by Android presentation method
Presentation methodExit offers supported
PaywallDialog (Composable)Yes
PaywallActivityLauncher (Activity)Yes
Paywall composable (embedded)No

This table reflects the Android presentation methods described in the source. Support status is a structural property of how each method handles dismissal, not a version-specific claim.

Frequently asked questions

Why don't exit offers work with the embedded Paywall composable?

The embedded Paywall composable renders directly in your layout and has no dismiss flow for the SDK to intercept. When the user taps dismiss, your onDismiss callback (for example navController.popBackStack()) runs immediately, so there is no moment where the SDK could present a second paywall. Switching to PaywallDialog inside the same screen composable preserves the navigation flow while giving the SDK control over dismissal.

When does setDismissRequest fire if an exit offer is configured?

It fires only after the user has fully dismissed both the main paywall and the exit offer. If no exit offer is configured, it fires on the first dismissal. If the user purchases on the main paywall, the paywall closes normally and the exit offer is not shown.

Does setShouldDisplayBlock affect whether the exit offer appears?

Yes. Before it presents the exit offer, the SDK runs the block again. When the block returns false — say the user bought on the main paywall and now holds an active entitlement — the exit offer is passed over and the dialog closes straight away.

How do I tell whether the user purchased from the main paywall or the exit offer with PaywallActivityLauncher?

You don't need to distinguish them for result handling. If the user purchases from either paywall, the result is PaywallResult.Purchased. If they dismiss both, the result is PaywallResult.Cancelled. The onActivityResult callback handles both scenarios uniformly.

Are exit offers risky for App Store review on iOS?

Some App Store rejections have pointed to Guideline 5.6 (Developer Code of Conduct) when an app presents a further offer as the user attempts to leave a paywall. Whether a given flow counts as a manipulative practice is a judgment call, and reviewers do not apply it the same way: many apps ship iOS exit offers without trouble, while others have been turned down. If you would rather ease in, use Targeting to turn exit offers on for Android users only.

Do exit offers work in the Kotlin Multiplatform SDK?

Not yet. Exit offers are not supported in the Kotlin Multiplatform SDK.