Testing the Google Play Install Referrer

The following methods for testing the proper collection and passing of the Google Play Install Referrer are only applicable for apps running the TUNE SDK versions 4.14.0 and below.

After you integrate the TUNE SDK into your Android app (but before you submit your app to the Google Play Store), make sure that the Google Play Install Referrer is being collected and passed properly to avoid any missed attributions and/or attribution discrepancies. For information about configuring the Install Referrer in your app code, please visit How Google Play Install Referrer Works.

Common Signs of an Issue Collecting the Install Referrer

When the Google Play Install Referrer is not setup properly in your app code, then you may see one or more of the following effects when testing your mobile app:

  • Installs are attributed as Organic instead of being credited to the appropriate advertising partner (whomever is referenced by the Install Referrer/TUNE tracking ID)
  • Integrations with Google Analytics may show relevant activity (such as page visits and ad clicks), but installs are not recorded properly
  • Integrations with Google Analytics may show installs, but they are not attributed to the proper source

Possible Causes and Solutions

Some possible causes for why an Install Referrer is not captured or passed properly include:

  • No test profile enabled in Attribution Analytics. Without a test profile enabled for your device and app, TUNE rejects duplicate installs and you may not see events in Attribution Analytics. For information about configuring a test profile, please visit Creating a Test Profile.
  • Multiple BroadcastReceivers for the same event. If you have more than one BroadcastReceiver listening for the same event or action, then it becomes uncertain which one will handle the intent and which one(s) will not. To support multiple BroadcastReceivers, you can create one receiver that passes the intent to other receivers (which are essentially subclasses of the one receiver) as described at Multiple Android Install Referrers.
  • For integrations with Google Analytics, the BroadcastReceiver used is not the one required for a specific version of Google Analytics. Make sure you are referencing the appropriate receiver.
    • For Google Analytics v2:
    • For Google Analytics v3:
    • For Google Analytics v4:

Testing the Install Referrer with the TUNE Referrer Test App

The TUNE Referrer Test app allows you to easily test if your Install Referrer Receiver is setup correctly.referrer_app1


Once you have launched your app, log into Attribution Analytics and go to the Test Logs.

  1. Click the Configure Report button.
  2. Search for and select the Referral URL metric.
  3. Click the Filters tab.
  4. Type in Referral Test Successful and click Add.
  5.  Click Apply.


If the Install Referrer Receiver is setup correctly, you should see the following result:


Testing the Install Referrer with ADB

***TUNE Debugging must be turned on***

// Do not enable this for release

To make sure that the install referrer is working properly, run the following command in an Android Debug Bridge (ADB) terminal:

adb logcat -s "TUNE"

This will start LogCat monitoring for the “TUNE” tag.

In a separate terminal, run:

adb shell
am broadcast -a com.android.vending.INSTALL_REFERRER -n {com.your.package}/com.tune.TuneTracker --es referrer "test_referrer=test"

Note: The “-n” parameter (which specifies the receiver) is optional. Omitting this parameter is a good test to see if the receiver is found by the broadcast (or if using multiple receivers, which particular receiver gets the broadcast).

When the install referrer is working properly, you should see output similar to:

09-19 11:56:23.123: D/TUNE: TUNE received referrer test_referrer=test

in your LogCat output.

For more information about testing your TUNE SDK integration, please visit: