Skip to content
AppDues
Log in
Contact salesSign up

Offering Targeting Ideas: Customize Paywalls by Country, Platform, App Version, and Attribute

A single paywall cannot serve every user equally well. Targeting lets you present a different Offering depending on where a user is, which platform they are on, which app or SDK version they run, where in the product they see the paywall, or a custom attribute you have stored about them. This guide collects practical starting points, then shows how to check whether each one worked.

Why segment Offerings at all

Personalization is not decoration. It is a way to match price, trial length, feature emphasis, and layout to the conditions a user actually faces. Targeting applies to every element of the paywall and to the placement where it appears, so the same app can present a different commercial proposition to a Brazilian first-time visitor, an Android user on a long trial, or someone still running an older build.

The ideas below are starting points for experiments, not universal winners. Each one needs a measurement plan before you ship it.

Target by country

Country-level targeting lets you align an Offering with local purchasing power, preferences, and feature availability. Four levers are worth testing:

  • Trial shape. Decide per market whether to offer a trial at all, how long it should run, and what it costs. A longer trial can win in one region while a shorter trial packed with more features converts better in another.
  • Feature emphasis. Lead the paywall with the bundle that fits local habits or trends instead of repeating a single global feature list in every market.
  • Paywall design. Adjust layout and visuals to match local cultural taste, and if you show testimonials, choose ones that speak to that country.
  • Plan structure. Compare monthly, quarterly, and yearly terms, and weigh one-time purchases where subscription auto-renewal is hard for users.

A useful caution comes from a pricing webinar with Keya Patel, then Director of Product Management, Growth at Headspace. Headspace had already lowered prices in some markets but still met cultural resistance to mindfulness and mental-health concepts. The lesson: when a market underperforms, check whether the barrier is price or messaging before cutting further.

Localized pricing: a worked example

Purchasing-power indexes such as the Big Mac index can suggest a starting band, but your own funnel data should decide where to test. A low new-to-trial or trial-to-paid rate is a signal that a lower price point may be worth trying.

Video-editing app Mojo raised yearly pricing in some countries, including the US and Germany, by 50% for new users and reported minimal adverse effect on free-to-paid conversion. It also reduced prices in other countries such as Brazil, with both short- and long-term benefits. Treat these as dated, app-specific results rather than a template: the transferable method is to pair an external index with your internal conversion metrics, then test one country at a time.

Target by platform

iOS and Android audiences differ in behavior, preference, and device capability, so the same Offering does not have to serve both.

  • Android: if users tend to be price-sensitive, extend the introductory window — a longer trial or a reduced rate for the first months. Combining a short free trial with a discounted period can ease users toward the full price step by step.
  • iOS: broaden the package mix — for instance, add a lifetime option for users ready to commit long term — and make the annual plan incentive more attractive.

These are hypotheses to test against your own platform-level conversion, not fixed rules.

Target by app version

Version targeting keeps each user's offer consistent with what their build can actually do.

  • New versions: offer trials tied to features that only exist in the latest build, and pair this with a customer-messaging integration for personalized prompts.
  • Older versions: present simpler plans built around core features that still work, and use the paywall to explain what upgrading would unlock.
  • Sunsetting: when phasing out an old version, consider a one-time incentive, such as a discount on the first month of a newer tier.
  • Paywall footer consistency: if you use Paywalls, Display Methods lets you pair a pre-built purchase component such as a footer with your own design. Targeting by app version keeps the footer matched to the design the user is seeing.

Target by SDK version

Paywall templates have compatibility requirements. Targeting by SDK version lets you show a template that matches what the installed SDK supports, which avoids falling back to a default template on older clients and keeps the paywall experience consistent across segments.

Target by in-product placement

Where and when a paywall appears matters as much as what it says. Three placements are worth testing:

  • At a gated feature. Show a paywall that explains the value of the specific premium feature the user just reached.
  • During onboarding. Test before, during, and after onboarding. Many teams are more cautious than necessary; most users are accustomed to seeing paywalls. Panic-attack relief app Rootd reported a 5x revenue increase after moving its paywall near the start of onboarding.
  • After a specific action. Trigger an offer once a user completes a task or opens the app a set number of times, when engagement is already high.

