One Android app.
More than one store.

Make the reporting decision early.

AppsFlyer supports a combined dashboard for multiple Android stores or separate dashboards by store. Decide the approach with the app owner before preparing builds and links.

The marketing discussion is wider than the dashboard. Which team will maintain the store versions? Who approves the destination URLs? What should a campaign report let the team compare?

Understand the two approaches.

With a single dashboard, store builds keep the same Android package name. AF_STORE identifies the store; the value is reflected in install_app_store. The af_r parameter can direct the user to the intended store.

With a dashboard per store, a store-specific channel combines with the package name to identify the app configuration, and attribution links differ by store. Consult the official instructions for build preparation and partner activation.

Keep a shared launch worksheet.

A simple worksheet can keep the release, media and measurement teams aligned. Use one row for each intended distribution path, with a named owner for every item that must be checked.

• App name and package name
• Target store and listing URL
• Approved build and release owner
• Reporting configuration and link owner
• Planned activation and value events
• Test status, open questions and launch approval

Test the whole route.

Do not treat a working URL as the only test. Review the expected route from the media click through the store and into the app. The teams should agree what they expect to see before running the check.

Record the device and market context, the destination reached and the reporting observations. Resolve differences between expectations and observations before expanding the campaign.

Make comparisons fair.

Store mix, creative mix and country mix can all change the shape of a campaign. Preserve the context when reviewing results, and separate a measurement question from a media-performance question.

Trendmax’s campaign planning connects the media scope with these readiness checks. The app’s authorized development and measurement teams remain responsible for the technical configuration.