P
Priya the Plateaued
Persona · Custom Product Pages / Listing experimentation
Chapter 1 of 6 · Microsoft Store Discoverability
WHOSE PAIN

Meet Priya,
the Plateaued.

Established indie. FocusDrop Timer shipped 3 years ago. 50,000 installs. Growth flatlined for 6 months. She has the data, the audience, and ideas to test. What she doesn't have is a way to iterate on her listing without shipping a new build.

3yr live on Store
50K installs
Growth flat 6 mo
4.4★ · 312 reviews
Priya · mid-stage indie dev · solo PM + dev
feeling: stuck, has hypotheses she can't test
Priya's iteration backlog · this week
Mon
Swap lead screenshot — current one is 3 years old, taken on old Surface.
Tue
Test a sharper tagline: "Focus on what matters" vs current "A simple timer for deep work".
Wed
Try a variant aimed at students for searches like "pomodoro" / "study timer".
Thu
Try a variant aimed at remote workers for "deep work" / "calendar block".
Fri
See which variant won — keep the winner, learn from the loser.
Reality
Microsoft Store gives her one Product Page Experiment slot at a time, and only lets her vary the logo and screenshots — not the tagline, description, or keywords she actually wants to test.
THE PAIN

"I tried A/B testing.
I stopped."

"I tried to do some A/B testing, but I don't know, that didn't give me good results, so I stopped doing that." — Dave Smits, established Microsoft Store dev · VoD Pulse, 4 June 2026

Priya — and devs like her — opened the one experimentation tool Microsoft Store actually ships (Product Page Experiments), tried it once, didn't trust the result, and walked away. The pain isn't "I want a feature you don't have." It's "I used the feature you do have, and it failed me."

1 active experiment per app
Vary logo + screenshots only
90-day max duration
No targeting — one global audience
VOD PULSE · Sep 2025
"The A/B testing in Partner Center is too limited. One variant, fixed split, and you wait three months for a result you can't trust."
Productivity app dev · synthesised from VoD Pulse Q3'25 free-text responses
REDDIT · r/microsoftdevs
"Why can I change my logo OR my screenshots in an experiment but not both? I want to test a whole new positioning."
Synthesised from recurring complaints across r/microsoftdevs, MS Q&A "Product Page Experiments" tag (12 threads, Jan–May 2026)
VOD PULSE · 4 June 2026 · verbatim
"I tried to do some A/B testing, but I don't know, that didn't give me good results, so I stopped doing that."
Dave Smits, established MS Store dev · VoD Pulse interview
WHY SHE STOPPED

The PPE box has
four walls.

Microsoft Store does ship a listing-experimentation feature — Product Page Experiments (PPE). It's not absent. It's just structurally too narrow to test the hypotheses Priya actually has.

Here's what PPE lets her change — and everything it doesn't:

Wall 1 · Variants
1 active
Apple CPP: up to 35 · Google CSL: up to 50
Wall 2 · What you can vary
Logo + screenshots only
Not tagline. Not description. Not keywords. Not category. Not "What's new". Apple & Google let you vary every asset including text.
Wall 3 · Targeting
One global audience
No country, language, keyword, device, or install-state targeting. Same variant served to every user worldwide.
Wall 4 · Duration
90 days max
Then it auto-stops, winner-or-not. Cert required to start the next one.
Microsoft Partner Center · New Product Page ExperimentThe whole variant configuration surface — June 2026
Microsoft Partner Center new product page experiment screen. Variant configuration section shows two upload areas: Logo (poster art and 1:1 app tile icon) and Screenshots (up to 10). No fields for tagline, description, keywords, category, or any text variation.
What this screen does NOT have
No tagline field. No description field. No keyword field. No category override. No "What's new" override. No country / language / keyword targeting. No traffic-split control. The whole experiment surface is two image upload boxes.
APPLE SHIPS IT. GOOGLE SHIPS IT.

Apple ships a page per keyword.
Google ships 181 countries of peer-benchmarked data.
We ship two image upload boxes.

