Testing Attribution on Google Play Internal Testing Tracks

Play install referrer data exists only when the app comes from Google Play, so a build installed from an APK file cannot show whether your campaign parameters survive. That makes pre-release attribution testing awkward: you need a real store install, but you do not want to publish the build to everyone. Google Play's testing tracks offer that middle ground.

Why sideloaded APKs miss referrer data

Sideloading a local APK onto your phone or running a build straight from your IDE will not test install-referrer attribution. Android installs from external sources—such as direct APK downloads—do not generate a store referrer.

How the Install Referrer API works

As covered in Install Referrer: Android Attribution Explained, the Install Referrer library provides a stable interface for querying store referrer data on first launch.

Pre-launch checks with internal links

Before you turn on paid campaigns, you can pair test devices with internal tracking links to verify the end-to-end referrer flow. Running a pre-release check through the store flow lets you confirm three specific outcomes before a single ad dollar is spent: that the app retrieves the referrer string, that the install is attributed to the expected source, and that your custom parameters survive the installation intact.

Once the Airbridge SDK is integrated into your build, referrer retrieval happens automatically. On the very first open, the SDK queries the Install Referrer API, parses the referrer string, and forwards that data to the attribution platform, making manual API calls generally unnecessary.

Running link tests and reading logs

Testing the Airbridge SDK Integration for Marketers checks whether app install events coming from a campaign tracking link are attributed to Airbridge as expected. To run an attributed-install test, grab your test device's GAID or IDFA in its original format—keeping the hyphens—and register it at Settings > Testing Console > Attributed Installs to generate a QR code.

Dashboard test status indicators and real-time event logs do not always update at the exact same second. When you are going through Testing - Android SDK, you might see the dashboard test result lag behind or initially display a failure. Do not immediately tear down your SDK setup if that happens. Check the App Real-time Logs first: if the install-event details appear in those logs, your install-event collection and attribution succeeded regardless of the delayed or failed status on the test screen.

When you run a Tracking Link Test for Marketers to inspect how a specific link behaves, head to Raw Data > Real-time Log (App) and search for your test device's device ID. You must enter the ID exactly as it is formatted. Once the search returns your log entry, look at two fields to confirm the link worked:

• The event name appears in the results when the event itself was collected.
• The ad channel name appears alongside it when attribution to that ad channel succeeded.

If you wait a reasonable amount of time and still see no result—or if the test genuinely fails without showing install-event details in the logs—uninstall the app from your test phone and run the test again.

Bypassing log sampling with test IDs

One common trap during pre-launch QA is staring at an empty log screen and assuming the SDK failed to fire, when in reality your event was just filtered out of the view. In Airbridge, App Real-time Logs are sampled, which means a test event can be collected and still not show up in the log stream.

To view events in full without sampling, register your test identifier at Raw Data > Test Identifiers. Events coming from registered test identifiers—whether you register a device, browser, user account, or IP address identifier—are shown in full without sampling. For attributed-install testing specifically (as documented in Testing - Android SDK), you can add a test device by going to Settings > Testing Console > Attributed Installs in the Airbridge dashboard and entering the device ID with its hyphens included.