Enter your listing ideas
Record title, subtitle, description and keyword wording where those fields apply to your store. You supply the variants.
Metadata A/B comparisons
Compare listing ideas.
Keep the rank history.
Save two versions of your metadata and compare keyword positions before and after your store update. You choose when each period starts.
Basic and above · 10 tokens to create · No tokens to view results
You update the store metadata and mark each observation period in AppDrift.
WayfarerTravel planning app
Explore a different emphasis in the app title.
A
Current wording
- Title
- Wayfarer: Travel Planner
- Subtitle
- Plan days and save places
B
Proposed wording
- Title
- Wayfarer: Trip Itinerary
- Subtitle
- Plan days and save places
You enter both versions. Creating the comparison does not change the store listing.
Two periods. You control the switch.
From an idea to a useful comparison.
Start with an app and tracked keywords. Enter the metadata you want to compare, then work through each period at your own pace.
- 1
You start period A
Observe A
Keep your current listing in place while AppDrift collects your tracked keyword ranks.
- 2
You update the store
Change your listing
Send your proposed metadata through your usual store workflow. Check that the change is visible.
- 3
You switch to period B
Observe B
Mark the switch in AppDrift and collect ranks with the new listing in place.
- 4
You complete the comparison
Review the comparison
Compare average positions for each tracked keyword across the two periods.
The 7-, 14- and 30-day options are planning durations. Start, switch and complete are manual actions; the comparison uses the actual dates you record.
Know what you are comparing
A record of what changed in search.
Review the average position of each tracked keyword across period A and period B. Keep the comparison to inform your next listing decision.
Explore keyword trackingGive both periods time
Collect keyword observations before completing the comparison. Missing observations limit what you can learn; a longer calendar period alone does not guarantee useful evidence.
Use the result as a signal
Other market changes can affect ranks. A difference between the periods does not establish that your metadata caused it, and the comparison does not calculate statistical confidence.
Testing screenshot conversion?
Use a native store experiment.
Apple Product Page Optimization and Google Play Store Listing Experiments run in their respective store consoles. Their store-reported conversion results answer a different question from AppDrift’s sequential keyword-rank comparison.
Create screenshot assets in AppDrift, then set up and run the experiment in the store. AppDrift does not start or switch these native experiments.
Before you begin
The details, clearly.
Add your app, choose the keywords you want to track, and prepare two versions of your listing text.
It compares average tracked keyword ranks across two successive periods. You record your current and proposed metadata, then mark when each period starts. The result is an observation of ranking changes; it does not measure install conversion or establish that the metadata caused the change.
No. Creating or starting a comparison saves its wording and dates in AppDrift. You update the store metadata through your usual publishing workflow, check that the change is visible, and manually switch to period B. Completing the comparison is also your action.
The 7-, 14- and 30-day choices are planning durations. AppDrift does not automatically switch or finish the comparison. The results use the actual start, switch and completion dates. Allow time for rank observations in both periods before interpreting differences.
Metadata comparisons are included on paid plans starting with Basic, and eligible active trials. Creating one costs 10 tokens; viewing its results has no separate charge. You can keep up to three active comparisons per app. A Free account needs paid access or an eligible active trial to create one.
No. The result summarizes observed average ranks and differences by keyword. It does not calculate statistical confidence or isolate the effect of your metadata from other market changes. Missing observations can make the comparison inconclusive.
Native conversion experiments run in Apple Product Page Optimization or Google Play Store Listing Experiments. You can create screenshot assets in AppDrift and use them in the store’s experiment workflow. AppDrift’s metadata comparison does not allocate traffic or launch those experiments.
Give your next listing idea a record.
Keep the wording, the observation periods and the rank comparison together.
Set up a comparison
Basic and above · 10 tokens to create