Additional Testing for AppsFlyer Android SDK

  • Advertisers
  • Developers

Introduction

AppsFlyer provides a simple test app to test the integration of your app with our Android SDK.

Using the Android SDK Integration test app, you can track integration issues in your project. The test app can perform automated click-install tests that provide a non-organic install on your dashboard (before and after publishing).
DOWNLOAD LINK

Test App Overview and Set-Up

  1. Integrate the AppsFlyer’s Android SDK into your app and install the app on your device. You can install the app any way you like - directly from the API, via Android studio or via the Play Store (if the version in the store already has the SDK integrated). What's important is not to launch it after installing it.
  2. Download the test app from Google Play and open it.
  3. The following window is displayed:

    integration-test-app-home-screen.jpg
    Click the WHITELIST DEVICE button to display your device’s whitelist parameter values - Android ID and Google Advertising ID.

    test-app-white-list-device.png
    Click the green share button to send these values via email.

  4. Click on the blue WHITELIST button to whitelist your device.
  5. Enter your login details to whitelist the device

    test-app-white-list-device-login.png
    These values are added to your account’s Whitelist page. Make sure you run the test app on a Whitelisted device, otherwise you are unable to receive a non-organic install.

  6. Go back to the main screen and enter your app’s Package Name or App name in the search bar (e.g. android.appsflyer.sampleapp or ‘Sample App’)

    test_integration_search_app.png

Testing a Non-Organic Install

Once the device is whitelisted, in the app's main screen click on NON ORGANIC INSTALL TEST: If the test is successful, you should see the following screen:

integration-test-app-test-install.jpg

As a result of this test, a referrer broadcast has been simulated on your app - this works for both published and unpublished apps. If your app is published in the Play Store, the attribution is generated using the Play Store Referrer. Otherwise, it is generated using Device ID Matching.

If the test is not successful, examine the category that displays an error.

  1. In the AppsFlyer dashboard, go to the Overview Page.
  2. Filter by Media Source AppsFlyer_Test

    filter_test.png

You can see a non-organic install on your dashboard, under the AppsFlyer_Test media source.

test_media_source.png

The integration is complete and you are good to go!

Testing Retargeting Attribution

In addition, to install attribution, the test app can test your Retargeting and Deep Link configurations.

Make sure you to use the Integration Test at least once, before trying the Retargeting Test.

  1. Click RETARGETING TESTING on the home page.
    The following window opens:

    test-app-test-retargeting.png

  2. Enter your app’s Deep Link scheme and host (according to your AndroidManifest configurations). Select Http:// to quickly add http:// to the search bar.
  3. Once your scheme is found, the test app generates a tracking link that redirects back to your deep linked activity.

If the deep linked Activity is the main Activity or contains AppsFlyerLib.getInstance().sendDeepLinkData(this) in the onCreate() method the test works and the test app displays the following screen:

test-app-test-retargeting-success.png

 Note

The test app waits six seconds before timing-out the attempt - a slow internet connection may cause the test to fail.


You can use the test to generate Re-Engagement attribution in your dashboard. To do so, make sure that your app has retargeting enabled on the dashboard, and that you open the app at least three times before testing.

If everything is successful, you can see a Re-Engagement attribution under AppsFlyer_Test media source and Test campaign, as follows:

Detecting Integration Problems in your App

The test app can be used to quickly detect common problems with the integration.

There are 5 test categories. See the table below to learn what each category checks for.

 

 

Possible Integration Errors

The table lists all possible errors and their corresponding solutions:

# Category Title Error

1

AppsFlyer Dashboard Configured

Error message:

Test Aborted! Click here for more info on setting up an AppsFlyer dashboard

The app is not configured in your dashboard. Add the app in your dashboard before testing.

2

Required Manifest Permissions

Make sure to add Internet permissions to your app’s manifest, without it the SDK cannot run

3

Device White Listed

Error message:

Whitelisting Required

The device is not whitelisted in your dashboard. If the device is not whitelisted, the test app cannot generate non-organic installs.

4

Manifest Receiver

AppsFlyer’s BroadcastReceiver is missing from the
AndroidManifest.xml

5

startTracking() detected

Error message:

The SDK was not detected by the Test App

The test app attempts to communicate with the SDK. If it fails, it indicates that it is unable to detect startTracking(). 

Possible reasons:

  1. The SDK is not integrated
  2. The SDK is configured incorrectly
  3. SDK init delayed for CUID
  4. App launch is slow
  5. The app has GDPR related do not track mechanism implemented in the app

6

Non-Organic Install Verified

The test app is unable to generate a non-organic install, usually due to the errors above.

Was this article helpful?
3 out of 11 found this helpful

Page Contents: