Since the SDK can log conversions generated through the Apple iTunes App Store, Google Play Store, Amazon Appstore for Android, and other third parties, you should test conversion measurement without actually updating your mobile app listing in the production environment. First confirm that the Tune SDK is successfully working before you update your mobile app in its respective app store. You can save an enormous amount of time, resources, and frustration by first testing that all functions are operational before updating your mobile app for the app store. For Android apps in the Google Play Store, make sure that your app is properly collecting the Install Referrer as described at Testing the Google Play Install Referrer.
***Before you start testing, first make sure that you integrated the Tune SDK as described at iOS SDK or Android SDK. Then set up a test profile as described in Creating a Test Profile.*** After you set up your test profile, generate a TUNE link:
After you set up your test profile, generate a TUNE link:
- Log in to Attribution Analytics.
- In the navigation (on the left side), under the Applications section, expand Testing, and then click Test Mobile App.
- On the Test Mobile App page, from the drop-down lists for each field (such as Mobile App, Partner, Campaign Type, Destination URL), make the appropriate selections so Attribution Analytics can automatically generate the appropriate TUNE link for your app.
- To append the device identifier (that you specified in your test profile) and/or other optional parameters, scroll down to the Parameters section, open the Identifiers for App-to-App Attributionaccordion menu and add the device identifier. As you type specific parameters to include, the TUNE link updates with those values.
- To send yourself an email with the updated TUNE link (which now includes your optional parameters), below the TUNE Link box, click the "envelope" icon as shown in the following screenshot.
- In the new email window (that already includes the updated TUNE link in the body of the email), attach your .APK or .IPA file (ad-hoc app build), and then click Send.
Before you can install a developer app on an Apple device, first set up a provisioning file as described in Provision an iOS Device. If you use the "TestFlightApp", please visit Testing iOS SDK integration with TestFlightApp.***
For information about generating a TUNE link in production (outside of a test profile), please visit Creating a TUNE Link.
Include Test Data in Reporting
After you set up a test profile in Attribution Analytics and run a test (for example, perform a mobile app install on your test device), you must include test data in your reports (else you will not see the test install event because by default Attribution Analytics excludes test data from reporting). To include test data in your reports:
- In the navigation, under the Reporting section, click the desired type of report (for example, Actuals, Cohort, Retention, or Logs).
- On the report page, next to the date time in the upper-left corner, click Edit.
- In the parameters and filters panel, scroll down to the Filter section at the bottom, remove the Test Data: Exclude filter, and then click Apply as shown in the following screenshot.
Testing SDK Implementation
You can use this testing process and functionality to test the Attribution Analytics SDK and ensure that it's implemented appropriately (is logging clicks, installs, and other in-app events accurately). For additional implementation testing and troubleshooting information, visit our Android SDK Implementation Troubleshooting and/or iOS SDK Implementation Troubleshooting.
Learn how to create a test profile and test your mobile app in Attribution Analytics to be sure the TUNE SDK was configured correctly so you can get accurate attribution information. This is the most important step when using Attribution Analytics, so let us help you along the way!