Test mobile SDK integration with the app

Testing and debugging the SDK integration

 Test SDK integration before submitting an app to the app store. In this article, SDK refers to both the AppsFlyer iOS and Android SDKs.

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 ensure that installs and in-app events are recorded and attributed correctly. 

Testing and debugging SDK integration

Use one of the following methods to test and debug SDK integration:

  • 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 SDK integration using attribution links you get an in-depth insight into the AppsFlyer attribution model. This gives you the opportunity to optimize your marketing operation and analysis.
  • Advanced testing:
    • Debugging directly from the development environment.
    • The SDK integration test section only tests a limited set of features. Test the following in the development environment using the debug log: 
      • Purchase validation
      • Conversion data
      • Errors in SDK setup. You can test these in the development environment with the help of the debug log.

Related reading for ad networks: Ad network integration testing.

Was this article helpful?