developer.apple.com/app-store/custom-product-pages · keyword binding
Apple App Store search result for 'tracking outdoor training' surfacing a Custom Product Page with workout-specific screenshots
A different page per search keyword.
When a user searches "tracking outdoor training", Apple surfaces a Custom Product Page whose screenshots match. 35 CPPs per app, each bindable to a specific search keyword.
appstoreconnect.apple.com · Analytics · Product Page Optimization
Apple PPO analytics — 8.62% overall CR for one CPP, with Forest Explorer referrer 13.89% vs Mountain Climber 5.24%
Same page. Two referrers. Two stories.
Conversion for one CPP: 13.89% via "Forest Explorer" referrer, 5.24% via "Mountain Climber" — aggregating to 8.62%. Broken by Referrer × Product Page × Platform × Territory × Device.
play.google.com/console · Store listing · Search-term acquisitions
Google Play Console 'Choose what to plot' with per-search-term acquisitions: 'get me solutions' 183,749 installs, 'get me technologies' 91,466
Acquisitions broken by exact search term.
A real Android dev sees "get me solutions" 183,749 installs, "get me technologies" 91,466, "get me software" 1,401 — pulled from Google Play search. Tells her which queries to optimise her listing for.
play.google.com/console · Conversion analysis · By language
Google Play Console conversion by language across 93 languages with peer median benchmarks
CR vs peer median for every language she ships in.
English-US 44.31%, Hindi 43.39%, Gujarati 45.94% (+23.72% vs Sports peer median). 93 languages, each with a green/red delta against the category benchmark.
play.google.com/console · Conversion analysis · By country
Google Play Console conversion analysis across 181 countries with per-country CR vs Sports peer-group median
CR vs peer median, across every country she's live in.
India 43.75% (+25% vs peers), Pakistan 45.75% (+23.5%), UAE 33.47% (−4.71% vs peers, red). 181 countries, each with a benchmark — tells her where to invest in localised listings.
play.google.com/console · Promotional content reports
Google Play Console promotional content report for BGMS X Rooter event: 4.35M viewers, 924 converters, 0.02% CR, broken across 176 countries
Events get their own analytics layer.
"BGMS X Rooter" promotional event: 4.35M viewers, 924 converters, broken by Acquisitions / Opens / Updates × 176 countries, rolling 28-day window. Microsoft Store has no concept of a promotional event tied to listing analytics.
partner.microsoft.com/dashboard · Product page experiment · New
Microsoft Partner Center new Product Page Experiment screen — variant configuration is two upload boxes: Logo and Screenshots. No fields for tagline, description, keywords, category, or targeting.
Logo + screenshots. One global audience.
1 active experiment per app. The variant configuration surface is two image upload boxes — no tagline, no description, no keywords, no category, no "What's new" override. No country, language, keyword, device, or install-state targeting. Cert required to start the next one.
Apple App Store
35
listing variants per app
+ 3 live A/B treatments
Google Play
50
custom store listings per app
(100 for partner accounts)
Microsoft Store
1
product page experiment
at any one time
Targeting — who sees the variant
Bind variant to search keyword
✓
✓
✗
Target by country / language
✓
✓
✗
Vary text (tagline, description, keywords)
✓
✓
✗
Analytics — what she learns from it
CR broken by referrer × device × territory
✓
◐
✗
Revenue / proceeds per variant
✓
◐
✗
Per-country / per-language CR vs peer median
✗
✓
✗
Cohort retention (D1–D60) per variant
✓
✓
✗
Friction — how easily she can iterate
No re-cert needed to start a variant
✓
✓
✗
LLM tags / AI review summary on page
✓
◐
✗
IF WE GAVE PRIYA THIS TOMORROW

Three moves.
No new code in her app.

Move 1 Decouple
Listing edits ship in hours.
Text, screenshots, tagline, "What's new" → review-only path, not full binary re-cert. Apple & Google did this years ago.
Move 2 Lift the walls
10+ variants. Targeting. Anything.
Vary icon + screenshots + tagline + description together. Target by country, language, keyword. Flexible traffic splits.
Move 3 Trust the data
Per-variant analytics she'll believe.
CR by referrer × country × device × keyword. Per-language CR vs peer median. Cohort retention per variant.

Roadmap · what ships when

P0 · NOW
Restore trust.
Audit & fix PPE data-layer bugs surfaced in dev tickets.
P1 · 1Q
Listing ≠ binary.
Text, screenshots, tagline → review-only path. Vary all assets together in PPE.
P2 · 2Q
Reach Google parity.
10+ variants. Country & language targeting. Per-variant breakdown analytics.
P3 · 3Q
Reach Apple bar.
Per-keyword variants. Peer-group CR benchmarks. AI-assisted tag & review summaries.
END-GOAL · DISCOVERY MET

Iteration → conversion →
a healthier Store.

+32%
CR uplift · MobileAction case study, CPP on a games portfolio
+15%
Install uplift · Koo, Google Play CSL targeted by language
+8%
Install uplift · Pocket Gems, per-keyword CPP rollout
1.85×
Downloads · Apple "Biking-On the Trail" CPP vs default page

The compounding loop

1 · Priya iterates weekly
Listing changes ship in hours. 4 variants/month instead of 1/quarter.
2 · She finds variant winners
Real data per keyword / country / device. CR climbs 10–30% on the wins.
3 · Store gets fresher listings
Catalogue ages slower. Search relevance improves. Peer-benchmarks become real.
4 · Devs who left come back
MVPs trust the data layer again. r/microsoftdevs flips from "don't bother" to "this actually works now".