Skip to content



With a push of a button you can send your Branch data to your Tune dashboard, helping you segment users, calculate LTV and understand the power of Branch links in acquiring users.

What events does Branch send to Tune?

Branch will send all Branch link clicks to Tune. Branch also sends all the data that is attached to the link. Tune then matches all downstream actions (installs, opens, custom events, payouts) back to the referring link. This will allow you to analyze which campaigns, channels, etc. are helping you acquire and engage users. You can see the list of fields that we send to Tune in the advaned section.

What does it look like?

See your Branch organic acquisition campaigns alongside your Tune data. You can also use Branch links with Tune measurement URL parameters to get the advantages of Branch deep linking with Tune's fine-grained attribution data and ROI analysis.




  • This guide requires you to have already integrated the Branch SDK. You also need to be a Tune customer and have the Tune SDK (iOS, Android) installed in your app.

Get credentials from your Tune dashboard

To set up the integration you will need your Tune Advertiser ID (an account-level identifier), your platform-specific Tune Site IDs (also known as App IDs) and a Tune Publisher ID for Branch.

You can find your Advertiser ID by navigating to "Accounts > Advertiser Account" in the left hand sidebar and finding the Advertiser ID in the Account Details.


You can find your Site ID by navigating to "Mobile Apps" in the left hand sidebar and getting the relevant Site ID from the table.


To retrieve Branch's Publisher ID from Tune it is first necessary to set Branch up as an Integrated Partner and find the Publisher ID:

  1. Log in to Tune and go to Attribution Analytics
  2. In the navigation bar on the left side of the portal, under the Partners section, click: Integrations
  3. On the Integrated Partners page (on the right side), search for Branch
  4. Select Branch and, in the far-right column, click: Enable
  5. Click on the Branch logo, then click on the "Attribution Settings" tab and copy the Partner ID (also known as the Branch Publisher ID)


Enable the Tune card in your Branch dashboard

  1. On the Branch Dashboard ( navigate to the Integrations page.
  2. Locate Tune and choose Enable.
  3. If you have not yet entered billing information, please do so now.
  4. Enter your Branch Partner ID, the Tune Advertiser ID and your platform-specific Tune Site IDs.
  5. Hit Save.



What Branch sends to Tune

Branch will send any parameters that you append to a link on to Tune (see below for adding advanced attribution parameters). By default, if you don't append any additional parameters to your link, Branch will pass Branch Analytics tags on to Tune with the below mapping.


If you enabled the Tune integration before August 10th 2016, your analytics tags will map to sub_publisher and sub_placement. To get the updated mappings please disable and re-enable the Tune card in your dashboard.

Branch Analytics Tag Tune Data Placeholder Tag
Campaign my_campaign
Channel my_placement
Feature my_keyword
Branch Click ID tracking_id

What are the methods Branch uses to let TUNE know an install came from Branch?

We rely on 3 methods to match attributions into TUNE’s dashboard.

  1. The first is snapshotting, which is the most basic. This is when we send a click event to Tune with IP address and User Agent and Tune completes the attribution.
  2. The next method is passing the Google Advertising Id or IDFA on iOS. This occurs when a Universal or App link drove open the app session via Branch (meaning a click never touched the browser). In this case, we can attribute Branch correctly in TUNE’s dashboard 100% of the time, because TUNE receives the IDFA / GAID from Branch while also keeping reference to it through their own SDK.
  3. The third method is passing along Branch’s click ID through the install referrer on Android, and the URI scheme on iOS. The TUNE SDK consumes the click ID through these mechanisms and then Branch sends that same click id back to TUNE. This also results in a 100% match.

By following all the steps listed in this guide, you’ll automatically have all 3 available.

Advanced network segmentation with Tune

If you are interested in advanced network attribution segmentation in Tune, you can use the same attribution parameters you'd append to a Tune Measurement URL with your Branch link.


If you enabled the Tune integration before August 10th 2016, you will need to disable and re-enable the Tune card in your dashboard before carrying out the instructions below. Please note this will change your default mapping of Branch analytics tags from the sub_publisher and sub_placement values into the my_partner values as noted above.

  1. Start with an existing Branch link, for example, a Quick Link.
  2. Append ? to the end of your link to start the query params string. For example:
  3. Next, create a measurement URL in Tune's Attribution Analytics Dashboard with the parameters you'd like to capture.
    • Select the "Click" URL (as opposed to the Impression URL)
    • After creating the measurement URL, copy everything after action=click& and append the parameters to the end of your Branch link.
    • You should remove &site_id={value} from the parameters, as Branch will automatically fill that in for your app depending on platform.


Your new URL will now pass useful parameters to Tune.

For example, here's a finalized link for Tapjoy:


Branch automatically uses the my_* parameters for its link data. If there is a conflict between the custom parameters you append to your Branch link and the default parameters Branch automatically sends to Tune, the custom parameters will override the default data.

Sending Google ValueTrack Parameters to Tune

For AdWords App Install Campaigns, you can append ValueTrack parameters to your Branch link by following the same instructions highlighted above.

When you create a Measurement URL in the Tune dashboard, the following URL parameters will automatically be generated and should be appended to the end of your Branch link (line breaks added for legibility):


With the macros {}, Google will insert the relevant values for each parameter, values which will then be passed to Tune's Attribution Analytics.

For a full list of supported value parameters for AdWords, check out Tune's Google AdWords Integration documentation.


How can I test this integration?

  1. Enable the integration
  2. Create a Branch link
  3. Click the Branch link so the app opens or you are taken to the app store. If you're taken to the app store, download and open the app.
  4. Log in to your Tune dashboard, and click "Logs" on the left hand side bar.
  5. Check the "Click" logs for a click attributed to Branch (or the network if you are using measurement URL parameters)
  6. Check the "Installs" or "Opens" logs for a correctly attributed install.
  7. After 10-15 minutes, you should see an install or open appear in your Attribution Dashboard.

Please note that to produce installs, you must delete the app and reset your advertising identifier, then click a Branch link and install the app.

Branch data not appearing in Tune

Ensure Branch is an enabled provider under your Partners in your TUNE dashboard. This should happen automatically, but to verify, click into the Integrated Partners section on your TUNE dashboard. From there, enter in Branch inside the search box, and click enable.

In this section, click on Attribution Settings. You'll see a section called Attribution Windows. Ensure Fingerprint Attribution Window is set to 3 hours or more. If you have this disabled, events will not be attributed to Branch.

Install discrepancies

Capture the GAID and IDFA device identifiers

Ensure that you are capturing both the Google Advertising Identifier (GAID) on Android, and the IDFA on iOS.

Add Google Play Install Referrer (Android)

When you integrate the Tune SDK, ensure you add the install referrer snippet provided Tune here.

Issues with Facebook data discrepancies.

If you are finding data discrepancies between Branch, Tune and Facebook - please ensure you have followed the Facebook Ads setup and troubleshooting steps here.

If you're using the Tune integration and Branch links in Facebook ads, Branch must initialize and complete before the Tune SDK. When this happens, Branch will be able fetch the necessary attribution parameters and pass them to Tune via the integration.