Skip to content

MyTarget

Overview

This guide will walk you through how to integrate MyTarget with Branch.

Universal Ads provides everything you need for complete tracking, including rich data for the MyTarget Engine to opimtize against.

The basic MyTarget integration involves three parts:

  1. Integrating the SDKs and tracking in-app events
  2. Enabling the integration and selecting postbacks
  3. Creating tracking links

Setup

Integrating the SDKs and tracking in-app events

The Branch SDKs for iOS and Android allow you to get up and running quickly.

If you haven't already integrated Branch SDK into your application, please follow our integration guide to integrate Branch SDK into your application:

  1. Documentation for Android

  2. Documentation for iOS

Limitations with setDebug and seeing data in Branch

When integrating the SDKs, it's often useful to use setDebug to verify that your app is able to communicate with Branch servers, and is receiving deep link data. However, our upstream systems don't register test events sent using setDebug, so events will not appear in Liveview or Analytics, nor will they fire postbacks. You should disable setDebug when looking at Liveview or testing postbacks.

Track conversion events

Install and open events are automatically tracked using just the Branch SDK integration. However, to track custom events, such as registration or purchase, you will need to integrate them into your application.

Please reference the general V2 Event Tracking Guide. This will help ensure that you've integrated the right Branch events with the correct metadata.

Testing your events with Liveview

You can test your integration by going to our Liveview page. Set a filter with the event name to verify that the Branch SDK is recording each event

Enabling the integration and selecting postbacks

Once you've integrated the SDK and configured the relevant events, you can enable MyTarget in the dashboard. Follow the steps below for enabling an ad partner, and select MyTarget from the list.

  1. Visit the Ads page on the Branch dashboard.
  2. Select Partner Management from the sidebar.
  3. Search for MyTarget.

    image

  4. Click Save and Enable.

    image

    Enable postbacks

    Postbacks will be automatically activated for the events listed above when you enable the integration. You can always add additional postbacks or edit postbacks, as described below in the Advanced section.

    Limitations with setDebug and seeing data in Branch

    When integrating the SDKs, it's often useful to use setDebug to verify that your app is able to communicate with Branch servers, and is receiving deep link data. However, our upstream systems don't register test events sent using setDebug, so events will not appear in Liveview or Analytics, nor will they fire postbacks. You should disable setDebug when looking at Liveview or testing postbacks.

MyTarget requires separate links for every platform - to create a tracking follow the normal link creation flow and add platform and partner specific parameters on Deep Linking tab.

  1. First, select an ad format. For App Install or App Engagement campaigns you'll want to select the App Only format. For Search or Display campaigns where the user should go to web if they don't have the app, then you should select Cross-Platform Search or Cross-Platform Display. Product Links are for shopping or dynamic remarketing campaigns and will take you to create a Deep Linked Product Feed.

    image

  2. At this point you need to name your link. Select something that will make it easy to find if you need it later. Your Ad Format and Ad Partner should be selected already, but feel free to choose one if they aren't. It's important that you select the right Ad Partner for analytics later on. Click Configure Options to continue.

    image

  3. In the Deep Linking tab of the link creator make sure to add the following key-value pairs, based on which platform the link is going to be used for. If these values are not added to the link, myTarget will block your links.

iOS

Key Value
$redirect_store_id iTunes ID (example id917737838)
$http_redirect_only true

image

Android

Key Value
$redirect_store_id Android App ID (example io.branch.branchster)
$http_redirect_only true

image

  1. This is also your chance to add deep link data and analytics tags. Analytics tags are important for later segmentation, so click the Analytics sub tab to add a Channel and Campaign value.

    image

    Set Analytics tags

    It's easier to slice your data in our analytics platform if you properly assign analytics parameters to your link. Channels generally correspond to ad networks, and Campaigns correspond to marketing initiatives that you're launching. For example: Channel: "YouTube", Campaign: "Summer 2017 Shoe Discounts."

  2. Click Create Link Now, and you have your tracking link! Take this link and give it to your Ad Partner's Account Manager or paste it into the tracking section of your campaign yourself. If you'd like to try our view-through attribution beta, please contact integrations@branch.io.

    image

