# ASO Agency — Lesson 29: Google Play custom store listings: targeting and setup

Outcome: Plan a targeted listing with explicit audience selection, fallback and maintenance rules.

App / store / market / locale:
Prepared by / date:
Product or listing version:

## Your ASO assignment

1. Prepare one variant brief with an explicit audience and supported benefit.

Your response:

2. Create three routing test cases, including a fallback case.

Your response:

3. Write how you will maintain the variant after a product update.

Your response:

## Scenario challenge

A campaign ends but its custom listing still advertises a temporary offer. Identify the owner, correction and monitoring changes needed, and explain why campaign shutdown alone does not complete listing maintenance.

Your reasoning:

## Handover

### Audience hypothesis

State the supported need and why the main listing is insufficient for this context.

Your evidence and decision:

### Targeting configuration

Record actual console criteria, destination links, language behavior and fallback.

Your evidence and decision:

### Approved assets

Keep exact fields and files for the targeted listing with product and locale approvals.

Your evidence and decision:

### Result context

Report metrics alongside audience and source differences rather than treating raw comparisons as experiments.

Your evidence and decision:

### Lifecycle

Assign launch verification, review date and retirement responsibility.

Your evidence and decision:

## Submission check

- [ ] Audience selection can be explained and tested.
- [ ] Locale and fallback behavior are explicit.
- [ ] Measurement does not confuse selection differences with creative causation.

## Next action
Owner:
Required evidence:
Due date:
Review decision:

www.asoagency.com