Adding Your App

Before you can measure or report on an app, you’ll need to add it into Attribution Analytics. If you’re a first time user of Attribution Analytics, you can add your first app directly in the platform. The steps below are for users adding more apps.

This article is part of our Background & Setup series.

Adding a Production Build App

To add a live Android or iOS app in Attribution Analytics:

  1. Go to ApplicationsApps in the main navigation
  2. On the Apps page, click Add a New App
  3. In the Add a New App dialog box, complete the following fields.
    Field Description
    App Name Enter the name of your app.
    Channel Select the channel/type of your app:

    • Mobile – Select this option if your app is a standard mobile app (available in one of the app stores).
    • Web – Select this option if your app runs within a mobile web browser.
    • TV – Select this option if your app runs on Apple tvOS.
    Platform Select the platform that your app runs on (you can only select one platform):

    • iOS – For an iOS app, provide your app’s package name (iOS Bundle Identifier) and the store app id. Note: Your app’s Store App ID is provided by Apple and is completely different from the automatically generated “App ID” in Attribution Analytics.
    • Android – For an Android app, provide your app’s package name and indicate if you have the Google Analytics SDK installed (your TUNE links include the Google Analytics Integration measurement parameters).
    • For a Web app that loads in a mobile web browser, provide the destination URL (to a mobile web experience) where users are directed for accessing your app. Please refer to our article on conversion attribution for Web with cookies for additional information. Note: This option is NOT for use with cross-platform apps.

    You need to “Add” the same app more than once if it runs on multiple platforms. Depending on the type you select, you may need to provide additional information.

    Destination URL Enter the URL where you want users directed to (for accessing your app).
  4. After completing the fields, in the lower-right corner, click Create App & Continue.
  5. After creating your app, you need to integrate the TUNE SDK into your actual mobile app if you selected iOS or Android as the App Type, or implement the install pixel provided after you create your web app in the Attribution Analytics platform.
  6. Download our SDK directly or email the SDK package to the appropriate person(s) in your organization:
    • Download SDK – Downloads a zip file containing the SDK, along with our Integration Guide (PDF) and attribution notes.
    • Email SDK – Opens an email including the URL that, when copied and pasted into your browser, automatically begins downloading the same zip file.


  7. After you access the SDK using either or both of the methods above, click Finish and you’re done!

Adding a Test Build of Your App

Many prefer to first do a dry run with a test build of their app to check for the correct implementation of the TUNE SDK and ensure attribution is completed properly.

As test builds are not yet in the App Store, you’ll need to manually provide all of your app’s information during setup.

  1. App Type – Android or iOS
  2. Package Name – Make sure the package name you provide during setup matches the actual package name of the app. For iOS only, you’ll be asked to provide the Store App ID which you can provide a fake number as the test build doesn’t exist in the App Store yet.
  3. Destination URL – Even though your app is not yet in the app store, we recommend providing the base URL of the app store itself. For example: “” or “”.

Things to Keep in Mind

  • Once you release the Production Build of your app, you’ll need to add the Production Build version separately using its specific app information.
  • TUNE uses package names to uniquely identify apps. So make sure the package name you provide when adding your app to your account matches the package name of your app.
    • If you add a test build of an existing app in your account, you’ll need to add it separately and use a unique package name.

Adding Web Apps

With web-based apps for browsers, client-based cookies are used to measure installs and additional events beyond the install. Implement the pixels provided for the events that you created for this web-based app.

Note: The install pixel must always be displayed first in the user path because events cannot attribute properly unless the install event is displayed first.

Copy the pixel code into your app, and you’re done!


Leave a reply
  • Chinmay  •  July 26, 2016

    The initialize method is no more available in latest SDK . Also when I created Test build as per above instructions , the advertising and conversion ID's are same as the one used for production build . So how does Tune distinguish between these two builds ?

    • Grace  •  July 28, 2016

      Hi Chinmay,

      The latest TUNE SDK includes the initialize method and can be found in Step 6 of the Android guide or Step 4 of the iOS guide. Which SDK guide were you using?

      Regarding distinguishing test builds vs production builds, TUNE uses package names to uniquely identify mobile apps. So please make sure the package name you provide when adding your app to your account matches the package name of your app. If you add a test build of an exisiting app in your account, you'll need to add it separately and use a unique package name.

  • Usman Ali  •  August 8, 2017

    is there in any Example or source for android set tracking in android application. I have search a lot but didn't find any helping material except official documentation.

    • Grace  •  August 8, 2017

      Hello Usman,

      For SDK-specific information, please visit There you can find all of our developer documentation relating to the TUNE SDK and APIs.

      For your specific request, I believe you're looking to set app level ad tracking which you can find in the Settings for Advanced Tracking.