NewThe guide: 11 paywall examples

11 minutes

Pricing localization: the test you should run first

Locale tests have an LTV success rate of 62.3%, versus 45.5% for price tests, according to Adapty. Translating the paywall and adapting price by market comes before the price test.

Clément Parot

Pricing localization: the test you should run first

Article summary

  • 62.3% of locale tests improve LTV, versus 45.5% of price tests and 34.6% of visual tests. That is a success rate, not an automatic revenue gain.
  • Translating the paywall of the 5 main markets generates 37% more LTV than a price test alone.
  • Adapty's order then places trial structure at a 59.6% success rate, the number of plans at 57.1%, then price.
  • European apps charge 29 to 39% more than North American ones. The monthly gap went from 6% in 2023 to 39% in 2025.
  • The pricing index puts Switzerland, Norway, Sweden, and Denmark at 1.4 to 1.6 times the US, France and its neighbors at 1.2 times, and India at 0.6 times.

Summarize this article with

⚠️ Warning: Most teams that want to increase revenue start by testing price. It is the most documented mistake in 2026 mobile monetization data.

Price tests have an LTV success rate of 45.5% according to Adapty. Locale tests, translation of the paywall and pricing adapted by market, have a success rate of 62.3%. That is not a marginal gap. It is the difference between the least effective lever and the most effective lever on your entire experimentation roadmap.

firstapp works with founders on the monetization of their apps. What the 2026 data says about localization is among the least known information in the French-speaking market, and among the most actionable.

Why pricing is not the first lever to test

It is counterintuitive because price is the most visible and most accessible variable. A price change ships in a few minutes. It produces measurable results quickly. And everyone has an intuition about "the right price."

That is precisely why it is the lever everyone tests first, and the least effective one.

According to Adapty (State of In-App Subscriptions 2026, 16,000+ apps, $3 billion in revenue analyzed), here is the LTV success rate by experiment type:

  • Locale tests: 62.3%
  • Trial structure tests: 59.6%
  • Number-of-plans tests: 57.1%
  • Price tests: 45.5%
  • Visual and copy-only tests: 34.6%

Price is second to last. Purely visual tests are last. Localization is first.

Adapty states the conclusion without ambiguity: "If your experimentation roadmap is built around design iterations and price tests, you are testing the wrong layer first. Structure before aesthetics. Localization before price."

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week

What localization actually covers

Pricing localization is not just translating your app into several languages. It is two distinct interventions that can be done independently.

Content localization

Translating your paywall into the languages of your main markets. Not the whole app. The paywall. It is the most critical screen in the user journey, and it is often the last one to be localized.

A Brazilian user who sees a paywall in English has to make an extra cognitive effort at the exact moment you ask them to pay. That effort reduces conversion. Translating the paywall removes that friction without changing either the price or the structure.

💡 Key figure: According to Adapty 2026 data, translating your paywall into the languages of your 5 main markets generates 37% more LTV than a price test alone. More impact for less effort.

Price localization

Adapting the price level to local purchasing power. A subscription at $9.99/month is affordable for an American or Swiss user. It is a significant barrier for an Indian or Brazilian user. And it probably underprices the European market, which accepts prices 29 to 39% higher than North American apps according to Adapty 2026.

The difference in willingness to pay can be 2 to 3 times between two countries according to Adapty 2025 data. Applying a single global price means undercharging your best markets and overcharging your emerging markets at the same time.

These two interventions have different implementations and can be tested separately. Content localization is often faster to ship. Price localization requires configuration in App Store Connect and Google Play Console, plus a prior analysis of your geographic distribution.

62.3% LTV uplift: what the data says

This figure deserves context.

62.3% LTV uplift does not mean that every locale test generates 62.3% more revenue. It means that 62.3% of locale tests launched in the Adapty dataset (16,000+ apps) produce an improvement in LTV. It is the highest success rate of every experimentation category.

For comparison: design and copy tests have a success rate of 34.6%. Fewer than one test in three improves LTV. A locale test is statistically almost 2 times more likely to produce a positive result than a visual test.

The structural reason: localization solves a real problem of friction or of price-to-market fit. Design solves a presentation problem. Friction has more impact on conversion than presentation.

Europe is the most documented case. European apps now charge 29 to 39% more than North American apps across every plan type. The monthly gap went from 6% in 2023 to 39% in 2025 ($15.25 vs $10.95). Europe is also the region with the best annual retention at D380 (21.3% versus 20.0% for North America). Users who pay more and stay longer.

If you apply US prices on your European markets, you are undercharging users who would willingly pay more. That is a direct loss of revenue with nothing in return.

The test order recommended by the data

Adapty explicitly states the order in which experiments should be launched to maximize the ROI of your roadmap:

PriorityTest typeLTV success ratePotential impact
1Locale tests (translation + local pricing)62.3%High
2Trial structure (length, gates)59.6%High
3Number of plans57.1%Medium to high
4Price45.5%Medium
5Visuals and copy34.6%Low to medium

Source: Adapty State of In-App Subscriptions 2026

This table puts most optimization roadmaps in perspective. Teams often start at the bottom of the table (visuals, price) and never reach the top (localization, structure). The data says to do the reverse.

A structure test, 2 plans vs 3 plans, generates 63% more conversion-rate uplift than a price test alone. A locale test generates 37% more LTV than a price test. Price is the most intuitive lever and the least effective. That is not a reason not to test it. It is a reason to test it last, not first.

