Testing AppsFlyer SDK integration

  • Developers

Testing and debugging the SDK integration

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


The AppsFlyer SDK is compatible with Android based Smart TVs and Apple TV (tvOS).

You can use the instructions in this guide to test the SDK integration for apps developed for Android and Apple TVs.

For unpublished tvOS apps, see Testing tvOS Integration Before Publishing.

For apps developed for Amazon's Fire TV, see Testing Attribution Out of Store.

Why should I debug and test anyway?

Carefully tested integration ensures accurate and comprehensive data collection.

By testing the SDK integration, you make sure that installs and in-app events are recorded 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: testing the integration using attribution links

AppsFlyer attribution model utilizes attribution links. Conducting tests using attribution links is highly recommended.

When you test the SDK integration using attribution links you get in-depth insight into AppsFlyer's attribution model. In return, knowledge of AppsFlyer's attribution model and attribution features gives you the opportunity optimize your marketing operation and analysis.

Advanced testing: debugging directly from the development environment

The SDK Integration Tests section only tests for a limited set of features. It doesn't cover purchase validation, conversion data and errors in SDK setup. You can test these in the development environment with the help of the debug log.


If you are an Ad Network and you want to test your integration with AppsFlyer or with advertisers, see our guide on Ad Network Integration Testing.

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