Journeys Assist

Overview

Journeys Assist allows you to combine your powerful banners and interstitials from Journeys with your mobile measurement capabilities of Universal Ads, Universal Email and other Branch powered channels to provide complete attribution of the user flow.

How does it work?

Same Session (Enabled by default)

1. User lands on your mobile website and sees a banner or full-page interstitial promoting the mobile app coming from an ad, email interaction or other Branch powered channel.
   • User can come from an ad they interact with (click).
   • User can come from an email campaign (click).
2. User clicks the call to action to install the mobile app within the same session.
3. Once the user opens the app, conversions (including the install) that happen in the app, are attributed to the original Branch powered campaign the user interacted with.

Multi Session

1. User lands on your mobile website and sees a banner or full-page interstitial promoting the mobile app coming from an ad, email interaction or other Branch powered channel.
   • User can come from an ad they interact with (click).
   • User can come from an email campaign (click).
2. User drops off for some time and returns to the mobile website to see the Journeys banner/interstitial again.
3. User clicks the call to action to install the mobile app.
4. Once the user opens the app, conversions (including the install) that happen in the app, are attributed to the original Branch powered campaign the user interacted with.

Prerequisites

In order to enable Journeys Assist, you need to have completed the following:

1. Created a Branch Dashboard.
2. Enabled Journeys for your Branch account.
   • Contact your Branch account manager or visit https://branch.io/pricing
3. Implemented the Branch SDK into your mobile app (iOS | Android)
   • Track events
4. Implemented the Branch Web SDK into your website.
5. Already running Journeys banners/interstitials.
6. Already running other Branch powered channels, like ad campaigns through your chosen ad partner and/or running email campaigns through your chosen email partner.

Enabling Journeys Assist

Same Session

This is enabled by default for all Journeys. If a user is driven to a mobile web session from a Branch powered channel and interacts with a Journey Banner within the same session. Branch will automatically bypass the Journey CTA link with the session's referring Branch link.

Multi Session

📘

Developer Required

If you wish to support Journeys Assist across multiple mobile web sessions to credit referring Branch powered channels for longer durations, you must add two new parameters the web SDKs initialization options.

Opt-In to Journeys Assist Multi Session through Web SDK Initialization Options

Before the Branch SDK initializes, implement the following method:

var options = { 
  enableExtendedJourneysAssist: true, // enable or disable referring Branch link expiry for Journeys Assist
  extendedJourneysAssistExpiryTime : 5000 // TTL value in milliseconds for the referring Branch link. Defaults to 7 days
};
branch.init('key_live_YOUR_KEY_GOES_HERE', options, function(err, data) {
  console.log(err, data);
});

Disabling Journeys Assist

If you wish to disable the default Same Session Journeys Assist support and have Journeys always claim attribution for post CTA click conversions, you can do so through the following two ways:

1. Add make_new_link:true to your Journey View Deep Link Data

2. Add make_new_link:true to the web SDK initialization options

var options = { 
  make_new_link: true
};
branch.init('key_live_YOUR_KEY_GOES_HERE', options, function(err, data) {
  console.log(err, data);
});

View Analytics

After enabling Journeys Assist and as campaigns run, your ad/email campaigns should receive credit through Journeys installs and other conversions. To do this, we can apply the add the ~tags filter for your respective campaign. With this, you can view which Journeys campaign drove the ad/email conversion.

FAQ

Does Journeys Assist work with all types of ad networks?

Journeys Assist only works with ad networks where a Branch Link is used for redirection. In other words, ad networks that solely rely on an MMP API connection to function will not utilize Journeys Assist.