Testing AppsFlyer SDK integration

Testing and debugging the SDK integration

After integrating the AppsFlyer SDK in your app test the integration before submitting the app to the app store.

Special cases of testing and debugging

Why should I debug and test?

  • 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.

Testing and debugging SDK integration

Use one of the following methods to test and debug SDK integation

Basic testing: testing the integration using attribution links

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

When you test the SDK integration using attribution links you get in-depth insight into the AppsFlyer attribution model. The knowledge of AppsFlyer attribution model and attribution features gives you the opportunity to 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?