Listing Updates Guide

Start from a saved version

Open your app in Apps, then choose Store listing → Listing updates.
Start an update and choose a Saved version. If none is available, create and save a listing draft in Versions first.
Choose the Original language. Add the other languages you need, using the full language and region names shown in the selector.
Optionally include captions from saved screenshot projects. You can select up to ten projects for an update.

Preparing an update is free. AI translation uses the displayed token quote; approved wording, private reviews and report tools have their own paid-plan or active-trial access. You do not need performance results to start preparing an update.

1. Edit & translate

Start with the original text, then select a translation language to compare both versions. Review labels such as Needs translation, Needs review and Source changed. Changing original text means related translations need another review.

Edit the fields you want to change, including the selected screenshot captions.
Select the translation fields you need. Check the selection scope and exact token quote before translating.
Review the generated result for meaning, names, numbers and field limits. Mark reviewed fields as appropriate.
Choose Save changes to keep your edits in the update.

Screenshot previews help you review caption layout. To replace images, move devices or change the artwork, open the screenshot editor.

2. Get approval, if needed

Use Get approval when a client or teammate needs to review the prepared text and screenshots. Eligible accounts can create a private review link and follow feedback on that version of the update.

Share the review link only with intended reviewers: anyone who has the link can access that review while it is active. If the content changes after a review, check that approval still applies to the current version.

Approval is optional. It records a review decision in AppDrift; sending changes to a store remains a separate action.

Copy reviewed changes to drafts

After saving, choose Copy changes to drafts and review the confirmation. This applies the prepared listing text and selected captions to their AppDrift drafts.

Save changes: Keeps edits in this listing update.
Copy changes to drafts: Applies reviewed text to the saved listing and screenshot-caption drafts.
Open version editor: Opens the listing draft so you can review and explicitly send supported text changes to your connected store.
Screenshot export or upload: Happens in the screenshot editor. Editing captions or approving a review does not upload screenshot images.

A saved update or approved review does not change the public listing. Check the app, version, fields and languages before a store send. Store acceptance, public availability and review status remain distinct.

Reuse approved wording

Open Approved wording inside Listing updates to save product terms and reviewed translations for this app. In Edit & translate, review a saved translation and choose Approve for reuse.

Exact eligible approved matches can be reused without AI tokens. Reuse depends on the same original text, language pair, field context and approved terms. If the source or terms change, an earlier translation may need review again.

Imported or generated text is not automatically approved. Your review confirms the wording; check that it remains correct for this release.

3. Check results after a store update

Open Check results after sending supported listing changes. Select the recorded store update and check whether the prepared text is visible in the chosen public storefront.

With eligible access and connected Apple reports, choose one report and market to compare available data before and after the first public match. The comparison needs 14 complete days on each side. Missing or incomplete reports remain unavailable.

For Google Play, you can check the public listing and review a downloaded report in Store reports. Automatic before-and-after acquisition comparisons are unavailable.

These observations can help you decide what to investigate. Advertising, seasonality, other updates and reporting gaps can also affect the figures.

Store reports and A/B comparisons

Store reports keeps supported downloaded Apple and Google reports alongside manually entered native experiment records. Preview an import, verify its app, reporting period and source, then confirm it. Keep report types and their metric definitions separate.

For AppDrift's A/B tests, open the app's Store listing section, prepare two metadata variants and record successive observation periods. Creating a comparison requires Basic or higher paid-plan access and costs 10 AI tokens; viewing its results is free. Apply store metadata yourself and record each phase transition in AppDrift. Planning durations do not automatically switch the store listing.

These tests compare tracked keyword ranks. They do not prove a causal improvement or calculate a statistically verified conversion winner. Native Apple Product Page Optimization and Google Play listing experiments run in their respective store consoles; AppDrift can keep their manually entered results separately.

Get help with translations, drafts and missing results