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: create the integration in Tapper, 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 created on Block's screens, so the workspace needs Tapper Block.
- Have your Branch Key and Branch Secret at hand. In your Branch dashboard, both are under Account Settings, then App, in the section Branch Key and Secret. Use the live ones: the key starts with
key_live_and the secret withsecret_live_.
Create the integration in Tapper
Open Add mobile app
Under Setup, open Ad accounts and click Add ad account. On the page that opens, click Add mobile app.
Fill in the integration
In Create MMP integration, give it a Name, choose Branch as the MMP type, and enter your Branch Key and Branch Secret. All of them are required.
Choose a webhook secret (optional)
Tapper uses the webhook secret to check that every postback really comes from your Branch. Leave it blank and Tapper generates one for you. If you choose your own, it needs at least 32 characters.
Copy the Integration ID and webhook secret
Click Create. On Integration created, copy the Integration ID and the Webhook secret: you enter both in Branch next. The secret is shown only this once. The Webhook URL is for reference only: Branch fills it in from the two values. Click Done.
The app then shows under Setup, Mobile app. On the app's page, the tab after Details shows the Integration ID again, with a copy button. Lost the secret? On that tab, 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.
Enable Tapper as an ad partner
In your Branch dashboard, open Ads Partners, then Partner Management, search for Tapper, and enable it.
Enter your Integration ID and webhook secret
Tapper's form in Branch asks for two values:
| Branch field | Where to get it |
|---|---|
| Integration ID | The numeric Integration ID on your Tapper integration. |
| Webhook Secret | The secret you copied when you created the integration. Tapper shows it only once. |
Send all events
Tick All Events on every Tapper postback, and leave any condition or filter empty. Do this before you save.
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.