Create MyTarget campaign

  1. Access your myTarget dashboard and start creating a new campaign.

  2. Obtain the Ad Link you created earlier from Branch, and remove all URL query parameters except %243p=a_mytarget, as myTarget will add these parameters later.

For example Example: Original link from Branch: https://branchster.app.link/yNC2Q06utF?%243p=a_mytarget&%24aaid={gaid}&%24idfa={idfa}&~click_id={clickid}

Final link for modified to fit myTarget's standards: https://branchster.app.link/yNC2Q06utF?%243p=a_mytarget

  1. Paste this modified link into the URL field.

image

View Your Data

The Ads Analytics Page on the Branch dashboard provides an interactive time series graph and table to view the performance of your Ad campaigns.

Example Ads Analytics Graph

The table shows summary data on the performance of each Ad campaign. On the right top side of the table you can find a download button to retrieve the chart's content as a CSV file.

Example Ads Table

Interacting with your data

Breakdown and compare aspects of your Ad campaigns' performance by using the Compare by + button to add a parameter to split the data displayed data by.

Then use the and + button to refine the data displayed to gain deeper insight into the performance of your Ad campaigns.

Advanced

Add more postbacks

When you enable an ad partner, your ad partner postbacks can be found under the Postbacks tab for that ad partner. It's easy to add additional postbacks.

image

  1. Click the Add New Postback button at the bottom of the screen.

  2. A modal will appear with Branch default events, as well as any commerce or custom events you've set up. Select an event, enter a postback URL if you're asked to, and click Save. This will be the event that triggers your new postback

    image

Edit postbacks

For advanced integrations, you may want to provide additional information in your postback that isn't there by default. You can edit postbacks by following our postback templating instructions, then clicking save. The postbacks in the Universal Ads interface follow the same syntax as Webhooks in Data Feeds. When the postback is saved, it is then validated - if you enter an invalid postback, you'll get an error at the top of your screen.

Reset Postbacks

We all make mistakes from time to time. If you need to reset your postbacks and your credentials, navigate to the Account Settings tab and look for the Reset all settings button. Be careful though! This will disable the ad partner, clear out all credentials and postbacks that you've set up, and return the ad partner to its basic configuration. You can then start afresh

Change attribution windows

Attribution windows can be specified at the global account level or on a per link basis with the link level window taking priority. See the below instructions for setup.

For customer experience and data accuracy, please do not set your deep linking window longer than the other attribution windows.

Account Level Attribution Windows

You can edit your attribution windows under Link Settings > Attribution Windows.

image

Learn more about account level attribution windows in People-Based Attribution.

Ad Network Attribution Windows

You can edit your attribution windows at the ad network level, if your ad network requires it. This is recommended when you enable networks like Facebook and Google, who may have different windows for installs. With this, you can preserve your Account Level Attribution Windows, as well.

image

To set attribution windows on a link level, you can append the following parameters to your generated Branch link.

Key Example Link
$click_install_window_days https://branchster.app.link/hpNVE52gxE?$click_install_window_days=3
$click_session_start_window_days https://branchster.app.link/hpNVE52gxE?$click_session_start_window_days=7
$click_conversion_window_days https://branchster.app.link/hpNVE52gxE?$click_session_start_window_days=30
$impression_install_window_days https://branchster.app.link/hpNVE52gxE?$impression_install_window_days=3
$impression_session_start_window_days https://branchster.app.link/hpNVE52gxE?$impression_session_start_window_days=1
$impression_conversion_window_days https://branchster.app.link/hpNVE52gxE?$impression_session_start_window_days=7

Link Level Attribution Support for Standard Branch links

As of July 2017, link level attribution window setting is only available on standard Branch links. Special Branch links such as the ones used for Google's Universal App Campaign or Play Store links with Branch link id parameters are currently not supported.

Support

How do I debug a discrepancy?

Navigate to the Analytics page to see data.

Comments