Customize and Target Paywalls
Not every subscriber sees the same screen at the same moment.
Paywall targeting lets you decide which paywall a user sees based on who they are, where they are, what they just did, and which app version they are running — without shipping a new build. This overview explains the available targeting dimensions, how to build and test paywalls, and how to choose a segmentation strategy that fits your app.
What paywall targeting covers
Targeting is the layer that connects a user context to a specific paywall. Instead of one default screen for everyone, you can define rules that match a user to a variant. The available dimensions include country, app platform, app version, custom attributes you define, feature-use moments, locked-feature gates, and local-market preferences. You can also choose when a paywall appears: on app open, after onboarding, when a user triggers an event, or when they land on a feature. The goal is to test and ship the best fit for each audience, insight, and placement without code changes or app updates.
Build a paywall without code or app updates
Start from a template or a blank canvas in a WYSIWYG editor. Developers and marketers can adjust layout, copy, and offers, then publish. Because the paywall is configured remotely, changes do not require a new app release. This is the same editor used for the broader paywall feature; targeting decides which configured paywall a given user receives.
Choose a targeting dimension
Use the dimension that matches the question you are trying to answer. A short decision checklist:
- Country or local market — adapt the presence, duration, and pricing of offers to local preferences.
- Platform — iOS and Android users differ in behavior, preferences, and device capabilities.
- App version — show a paywall only to users on a version that supports it.
- Custom attributes — group users by demographics, feature usage, or other data you define.
- Feature use — react to a first workout or first journal entry with a paywall that highlights related features.
- Feature gate — when a user tries a locked feature, present a personalized paywall.
- Onboarding moment — compare an offer shown immediately on app open against one shown after onboarding.
Feature use vs. feature gate: a useful distinction
These two dimensions sound similar but answer different questions. Feature use is about a completed or initiated action — a first workout, a first journal entry — and the paywall can highlight features related to that action. Feature gate is about a locked capability — the user tries to use something they do not yet have access to, and the paywall explains or offers the upgrade. Use feature use to reinforce momentum; use feature gate to remove a specific blocker.
Test and measure the full funnel
Run A/B/n tests to find which paywall performs best with a target audience. Look beyond the initial conversion: pre-built data visualizations and predictive analytics help show how a test affects the full subscription funnel. Pair targeting with experiments so a segmentation rule is backed by observed outcomes rather than assumption.
Connected growth tools
Targeting sits alongside other monetization tools. Paywalls provide native templates or remote configuration via metadata. Experiments test the impact of changing a paywall variable. Funnels add no-code web-to-app journeys with built-in testing. Together they support revenue and subscriber-retention work across the subscription lifecycle.
Frequently asked questions
How is targeting different from running an experiment?
Targeting decides which paywall a user sees based on rules such as country, platform, app version, custom attribute, or feature moment. Experiments compare variants to measure impact. You can use targeting to define an audience and experiments to test which paywall performs best for that audience.
Do I need to ship a new app version to change a paywall?
No. Paywalls are configured and published remotely, so changes do not require a new app release. App version can still be used as a targeting dimension when you want to limit a paywall to users on a specific build.
What can I use as a custom attribute?
You define the attributes. Common examples include demographics and feature usage. Ready-made filters also cover country, app platform, and app version.
When can a targeted paywall appear?
Examples include on app open, after onboarding, when a user triggers an event, when a user lands on a feature, when a user completes a first action such as a workout or journal entry, and when a user tries to use a locked feature.