Testing Your Mobile App

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

This article is part of our Background & Setup series.

Test Procedure

***Before you start testing, first make sure that you integrated the TUNE SDK as described in the iOS SDK Quick Start or Android SDK Quick Start. Then set up a test profile as described in Creating a Test Profile.***

After you set up your test profile in Attribution Analytics, create a test TUNE link:

  1. Go to Testing > Test Profiles from the main navigation.
  2. Find the test profile associated with your test device, and write down or copy the unique advertising identifier. For example, this would be the “Google AID” value for an Android device or the “iOS IFA” for an Apple device.
  3. Go to Partners from the main navigation and select your internal test partner. If you don’t have one set up already, you can follow the instructions in Setting up an Internal Partner.
  4. Click the Create New button and select your app to choose the app you want to test.
  5. Copy the URL that appears in the TUNE Link section and paste it into an email to yourself.
  6. Append the appropriate unique identifier parameter to the TUNE link and include the identifier value from step 2 above.
    • Example: Your Google AID from step 2 was “123-ABC”, and your TUNE link from step 5 was “https://s9u-6.tlnk.io/serve?action=click&publisher_id=360772&site_id=2962” You append “&google_aid=123-ABC” to the end of your TUNE link, and have a test URL of:
      https://s9u-6.tlnk.io/serve?action=click&publisher_id=360772&site_id=2962&google_aid=123-ABC

Next, use your test device to click the test URL and open the mobile app:

  1. Send the test TUNE link with the hard-coded identifier to yourself via email.
  2. Open that email on your test device and click the URL.
  3. Install the app if necessary (via appstore, APK file, or IPA file).
  4. Open the app and perform the action you want to test. If you’re testing install measurement, then you’re finished once you open the app.

Note: 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”, see our specific notes in Testing iOS SDK integration with TestFlightApp.

View Test Data in Reporting

After you set up a test profile and run a test (for example, perform a mobile app install on your test device), you can view the data in your Attribution Analytics reports.

To view test data in Attribution Analytics:

  1. Go to either the Test Logs Report or Logs Report.
  2. Select the tab most relevant to your test data.
  3. Click the Configure Report button and select the Filters tab.
  4. Select the Partner field from the filter pane, and check the box for your internal test partner.
  5. Click Apply once you’re finished.

Tip: If test data doesn’t appear in your report, try filtering the report by the unique identifier instead.

Testing SDK Implementation

You can use the above testing process and functionality to test the Attribution Analytics SDK and ensure that it’s implemented appropriately (logging clicks, installs, and other in-app events accurately). For additional implementation testing and troubleshooting information, see our developer documentation on Android SDK Implementation Troubleshooting and/or iOS SDK Implementation Troubleshooting.

No Comments

Leave a reply