To go further on the 6 structural decisions of the paywall, localization is the fourth variable in the optimization order.

The pricing index by country in 2026

Adapty publishes a pricing index relative to the US market (base 1.0). This data lets you quickly see whether you are below or above the market in your main countries.

Country / regionPricing index (US = 1.0)
🇨🇭 Switzerland, 🇳🇴 Norway, 🇸🇪 Sweden, 🇩🇰 Denmark1.4 to 1.6x
🇬🇧 United Kingdom, 🇫🇷 France, 🇩🇪 Germany, 🇮🇹 Italy, 🇪🇸 Spain1.2x
🇺🇸 United States (reference)1.0x
🇨🇦 Canada, 🇧🇷 Brazil, 🇦🇷 Argentina, 🇶🇦 Qatar, 🇰🇷 South Korea, 🇦🇪 UAE0.9x
🇹🇷 Turkey0.7x
🇮🇳 India0.6x

Source: Adapty State of In-App Subscriptions 2026 - US = base 1.0

This table has two readings.

First, if you are a French app with users mostly in France, the UK, Germany, and Spain, your pricing should be at 1.2x the US market. If you use identical US prices, you are structurally below the market.

Second, if you have significant volume in India or Turkey at US prices, your conversion rate is probably penalized by pricing that does not fit local purchasing power. Adapting the price to 0.6x–0.7x the US price in those markets can significantly increase conversion volume without affecting your revenue on the main markets.

Switzerland is the extreme case: with a median LTV of $28.5 versus $19.9 for the US (Adapty 2026), Swiss users generate 43% more revenue per user. If you charge the same price in Switzerland and in the US, you leave that extra value on the table.

How to implement a locale test

The technical implementation depends on your monetization stack, but the steps are the same for everyone.

Step 1: identify your 5 main markets by revenue volume

Not by install volume. By revenue. Your 5 highest-revenue markets are the ones to localize first. The information is available in App Store Connect (Sales and Trends) and Google Play Console (Financial reports).

Step 2: translate your paywall into the languages of those markets

This is often the fastest change to ship. Paywall SDKs such as Superwall, Purchasely, or Adapty let you configure paywalls localized by language without touching the code. For an app managed with RevenueCat, localized paywalls are configured directly in the dashboard.

Elements to translate first: the paywall headline, the plan descriptions, the CTA button, the reassurance elements (trial terms, cancellation policy). Not necessarily the whole app at first.

Step 3: configure local pricing

In App Store Connect: Pricing and Availability tab, Availability section, then customize the price by territory. Apple offers suggested prices by territory based on exchange rates and local reference prices.

In Google Play Console: Monetize tab, Subscriptions section, then edit the price by country. Google allows custom prices by country with no automatic conversion constraint.

Start with your 3 to 5 main markets. An A/B test of localized pricing versus global pricing in those markets will give you statistically significant data in 2 to 4 weeks depending on your volume.

Step 4: measure the right indicators

The install-to-trial conversion rate in each market before and after. Trial-to-paid in each market. LTV at 30 and 90 days by market. These three metrics together give you a complete picture of localization's impact on your product economics.

Do not measure only the immediate conversion rate. A lower localized price in an emerging market can increase conversion volume while reducing revenue per subscriber. LTV at 90 days is the metric that decides.

FAQ

What is pricing localization for a mobile app?

Pricing localization covers two distinct interventions: translating the paywall and the conversion screens into the languages of the main markets, and adapting the price level to local purchasing power. These two interventions can be done independently. Translating the paywall is often faster to ship and generates an immediate impact on conversion. Adapting the price requires configuration in App Store Connect and Google Play Console and an A/B test to validate the impact on LTV.

Why do locale tests have the best ROI?

Because they solve a structural problem of friction or of price-to-market mismatch, not a presentation problem. A user who sees a paywall in a foreign language at the moment of paying, or a price that does not fit their purchasing power, hits a real barrier to conversion. Removing that barrier has a stronger impact than optimizing design or copy, which acts on a smaller friction. That is what the Adapty 2026 data explains: 62.3% of locale tests produce an LTV improvement, versus 34.6% for visual tests.

Which markets should you start localizing?

Your 5 markets that currently generate the most revenue, not those that generate the most installs. If you are a French app, the priority markets are typically France, Belgium, Switzerland, the UK, and Germany for the European dimension. Start by translating the paywall into those languages, then adjust pricing according to the Adapty reference index (UK, France, Germany, Italy, Spain at 1.2x vs the US baseline).

Should you lower prices in emerging markets?

Yes, if you want to convert in those markets. The difference in willingness to pay can be 2 to 3 times between India (index 0.6x) and the US (1.0x) or Europe (1.2x). Applying a US price in India structurally overcharges a market with high volume potential. Lowering the price to 60% of the US price in that market can significantly increase conversion volume. LTV per subscriber will be lower, but total revenue can rise thanks to volume. Measure LTV at 90 days to decide.

Does localization replace price tests?

No. Localization comes before price tests in the priority order recommended by Adapty, but the two are complementary. Once localization is in place, testing the price level in each localized market becomes relevant. What does not work: testing the global price before you have localized, because a global price test hides very different dynamics by market. A price that converts well in France can fail in India, and the reverse. Localization has to come before the price test so the results can be read market by market.

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week