Testing AppsFlyer’s Android SDK Integration and Retargeting


Testing and Debugging the SDK

Integrating AppsFlyer SDK is easy and straightforward. Nevertheless, we highly recommend that you test the integration before submitting the app to the app store.

Why Should I Debug and Test Anyway?

Carefully tested integration ensures accurate and comprehensive data collection. 

When you test the SDK integration before releasing it, you make sure that installs and in-app events are tracked and attributed to the correct campaigns. 

So How do I Test and Debug The SDK Integration?

There are two ways you can test and debug the SDK integration. 

Basic Testing - Using AppsFlyer's Testing App

The test app can generate non-organic installs as well as retargeting installs. The app also tests for missing permissions in the app's manifest file and can also alert you about a missing or wrong dev key. For a full list of issues that the app tests for, see the AppsFlyer Testing App section of this article.

Advanced Testing - Debugging Directly from The Development Environment

The testing app doesn't test for more complex events such as in-app events, validating purchases and getting conversion data. You can test these features in the development environment with the help of the debug log.


The test app is compatible with AppsFlyer's Android SDK Versions 4.4.0 and above only.

If you are using an older SDK version or if this testing procedure has been unsuccessful, you can use the old test app, click here for more information.

All Android plugins are supported for the Android Testing App.

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