Troubleshooting Missing Google Play Install Referrers on Android
Use a clean Google Play install to separate referrer delivery, SDK collection, and attribution reporting problems.
If a Google Play test install does not show under the expected campaign, check three points in order: whether Google Play received the campaign link, whether your app collected the install, and whether the install matched the campaign under your attribution rules. A missing campaign row alone cannot tell you which step failed.
1. Reproduce the click and install
Use one known tracking link, a test device with the Google Play Store, and a build distributed through Google Play. Start with the app uninstalled. Click the tracking link, install from Google Play, open the app for the first time, then inspect the Airbridge Android SDK test logs. Record when you clicked, whether the link opened the intended store listing, when installation completed, and when you opened the app. Avoid clicking another campaign link on that device during the test. An APK installed directly from a file cannot reproduce the Google Play referrer path.
2. Check collection without adding another attribution client
If you maintain a direct integration with Google's Install Referrer API, inspect the response to see whether the service returned the referrer field. The API returns click and install-start timestamps as separate fields; do not assume they are encoded inside the referrer string. Distinguish a service or connection error from a successful response without your campaign parameters.
If you use the Airbridge SDK, use the SDK's documented testing tools to check the first app launch and install event before adding diagnostic code. A second direct API implementation is not required merely to check attribution in Airbridge.
3. Compare the install event with campaign reporting
If the first launch did not create an install event, check the SDK setup and the app or environment you are testing. If the install event exists but the expected campaign is missing, check the campaign link, attribution window, and whether another touchpoint was eligible. Check the app, platform, time range, and any campaign filters in the report before concluding that attribution is missing.
| Test result | Next check |
|---|---|
| The link did not reach Google Play | Confirm the destination and redirect chain |
| The link reached Google Play, but there is no install event | Verify SDK initialization and the first launch in the test build |
| The install exists without the expected campaign | Compare the link parameters, reporting filters, and attribution settings |
Save the test link, app version, and timestamps. A second test that changes one variable at a time is easier to diagnose than several installs with different links and builds.
