CUSTOM LISTING LAUNCH RECORD — ONE AUDIENCE, ONE LOCALE

Store / app / package or app identifier: [public product details]
Page or listing reference name: [stable console name]
Owner / review date / build: [responsible role and version]
Target customer task: [one outcome the released app supports]
Audience route: [selected search terms, exact URL or other console option]
Reason for a custom version: [difference from the default audience or story]
Default listing saved at: [safe file reference]

INTENT AND PROMISE
Candidate phrase and evidence source: [customer language or measured research]
Selected console keyword or targeting setting: [exact configured selection]
Variations / locale reviewed: [meaning and fit checked by a local reviewer]
First screenshot promise: [what a fresh reader expects]
Released feature supporting the promise: [build and observed action]
Unsupported claims removed: [planned features or ambiguous wording]
Pricing, account or permission boundary: [relevant condition]

ASSETS AND LANGUAGE
Listing name / secondary text / description: [reviewed draft reference]
Screenshots and other assets: [filenames and locale]
Language fit and field lengths: [checks and unresolved items]
Product text in the same locale: [observed gaps and owner]
Final approved files saved at: [safe team reference]

PUBLICATION AND DESTINATION
Approval / publication / visibility: [actual console state and checked date]
Exact public custom listing URL: [copy the released URL]
In-app destination when configured: [separate from the store page URL]
Device / OS / account state used: [repeatable context]
Observed listing and language: [assets shown, not assumed]
Advertised task attempted: [harmless sample action]
Observed result and mismatch: [completed, blocked or unexpected]
Issue owner and retest condition: [next action]

MEASUREMENT AND NEXT DECISION
Report name and page identifier: [exact console scope]
Period / locale / source / audience filters: [matching comparison context]
Numerator, denominator and definition: [report labels and eligible counts]
Completed acquisition or use evidence: [separate report, or unavailable]
Concurrent product or acquisition changes: [potential confounding context]
Conclusion: [supported observation, pending or inconclusive]
Next decision and owner: [one action justified by the evidence]

Use the store's actual approval and reporting workflow. This record organizes observations; it does not publish metadata, estimate demand, attribute an uplift or guarantee a ranking. Do not include account credentials, private customer details or identifiable analytics exports.

Original template by RateMyApp, October 5, 2026.
https://ratemyapp.io/resources/aso-templates/
Free to copy and adapt, including for commercial team projects. Attribution optional.
Keep account credentials, customer information and unpublished business figures out of shared copies.