Branch integration for Tapper Lift
Connect Branch so Lift can check Google's and Meta's numbers against your own Branch numbers, and see what Lift reads from each Branch postback.
Connect Branch so Tapper Lift can check Google's and Meta's numbers against your own Branch numbers. Lift reads the installs, in-app events and revenue Branch attributes to each network, campaign and ad group, and never changes anything in Branch.
Connecting Branch takes two steps: add the app in Tapper and switch on Block for it, then enable Tapper as an ad partner in Branch and paste in the two values Tapper gives you. No SDK changes are required.
This is the same Branch integration that Tapper Block uses. If you have already set it up for Block, there is nothing more to do.
Before you start
- You need the Owner or Admin role in the workspace.
- The integration is Block's part of the app, so the workspace needs Tapper Block.
- Have your Branch Key at hand. In your Branch dashboard, it is under Account Settings, then App, in the section Branch Key and Secret. Use the live one: it starts with
key_live_.
Create the integration in Tapper
Open Setup > Mobile app. With no app yet, the page opens on the add form; otherwise click Add app at the end of the list on the left. Enter a Name, tick the Platforms, choose Branch as the Tracking tool, enter your Branch Key and click Add app. On a new workspace, Add mobile app on the Mobile app row of the connect step opens the same form.
On the app's page, turn on the switch on the Block card, under Access. The dialog asks for nothing: click Switch on. Tapper makes an Integration ID, a secret and a callback address.
The dialog shows the Integration ID and the Secret, each with a copy button, and the Branch steps. You enter both in Branch next. The secret is shown only in this dialog; afterwards the app's Access card keeps a preview. The Callback address is for reference: Branch fills it in from the two values.
The app then shows under Setup, Mobile app. Its Access card shows the Integration ID again, with a copy button. Lost the secret? On the Access card, press Replace beside Secret, type a new one of at least 32 characters or press Generate, then press Replace. The old secret stops working at once, so enter the new one in Tapper's partner form in Branch.
Configure the Branch dashboard
Tapper is a listed Branch ad partner, so there is nothing to build by hand. Enable Tapper, give it the two values, and widen the postbacks.
Tick All Events on every Tapper postback, and leave any condition or filter empty. Lift compares your Branch numbers with Google's and Meta's, so it needs every install and event, whichever network Branch credits. Left scoped to attributed traffic only, a postback fires only for events already attributed to Tapper, and Lift receives nothing.
In your Branch dashboard, open Ads Partners, then Partner Management, search for Tapper, and enable it.
Tapper's form in Branch asks for two values:
| Branch field | Where to get it |
|---|---|
| Integration ID | The numeric Integration ID on the app's Access card. |
| Webhook Secret | The secret you copied when you switched on Block. Tapper shows it only once. |
Tick All Events on every Tapper postback, and leave any condition or filter empty. Do this before you save.
Save the partner configuration. Events appear in Tapper within minutes.
Branch sends one postback per event, so enable every event that counts as a result for your app: installs, reinstalls, opens, purchases and any custom events your app fires.
What Lift reads
From each Branch postback, Lift uses:
- Attribution: network, campaign, ad group and ad, from Last Attributed Touch Data. This is how each result is matched to your Google Ads and Meta Ads campaigns.
- Activity type: install, reinstall, app open or in-app event.
- Revenue: amount and currency, from Event Data.
Paid and organic
A result Branch attributes to an ad network counts as paid. A result with no attributed network counts as organic.
Event names
Branch writes event names in different ways:
- System events are lowercase:
install,reinstall,open. - Standard commerce events are uppercase:
PURCHASE,SUBSCRIBE,ADD_TO_CART. - Custom events use whatever name your app gives them.