Branch Integration
Connect Branch to Tapper to detect fraudulent installs and in-app events across your mobile campaigns.
Create the Integration in Tapper
Open Your Protection Script
Go to Mobile App Protection and open the protection script for your app.
Add MMP Integration
Click Add MMP Integration, choose Branch as the MMP type, and give it a name.
Set a Webhook Secret (Recommended)
Enter a random string as the Webhook Secret. Tapper will use this to verify that incoming callbacks are legitimate.
Copy the Webhook URL
After saving, copy your Tapper webhook URL. You'll paste it into Branch next.
Configure in Branch Dashboard
Branch does not have a Global Callback. You need to create a separate webhook for each event type you want Tapper to receive.
Open Data Feeds → Webhooks
In your Branch dashboard, go to Data Feeds → Webhooks and click Add New Webhook.
Set the URL
Paste your Tapper webhook URL.
Select Event Type
Choose the event type for this webhook. Common events to track:
| Event | Branch event name |
|---|---|
| Install | install |
| Reinstall | reinstall |
| App open | open |
| Purchase | PURCHASE |
| Subscribe | SUBSCRIBE |
| Add to cart | ADD_TO_CART |
| Custom events | Your custom event name |
Repeat for Each Event
Create a separate webhook for each event type you want Tapper to analyze.
To receive everything, create webhooks for install, reinstall, open, and all commerce or custom events your app fires.
You can use the same Tapper webhook URL for all event webhooks — no need to create separate integrations in Tapper.
What Data Is Captured
Once connected, Tapper automatically receives the following from Branch on every postback:
- Attribution — network, campaign, ad group, creative, and ad IDs.
- Activity type — install, reinstall, app open, or in-app event.
- Device info — IDFA (iOS), GAID (Android), device model, OS version.
- Geolocation — IP address, country.
- Revenue — amount and currency (for purchase events).
Organic vs Paid
Tapper automatically distinguishes organic and paid activity based on the attribution data Branch provides:
- If an ad network is attributed → paid.
- If no ad network is attributed → organic.
Event Naming
Branch uses different casing conventions for event names:
- System events — lowercase:
install,reinstall,open. - Standard commerce events — uppercase:
PURCHASE,SUBSCRIBE,ADD_TO_CART. - Custom events — whatever name your app uses.