Target by custom attribute

Attributes store structured information about a customer, and you decide which ones drive personalization. Useful candidates:

  • Feature usage: when a user leans on particular features, put those front and center in the offer. Reflecting the content they already engage with both confirms their interest and nudges conversion.
  • Demographics: tune messaging, offers, and pricing to the group — student discounts are one example — and match paywall imagery to the user's age group and gender. Onboarding is a natural place to collect much of this data.
  • Stated goals and interests: use onboarding survey answers to show a paywall aligned with the goals or interests the user named. The change need not be elaborate — Babbel, for example, adjusts its paywall headline to the user's learning goal.
  • Referral source: tailor the offer to how a user found the app. If they arrive via a partner link, reflect that referral's terms — special pricing or exclusive features — so the offer feels personal and tied to their entry point.
  • Prior paywall views: if a user has seen a paywall but not subscribed, change the design, messaging, or offer. This lets you build a story over successive visits.

How to check whether targeting worked

Segment Charts by Offering to compare how each targeted group responds. The charts you can segment this way include:

  • Active Trials and Active Subscriptions — uptake per Offering.
  • Churn, Refund Rate, and Subscription Retention — longevity and satisfaction.
  • Revenue Metrics (ARR and MRR) — financial impact.

Segmenting by Offering shows which strategies resonate and where to adjust. Without that step, a targeting change is just a guess.

A starting checklist

Use this sequence to pick your first segment and keep the test honest:

  1. Choose one segment dimension — country, platform, app version, SDK version, placement, or a custom attribute. Changing several at once makes results hard to read.
  2. Write the hypothesis — for example, "a longer Android trial will lift trial starts without hurting trial-to-paid."
  3. Define the Offering change — price, duration, trial, feature emphasis, or layout. Keep the change small enough to attribute.
  4. Confirm compatibility — check that the build and SDK version in the segment can render the Offering and paywall you plan to show.
  5. Set the success metric — pick from the Charts list above before launch.
  6. Compare against a control — segment by Offering so the targeted group and the baseline are visible side by side.
  7. Decide and document — roll forward, roll back, or iterate, and record the result so the next test starts from evidence.
Segment dimension to first test
SegmentWhat you can varyFirst test to considerWhat to watch
CountryTrial presence, length, price; feature bundle; layout; plan duration; one-time vs subscriptionLocalized price band informed by a purchasing-power index plus your own conversion rateNew-to-trial and trial-to-paid by country
Platform (Android)Length of introductory offer; stacked trial-then-discount structureExtended trial or discounted first monthsTrial starts and conversion to full price
Platform (iOS)Package mix including lifetime; annual incentivesAdd a lifetime option or a stronger annual discountTake-up of longer-term plans
App versionFeature-linked trials; simplified plans; upgrade prompts; paywall footerSimpler plan for older builds with an upgrade pathUpgrade rate and retention on old builds
SDK versionPaywall template compatibilityMatch template to installed SDK versionFallback-to-default rate
In-product placementGated feature, onboarding timing, post-action triggerMove paywall earlier in onboardingRevenue and conversion by placement
Custom attributeFeature emphasis, demographics, stated goals, referral terms, prior paywall viewsHeadline matched to onboarding-stated goalConversion by attribute value

The segment-to-test pairings are suggested starting points drawn from the ideas above. They are not tested recommendations for any specific app; validate each against your own Charts data.

Frequently asked questions

What can I target an Offering by?

Country, platform, app version, SDK version, in-product placement, and custom attributes you store about the customer.

How do I know if a market needs lower pricing or different messaging?

Check your own funnel first. A low new-to-trial or trial-to-paid rate points toward a price test. If conversion stays flat after a price change, the barrier may be messaging or feature fit — the situation Headspace described when cultural attitudes toward mindfulness limited uptake despite lower prices.

Why target by SDK version separately from app version?

They answer different questions. App version targeting matches the offer to the features a build supports. SDK version targeting matches the paywall template to what the installed SDK can render, so older clients do not fall back to a default template.

Which metrics should I compare across targeted Offerings?

Active Trials, Active Subscriptions, Churn, Refund Rate, Subscription Retention, ARR, and MRR. Charts can be segmented by Offering so each targeted group is visible.