Home / Symptoms / Android

Android installs from other stores never attribute

Android installs from third-party stores or APKs lack the Google Play Install Referrer, so they rarely attribute. Learn why and which alternatives exist.

SymptomAndroid installs from third-party app stores, APKs or pre-installs almost never get a paid attribution.
Most likely causeThose installs have no Google Play Install Referrer, so the main Android matching signal is missing.
First checkCheck the installer source of the unattributed Android installs and see whether they came from Google Play.

Short answer: the Google Play Install Referrer only exists for installs from Google Play. Installs from other Android stores, sideloaded APKs or adb have no Play referrer, so MMPs lose their main Android matching signal. Use the store's own referrer if it offers one, or link-based matching.

Why non-Play installs lose attribution

Install Referrer: information Google Play passes to an app on first launch describing the link that sent the user to the store listing, read through the Install Referrer library.

Android's Install Referrer library retrieves this data from Google Play. Google Ads' help centre says installs from third-party Android stores are recorded on first open and recommends Firebase for them, which implies no Play referrer is available. Android's own referrer docs do not discuss non-Play installs.

Do these installs count at all?

Yes. Your MMP still records the install when the app opens; it simply cannot tie it to a click through the Play referrer, so it usually lands in organic unless another matching method applies.

Likely causes

  • Installed from a third-party store. No Google Play referrer exists for the install.
  • Sideloaded APK. Same result.
  • Debug builds installed with adb. Test installs from a developer machine have no Play referrer (general practice).
  • Store-specific referrer not integrated. Some stores offer their own referrer mechanism, which needs separate integration (general practice).

How to confirm it

  1. Pull the installer package or store source for the unattributed Android installs.
  2. Compare attribution rates for Play and non-Play installs.
  3. For test devices, reinstall from a Play testing track and check whether attribution works.
  4. Check whether your MMP supports any of the other stores your app is listed in.

How to fix it

  1. Test attribution only with builds installed from Google Play testing tracks.
  2. Integrate the referrer mechanism of any other store you rely on, if it has one (general practice).
  3. Use link-based matching for campaigns that send users to other stores (general practice).
  4. Report non-Play installs as a separate segment so they do not distort organic.
Install sourcePlay referrerUsual MMP result
Google PlayYesMatched for same-session clicks
Other Android storeNoOrganic unless store referrer integrated
Sideloaded APKNoOrganic
adb debug buildNoOrganic

The Play Install Referrer guide explains the referrer in detail, and the install referrer troubleshooter starts with this check. If Play installs are also unattributed, see paid installs showing as organic.

FAQ

Common questions

Why are installs from other Android stores always organic?

Because they have no Google Play Install Referrer, which is how most Android installs are matched to a click. Without another signal, the MMP cannot find a paid touchpoint.

How does Google Ads handle third-party store installs?

Google's help centre says installs from third-party Android stores are recorded on first open rather than on download, and recommends Firebase for measuring them.

Why does my test device always show organic?

Builds installed through adb or as an APK have no Play referrer. Install from a Play internal or closed testing track to test attribution.

Can deferred deep links work for non-Play installs?

Only if your MMP can match the install another way, such as link-based matching. The Play referrer route is not available for these installs.

What is mobile attribution?

Mobile attribution is the process of crediting each app install or in-app event to the ad, link or channel that drove it. A mobile measurement partner (MMP) does this across all your channels so each install is counted once.

Why do ad networks report more installs than my MMP?

Each network counts every install it touched within its own windows, including views, while an MMP gives each install to a single source. Adding the networks' numbers together therefore overstates real installs.