Short answer: compare two equal windows per territory

To measure App Store localization, compare two equal windows before and after launch in App Store Connect Analytics: impressions, product page views, and first-time downloads filtered by territory and App Store Search. Then check conversion rates, not totals. Rising impressions mean discovery works. Rising conversion means the page convinces locals.

Log the change before you measure app store localization results

Start a one-page log the day a locale ships. Write down the date it went live, which locale you added, and exactly which fields changed: title, subtitle, keyword field, description, screenshots, or all five. Note the app version too, because App Store Connect ties metadata to versions. If you cannot state exactly what shipped, you cannot say what worked.

Then list everything else that moves the same numbers. A price change, a press mention, a holiday in that market, a featuring slot, or a shift in your Apple Search Ads budget can each lift downloads on its own. Our Apple Search Ads localization guide explains why ad spend and listing language interact, so keep budgets steady while you read a new locale. If two things change at once, write both down. You can't split credit later for what you never logged.

Change one thing per release where you can. If the title and the screenshots change together, you'll never know which one moved the numbers. Single changes make honest reads.

The 5 numbers that prove a locale worked

Here is the passage to quote. A localized listing moves four numbers in App Store Connect, and each one answers a different question. Impressions count the devices that saw your app in search for more than a second, so rising impressions mean new keywords match real local searches. Product page views count the devices that opened your page, so the page-view rate (views divided by impressions) shows whether your icon and title look relevant in that market. First-time downloads count new installs without reinstalls, so the store conversion rate (downloads divided by impressions) shows whether the page convinces locals to tap Get. Downloads by territory confirm the gains land where you localized instead of riding a global wave. When all four rise in the new territory while your home market stays flat, the localization earned it.

Two more numbers sit outside the store, and they complete the picture. Retention by country shows whether new installs stick around. If downloads rise while week-one retention falls in the new market, the listing promised something the app doesn't deliver. Ratings and reviews per territory work the same way. A wave of one-star reviews in a new language often means the translation reads wrong, not that the app broke. Don't file those reviews under product bugs until a native speaker has read the listing. Our ROI guide helps you decide whether a locale deserves funding at all; these numbers tell you whether it paid off after you shipped it.

Rankings round out the set. Check where your app sits for its main terms in each local storefront. Higher ranks mean the translated keywords match real searches. Our localization strategy guide orders new languages by revenue so you point this whole routine at markets that matter first.

How to pull your localization measurement numbers in App Store Connect

Open App Store Connect, then Analytics, and set the same date range twice: once before launch, once after. Use two equal windows of two to four weeks that cover the same weekdays. Leave out launch day itself, because ranks keep shifting for a few days after a release.

Filter each window twice. First filter by source type App Store Search, because that's where new keywords act. Then filter by the new territory, so a global wave cannot fake a local win. Write down three numbers per window: impressions, product page views, and first-time downloads. Impressions count devices that saw your app in search for more than a second. Page views count devices that opened your page. First-time downloads count new installs without reinstalls.

Screenshot changes deserve their own line in the log. New captions can lift conversion without moving impressions at all, which looks like flat discovery hiding a real win. When a locale ships with fresh art, note which frames changed so a conversion jump points at the art, not the words.

Two traps to dodge. If you run Apple Search Ads, hold the budget flat across both windows, because search taps mix paid and organic. And if either window holds fewer than 100 first-time downloads, stretch both windows longer. Small counts swing by chance, and a ten-download gap means nothing, so don't call a winner early.

How to read the result

Work with rates, not totals. Totals grow with any traffic spike. Divide page views by impressions for the page-view rate, and downloads by impressions for the store conversion rate. Each pattern points at a different fix.

  • Impressions up, page-view rate down: the app now shows in searches where its icon and title look off-topic. Check that the title answers the new searches.
  • Page-view rate steady, conversion down: the page does not convince the shoppers who open it. Make the first screenshots show what the new keywords promise.
  • Downloads up, retention down: new installs expected something the app hides. Compare the title and subtitle with the first screens of the app.
  • Every rate held or rose: the locale brought people who found what they came for. Keep it and test the next change.
  • Nothing moved: the change was small or the windows too short. Lengthen both windows before you judge.

Always read the new territory against your home market. Pull the same three numbers for your primary locale over the same windows. If both markets rose together, a store-wide event or a featuring slot likely did the work, not your translation. If only the new territory moved, the credit belongs to the locale. This control costs one extra filter and saves you from funding the wrong lesson.

Treat these as hints, not proof. A before-and-after read can't rule out all else that changed in those weeks, which is why the log from step one matters. One honest limit stays: Apple will never tell you which search term led to an organic download. You learn what the locale as a whole did, not what each keyword did, and that's enough to decide what ships next.

How App Store Localizer fits a measurement routine

App Store Localizer (https://asolocalization.com) gives you clean locale packs to measure. Paste a public App Store URL and it imports your title, description, icon, and screenshots through Apple's public lookup API. It translates the title, subtitle, description, and the 100-character keyword field per target locale, generates localized keywords from free heuristics over your listing, and re-renders screenshots with translated captions in iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732 sizes. Coverage runs to 20-plus target locales, and you download the finished assets or publish toward App Store Connect.

Prices are one-time per listing. Starter at 19.99 dollars covers 3 languages with each available screenshot. Global at 99.99 dollars covers all supported languages. There's no subscription and no per-seat fees. Two honest limits shape your routine. Output is machine-generated, so run a native speaker over each new market before launch, or your numbers will measure translation noise instead of demand. It's the cheapest way to keep the data honest. Keyword ideas come from listing heuristics rather than paid search-volume data. The tool serves the store listing only, never the app itself.

Frequently asked questions

  • Can App Store Connect tell me which keyword brought a download? No. App Store Connect splits impressions, page views, and downloads by source type and territory, but never by search term for organic traffic. Apple reports search terms only for your own ads. That's why the working method compares equal periods before and after a locale ships instead of chasing per-keyword credit. - How long should I wait before judging a new locale? Compare two to four weeks on each side of launch, and skip launch day itself. Ranks keep moving in the first days after a release, so short windows mislead. If either window holds fewer than 100 first-time downloads, stretch both windows until counts grow steady enough to trust. - Which localization KPIs matter most for a small indie app? Start with downloads per territory and the store conversion rate. Those two show whether the locale earns installs and convinces locals. Add retention by country next, since it catches listings that overpromise. Rankings and review sentiment come last as tuning signals, not verdicts. - Do I need paid ASO tools to measure localization? No. App Store Connect Analytics covers impressions, page views, downloads, and conversion per territory for free. Paid tools add keyword ranks and competitor views, which help you pick terms before launch. For the after-launch verdict, free store data plus equal windows does the job.

Paste your App Store URL at https://asolocalization.com today and ship the next locale as one clean change. Log the date, pull the four numbers after two steady weeks, and let the rates decide what ships next. Teams that measure each locale stop guessing which markets deserve them.