Branch Certified Partner
This guide will walk you through how to setup your campaigns with Liftoff using Branch Universal Ads and track ad conversions across every device, platform, and channel.
DEVELOPER MAY BE REQUIRED
The following Universal Ads prerequisite includes providing URI schemes and other components that may require a developer:
The following Universal Ads prerequisites involve app code changes:
- Visit the Ads page on the Branch dashboard.
- Select Partner Management from the sidebar.
- Search for your Universal Ads Partner.
- Select Liftoff and hit Save & Enable.
Basic postbacks will automatically be activated for events like Install and Purchase when you enable your ad partner.
You can then add additional postbacks, for example, if you wanted to add postbacks for custom events that are specific to your app like Account Created.
You can also edit postbacks if there's additional data you really need to pass along to your ad partner.
There may be times when you need to reset a partner's settings; i.e. when a partner updates their postback templates or when perhaps you've made a mistake during partner setup. Resetting a partner's settings allows you to re-enable the partner integration with the correct information to accurately measure and attribute conversion.
Disables Ad Partner
Resetting partner settings will:
- Disable the ad partner.
- Clear out all of your saved credentials and postbacks that are already setup.
- Return the ad partner to its basic configuration.
To reset Liftoff's postbacks:
- Click on the Account Settings tab.
- Click the Reset All Settings button in the right-hand corner.
For details on re-engagement campaigns, see here.
There is no specific parameter inserted into links that differentiate a UA URL from a RE URL (ex: RE=1). Advertisers can create completely different campaigns in their dashboard (including links) and name them accordingly in order to differentiate data. (i.e. Sam’s Club created an “Evergreen_Re-engagement” link to be a re-engagement specific link.
To set up product feed retargeting, reach out to your Branch and Liftoff CSMs.
For product event tracking to work correctly, Liftoff needs to receive the product ID(s) associated with each of your events. For example, the IDs for specific products a user adds to their cart or purchase. These IDs need to be linked back to the unique IDs you pass Liftoff within your product feed.
Our default global template will automatically include the relevant product IDs if they are stored in the $sku attribute on Branch’s content items.
Because Branch’s SDK offers flexibility in the attributes you can associate with event items, it is possible that the relevant product ID is being passed via a different attribute. If that is the case, you will need to work with a Branch support engineer to determine which attribute matches your product feed. Once that has been determined, the engineer can help replace $sku with the correct field name on the macro that powers the product_id parameter on Liftoff’s postback template.
Updated about a month ago