SINGLE DASHBOARD
A shared reporting view.
Store builds use the same Android package name. Store identification is set through AF_STORE; the download source can appear as install_app_store. A store-specific redirect can use af_r.
MEASUREMENT & ATTRIBUTION
More destinations.
One clear plan.
A campaign is only as useful as the decisions it helps you make. Align distribution, attribution and business events before turning on media.
CONNECT THE JOURNEY
Follow the user.
Align the teams.
01
Discover
Meet users in their mobile routine.
02
Download
Connect the ad to the right destination.
03
Activate
Measure the first meaningful app action.
04
Return
Learn from engagement and value.
Distribution is part of measurement.
Agree the store destination and app build before creating the campaign. A listing, a tracking link and a reporting view should all describe the same planned user journey.
Keep the technical setup with the app’s development and measurement teams, while the media team confirms links, campaign identifiers and the information it needs to evaluate delivery.
Define the events worth optimizing.
A first open, an activated player and a paying user answer different questions. Write down the event names, counting basis and review window before comparing channels.
For revenue-led reviews, agree currency, cost source and the maturity of the cohorts being compared. Make uncertainty visible before making a budget decision.
MULTI-STORE ANDROID
Choose the reporting
structure intentionally.
AppsFlyer describes two approaches for an Android app distributed through multiple stores.
DASHBOARD PER STORE
Separate store views.
Each store uses a channel-specific app configuration and corresponding attribution links. Review the setup and implications with the app owner and development team.
PRE-LAUNCH ALIGNMENT
Six checks.
Fewer loose ends.
The product
Confirm the package name, app build, supported devices and target store listing.
The destination
Test the intended click-to-store journey in the planned market and device context.
The attribution setup
Confirm the chosen measurement configuration, campaign naming and expected reporting fields.
The event plan
Agree which activation, engagement or revenue events will inform performance reviews.
The test
Validate the journey and expected signals before using production spend to learn.
The reporting basis
Align timezone, currency, cost source and cohort age for a consistent review.
READ THE RESULT, THEN ACT
Delivery tells one story.
User value tells another.
Media performance
Review spend, impressions, clicks, installs and pacing against the agreed campaign scope. Investigate unexpected changes before scaling the same setup.
Product outcomes
Read the selected activation, retention and value signals alongside acquisition. Use the findings to guide the next test, not only to summarize the last one.
YOUR NEXT CHAPTER
Make the measurement
part of the plan.
Bring your app, store strategy and current tracking setup. Let’s align the campaign journey.
Start a conversation