Presenting Offers

Overview

Encore allows you to present targeted offers to users in exchange for rewards (free trials, discounts, credits) at critical moments like cancellation flows or feature paywalls. The SDK uses a delegation pattern — you register purchase and passthrough handlers, then call .show() wherever you need an offer.

Handle Offer Results

Choosing your integration shape: This page shows the handler pattern. If your call site has direct access to purchase logic, the async-result pattern is often cleaner. See Integration Patterns for the decision tree and Android Integration Patterns for Kotlin examples.

Before presenting offers, register handlers that tell the SDK how to process purchases and what to do when a user dismisses. Register these once in Application.onCreate(), after configure().

Register `onPurchaseRequest`

Called when a user accepts an offer. Use this to trigger a purchase via Google Play Billing, RevenueCat, Adapty, or your own billing implementation.

Encore.shared.onPurchaseRequest { request ->
    // Route to RevenueCat, Adapty, or your billing implementation
    billingManager.purchase(request.productId)
}

Register `onPassthrough`

Called when the user dismisses the offer or no offers are available. Use this to resume the user’s original action (e.g., proceed with cancellation).

Encore.shared.onPassthrough { placementId ->
    // Resume your original user flow
    proceedWithCancellation()
}

`onPurchaseComplete` (Optional)

Only needed when you don’t set an onPurchaseRequest handler, or when integrating with subscription managers that don’t auto-detect purchases (e.g., Adapty, Qonversion). RevenueCat and Superwall auto-detect purchases and don’t need this callback.

Encore.shared.onPurchaseComplete { productId, placementId ->
    // Sync purchase state with your subscription manager
}

Summary

Callback	When it fires	Required?
`onPurchaseRequest`	User accepts the offer	Yes
`onPassthrough`	User dismisses or no offers available	Yes
`onPurchaseComplete`	Purchase finishes (for managers that don’t auto-detect)	Optional

Both onPurchaseRequest and onPassthrough must be registered before presenting any placements.

Presenting an Offer

With Coroutines (Recommended)

lifecycleScope.launch {
    Encore.placement("cancellation_flow").show()
}

Fire-and-Forget

For cases where you don’t need to await the result:

Encore.placement("cancellation_flow").show(lifecycleScope)

That’s it — when the user accepts an offer, your onPurchaseRequest handler fires. When they dismiss or no offers are available, onPassthrough fires.

Placement IDs

Use meaningful placement IDs to track where offers are triggered in your app:

// Cancellation flow
Encore.placement("cancellation_flow").show()

// Feature paywall
Encore.placement("premium_feature_gate").show()

// Onboarding
Encore.placement("onboarding_offer").show()

Placement IDs appear in your Encore Dashboard analytics, letting you measure conversion rates per placement.

Next Steps

Add Subscription Product - Create a Google Play subscription product and connect it to Encore
Configure Analytics - Track offer performance and measure impact

Getting Started

iOS SDK

Android SDK

Flutter SDK

React Native SDK

Capacitor SDK

Kotlin Multiplatform SDK

Web SDK

Integration Patterns

Automated Messaging

Offer Catalog

Offers API

Overview

Handle Offer Results

Register `onPurchaseRequest`

Register `onPassthrough`

`onPurchaseComplete` (Optional)

Summary

Presenting an Offer

With Coroutines (Recommended)

Fire-and-Forget

Placement IDs

Next Steps

​Overview

​Handle Offer Results

​Register onPurchaseRequest

​Register onPassthrough

​onPurchaseComplete (Optional)

​Summary

​Presenting an Offer

​With Coroutines (Recommended)

​Fire-and-Forget

​Placement IDs

​Next Steps

Overview

Handle Offer Results

Register `onPurchaseRequest`

Register `onPassthrough`

`onPurchaseComplete` (Optional)

Summary

Presenting an Offer

With Coroutines (Recommended)

Fire-and-Forget

Placement IDs

Next Steps