Custom Store Listings and the Certificate Exam

So far your listing has been one page for everyone. But the people who reach your app are not all the same. A student in Ibadan who clicked a school-newsletter link, a parent in Accra who searched "school fees tracker", and a lapsed user you want to win back each care about different things. Custom store listings (CSLs) let you show different versions of your Google Play page to different audiences, with a different message, screenshots and description for each.

This lesson is Module 4: Drive user acquisition through custom store listings of the Google Play Store Listing Certificate (https://playacademy.withgoogle.com/certificate), followed by practical guidance on preparing for the certificate exam. We teach the skills in our own words with our own examples. We have not seen the exam, we cannot reproduce it, and nothing here guarantees a pass.

Honesty note. Custom store listings are a changing feature: limits on the number of listings, targeting options and Console menu names are updated from time to time, and some options depend on your account or app. Where we quote a number, treat it as "at the time of writing" and check the current Play Console Help. Exam format, number of attempts, fees and renewal rules are set by Google Play Academy: read them on the certificate page, not from us.

By the end you will be able to:

• Explain what a custom store listing is and when it is worth the effort.
• Name the targeting options: country or region, user state (new, lapsed or returning), pre-registration, specific URLs and campaigns, and Google Ads.
• Plan a set of custom listings from an audience map.
• Create a custom listing in Play Console and link to it with the right URL.
• Combine custom listings with tracking and experiments to measure their effect.
• Avoid the policy mistakes specific to personalised listings.
• Build a study plan for the certificate exam and check your readiness with self-made practice questions.

Big idea: a custom listing is a tailored welcome. Everything in it must still be true, but it can lead with the aspect of your app that matters most to that visitor.

• Main store listing, assets and policies (lessons 50 and 52).
• Acquisition reports, conversion and experiments (lesson 51).
• Campaign links with referrer parameters (lesson 51).
• Consistent brand story (lesson 52).

Consider a shop on a busy road in Ibadan. A customer coming off a bus wants to know whether you sell phone chargers. A neighbour who comes every week wants to hear about the new stock. A person who has not visited for a year wants a reason to come back. A good shopkeeper greets each differently, and does not lie to any of them.

A custom store listing works the same way. It is an alternative version of your listing page that Google Play shows to a particular audience.

                      +-----------------------------------+
                      |  Default (main) store listing     |  everyone else
                      +-----------------------------------+
                         ^                   ^
  Google Play shows the best match for the visitor:
                         |                   |
   +---------------------+----+   +----------+----------------------+
   | Custom listing A         |   | Custom listing B                |
   | Ghana, English           |   | Lapsed users (not opened in a   |
   | cedi, mobile money story |   | while): "What's new: reports"   |
   +--------------------------+   +---------------------------------+
   +--------------------------+   +---------------------------------+
   | Custom listing C         |   | Custom listing D                |
   | URL for school newsletter|   | URL for Google Ads campaign     |
   | "Free for your school"   |   | matching the ad promise         |
   +--------------------------+   +---------------------------------+

What can differ between listings?

Typically you can vary the title? No: the app name and icon stay the same in custom listings (check the current rules), while you can change elements such as the short and full descriptions, the feature graphic, screenshots and promo video. Custom listings are about the message, not a different identity. Check the Help page for the exact list of changeable fields.

Why they work (and when they do not)

• Relevance raises conversion. A visitor who clicked an ad about "offline attendance" and lands on a page that leads with offline attendance sees the promise kept. This is called message match.
• Re-engagement. A user who left may return if the page shows what is new since they left.
• Pre-registration and launches. A custom listing can prepare early adopters.
• Effort versus reward. Every custom listing needs assets, translation, review and maintenance. If you have a handful of visitors, the effort is wasted. They pay off where you have meaningful traffic in a distinct segment that you can describe in one sentence.

Reported averages from Google (for example the figure in the 2023 course announcement on the Android Developers Blog) show positive effects on average, but your results will differ: test.

When you create a custom listing in the Console you choose who sees it. The exact options change; these are the main ideas.

A few rules that usually apply (verify in Help):

• Each custom listing has one targeting type or combination allowed by the Console, and when more than one listing matches a visitor, a documented priority decides which is shown.
• Listings targeting a country or user state are shown automatically to those users in places such as Google Play search and Explore. Listings targeting URLs are only shown to those who open that URL.
• There is a limit on how many custom listings an app can have, and that limit can differ by account type.
• A custom listing cannot be shown if the app is not published in the targeted country, or if the listing fails review.

Do not start in the Console. Start with a table. We will plan for Class Register (free attendance app).

Step 1: Map audiences

AUDIENCE MAP
ID  Audience                         Size (est.)   What they want                  Message
A   Teachers who click our school    medium        Trust, "free for schools"       Free for your school; no ads
    newsletter link
B   Visitors from Ghana (search)     large         Local relevance                 Works offline; cedi reports; mobile money
C   Lapsed installers                small         A reason to return              New: weekly reports and large text
D   Google Ads "offline attendance"  medium        What the ad promised            Offline attendance in one tap
E   Parents (view reports only)      medium        See my child's attendance       See attendance anywhere (needs a separate app/feature)

Step 2: Prioritise

Score each audience from 1 to 5 on size, message difference (how different the best message is from your default) and effort, then pick the top two or three.

        Size  Difference  Effort(low=5)  Total
A        3        3            5           11
B        5        4            3           12   <- do first
C        2        4            4           10
D        3        5            4           12   <- do first
E        3        4            1            8   (needs product work; skip for now)

Step 3: Write a brief for each

CUSTOM LISTING B: Ghana
Audience: visitors in Ghana (search + explore)
Goal: raise CVR from 9% (default) toward the Nigeria level (18%)
Hypothesis: showing cedi in screenshots and mentioning mobile money exports will increase trust
Changed fields: short description, full description (first paragraph), screenshots 1-3, feature graphic
Same: app name, icon, requirements, contact
Success metric: store listing CVR for Ghana visitors; compare with the previous 4 weeks
Review date: after 3 weeks

Step 4: Check truthfulness

Every claim in a custom listing must be true for that user and that app version. If the Ghana listing says "pay with mobile money", the app must really support it for users in Ghana. A custom listing that promises more than the app offers is a policy violation and a reason for one-star reviews.

The Console flow below is approximate; use the Help article "Create custom store listings" for the current screens.

1. Go to Grow users → Store presence → Custom store listings (or the equivalent).
2. Click Create listing. Give it an internal name only you see: GH-search-v1 (see naming below).
3. Choose the targeting: for example Country, and select Ghana.
4. Edit the content for each language you serve: short description, full description, graphics, screenshots, video.
5. Preview how it looks.
6. Save and publish the listing. It goes through review. Custom listing changes can be reviewed separately from app releases.
7. For URL-targeted listings, copy the listing URL. It is the normal Play link plus a parameter that identifies the listing. Use that URL in newsletters, posters (as a QR code), social posts or ad campaigns. Never guess or hand-edit the identifier; copy it from the Console.
8. Wait for traffic, then read the report (below).

Naming convention

A naming scheme makes reports readable six months later:

<AUDIENCE>-<CHANNEL>-<LANG>-v<N>

GH-search-en-v1       Ghana, organic search, English
NG-newsletter-en-v2   Nigeria school newsletter link, second version
LAPSED-all-en-v1      Lapsed users, all countries, English
ADS-offline-en-v3     Google Ads campaign "offline", third creative

Linking to a listing from a web page

For URL-targeted listings, you place the link on a page or in a QR code. A plain HTML button works:

<a href="https://play.google.com/store/apps/details?id=com.techbase.classregister&listing=ng-newsletter-en-v2">
  Get Class Register on Google Play
</a>

The listing= parameter here shows the idea of a listing identifier; the actual parameter name and value come from the Console's generated URL, so always copy that URL. You can make a QR code from the link with a free generator, or in Python with the qrcode library (pip install qrcode[pil]):

import qrcode
url = "PASTE_THE_URL_FROM_PLAY_CONSOLE_HERE"
img = qrcode.make(url)
img.save("ng-newsletter-qr.png")
print("saved ng-newsletter-qr.png")

Test the QR code on a real phone in the actual printed size and light before you print a thousand copies.

Without measurement, custom listings are decoration. The store listing acquisition report (lesson 51) can be filtered by custom store listing, so you can compare:

A comparison helper

Using the two-proportion test from lesson 51, a small function can say whether a custom listing's conversion is credibly different from the default over the same period:

from math import sqrt, erf
def compare(label, v_default, i_default, v_custom, i_custom):
pa, pb = i_default / v_default, i_custom / v_custom
pooled = (i_default + i_custom) / (v_default + v_custom)
se = sqrt(pooled * (1 - pooled) * (1 / v_default + 1 / v_custom))
z = (pb - pa) / se
p = 2 * (1 - 0.5 * (1 + erf(abs(z) / sqrt(2))))
verdict = "evidence of a difference" if p < 0.05 else "not enough evidence"
print(f"{label}: default {pa:.1%}, custom {pb:.1%}, p={p:.3f} -> {verdict}")
compare("Ghana search", 3000, 270, 3200, 400)
compare("Newsletter", 600, 168, 650, 190)

Output:
Ghana search: default 9.0%, custom 12.5%, p=0.000 -> evidence of a difference
Newsletter: default 28.0%, custom 29.2%, p=0.631 -> not enough evidence

(The first comparison, 9.0% to 12.5% over thousands of visitors, is clearly a real gain; the second, 28.0% to 29.2% on a few hundred visitors, could easily be luck.)

Caveat: custom listings and the default do not see randomised traffic the way an experiment does; the audiences differ (that is the point). A difference may come from the audience, not the page. To isolate the effect of wording, run a store listing experiment on the custom listing's elements where the Console allows it (lesson 51).

Close the loop

After a month, update the decision log: did the listing meet its goal? If yes, extend (more countries, new audience). If not, was it the message, the assets or the audience? Retire listings that do not earn their upkeep. Many small listings can become a maintenance burden whenever the app UI changes.

• Truth: every claim must be accurate for those users and the app they will install.
• Same app: a custom listing cannot promise a different app or hide important facts (price, subscription, data practices).
• Sensitive targeting: target by country, activity state and campaign, not by sensitive personal attributes. Do not use text that singles out users by health, religion, race or similar attributes in a way policy forbids.
• Do not impersonate another developer, or imply endorsement.
• Keep assets in sync: screenshots must match the current UI.
• Children's apps and sensitive categories have stricter listing rules.
• Accessibility: captions and graphics still need good contrast (lesson 47).
• Consistency of the in-app experience: if a listing promises a feature, the first-run experience should help the user find it.

The Google Play Store Listing Certificate is a free, self-paced course from Google Play Academy, followed by an exam. People who pass receive an industry-recognised certificate and can be invited to join the Google Developer Certification Directory (according to Google's own announcement). The course was first launched in 2021 and updated in 2023 with new modules on custom store listings and listing experiments, so check the current version.

What we can and cannot tell you

Read the certificate page (https://playacademy.withgoogle.com/certificate) for the exam format, how many times you can attempt it, how long a pass remains valid and any language options. Do the official modules in order; the lessons here are companions, not substitutes.

A study plan (two weeks, one hour a day)

DAY 1   Lesson 50 + official Module 1. Create a dummy listing (no publishing needed).
DAY 2   Lesson 50 exercises: write title/short/full, check limits, policy checklist.
DAY 3   Lesson 51 + official Module 2. Compute CVR for the sample table by hand.
DAY 4   Lesson 51: write a hypothesis and an experiment plan; use the z-test helper.
DAY 5   Review day: re-read policy sections; make flashcards for limits and terms.
DAY 6   Lesson 52 + official Module 3. Audit a competitor's listing with the scorecard.
DAY 7   Rest, or redo the audit on your own app.
DAY 8   Lesson 52: storyboard five screenshots; plan one localisation.
DAY 9   Lesson 53 + official Module 4. Draw your audience map.
DAY 10  Write two custom listing briefs; check each claim for truth.
DAY 11  Take the official study guides and videos for any weak area.
DAY 12  Self-quiz with the practice questions below, closed book.
DAY 13  Fix weak areas, reread the official course summary pages.
DAY 14  Sit the exam when you feel ready, in a quiet place with a stable connection.

Learn the vocabulary

Make flashcards for these (from all four modules):

Store listing; main store listing; custom store listing (CSL); default listing
Title, short description, full description; feature graphic; icon; screenshots; promo video
Store listing visitor; installer; conversion rate (CVR); retained installer
Traffic source (search, explore, third-party referral, ads); search term
Store listing experiment (A/B test); control; variant; confidence interval; audience %
Localisation; localised experiment; default graphics experiment
Targeting: country, user state (new, lapsed, returning), pre-registration, URL, Google Ads
Data safety; privacy policy; content rating; app access; policy status
Internal / closed / open testing; production; staged rollout; managed publishing

Exam technique

• Read each question twice; look for words such as "best", "first", "NOT".
• Eliminate clearly wrong options (those that break policy or promise guaranteed results).
• Prefer answers that are honest, user-focused and measurable. In this subject, the correct answer is rarely "stuff keywords", "fake reviews" or "change everything at once".
• Do not rush, but do not stall: flag and return.
• Know the numbers that matter from the Console (field lengths, image sizes) but verify them against the current Console, because exams are written from current guidance.
• Rest the night before; this is an understanding test, not a memory marathon.

After the exam

If you pass: add the certificate to your CV and LinkedIn with the date, and keep note of the renewal period on the certificate page. If you do not: use the feedback, review the weak modules and retake after any waiting period the rules require. Either way, the real goal is to run better listings, and you have the tools to do that.

Mistake #1: Making many listings with tiny differences. Symptom: heavy maintenance, no measurable result. Fix: only audiences with a clearly different message and enough traffic.

Mistake #2: Not copying the URL from the Console. Symptom: a link that shows the default listing. Fix: use the generated URL.

Mistake #3: Listings that over-promise. Fix: every claim true for that audience.

Mistake #4: Forgetting to update screenshots after a release. Fix: add listing review to the release checklist.

Mistake #5: Reading the comparison without a significance check. Fix: the helper or the Console's intervals.

Mistake #6: No naming convention. Fix: audience, channel, language, version.

Mistake #7: Sending a print campaign to an untested QR code. Fix: test on real phones.

Mistake #8: Studying only the exam. Fix: practise on real listings.

Mistake #9: Counting on the certificate to get installs. Fix: the certificate shows knowledge; installs come from a good app and listing.

Mistake #10: Quoting old limits. Fix: confirm in the Console.

Question 1. What is a custom store listing?

Question 2. Give three ways you can target a custom listing.

Question 3. Why does "message match" improve conversion?

Question 4. How do you tell whether a custom listing really helps?

Question 5. What is the best way to prepare for the certificate exam?

Go deeper: official resources

• Google Play Store Listing Certificate
• Google Play Console Help
• Android Developers Blog: updated Play Store Listing Certificate course
• Publish your app (Android developers)