CONNECTIONS / Branch
Branch installs and links, credited across ad platforms
Branch tracks the deep link click, the install it drove, and the purchase that followed inside the app. Signals carries that chain through to Meta, Snap, and TikTok as a hashed app conversion, including installs that started as a web session.
- ● branch :: signals live
- > deep link click campaign=summer_sale
- > in-app event purchase value=55.00 AED
- hash sha256(email,phone) journey=web_to_app
- route meta · snap · tiktok
- ✓ 3 destinations synced · match 79%
The signal Branch yields.
Every kind of signal that moves between Branch and the platforms, through one hashed, deduplicated route.
- App conversions
- The campaign and channel behind a deep link click travel with the install it drove, straight through to every destination.
Pick your platform. Every use case for it, in one place.
Every way Branch data moves, grouped by platform and ranked by how many use cases Branch supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Point Branch webhooks at Signals
Branch's install and event webhooks connected to Signals alongside the deep link click data Branch already tracks.
-
Map link and event fields
Deep link parameters, install attribution, and in-app events mapped to each destination's app-conversion schema for Meta, Snap, and TikTok.
-
Reconcile the journey
A web session and the app install it drove tied back together, identifiers hashed, and the event deduped against SDK traffic on Branch's event ID.
-
Deliver with match feedback
Server-side delivery to Meta, Snap, and TikTok, with per-destination match results visible in the live debugger.
Branch questions, answered.
Does this page cover deep linking, attribution, or both?
Both, because Branch ties them together. A Branch deep link click carries campaign and channel data, the install or in-app open it drives is a separate event, and Signals reads both off Branch's postbacks rather than treating the click as the conversion. Only the install and the in-app events that follow it become app conversions sent to Meta, Snap, and TikTok.
How does a web-to-app Journey get credited correctly?
Branch attributes it correctly already, crediting the install to the web session's campaign and channel rather than to organic. Signals reads that attribution straight off the Branch postback, so a visitor who tapped a Branch link on a mobile site and finished the install later still lands on the same campaign when the resulting purchase reaches Meta, Snap, or TikTok.
Do our existing Branch integrations to ad networks need to change?
Only a webhook needs adding. Branch's own integrations to a given ad network can stay configured for whatever they already forward, and Signals reads the same install and event postbacks in parallel, deduped on Branch's event ID. A network already receiving a Branch-attributed install through its native integration will not receive it a second time from Signals.
What happens when a user declines ATT tracking?
IDFA disappears from the postback, but Branch still resolves the install through its own probabilistic and deferred deep-linking match, so the event still arrives with a campaign and channel attached. Signals forwards whatever identifier remains, a hashed email from an in-app login or a GAID on Android, so the app conversion still has something a destination can match against.
NEXT STEP
See your Branch data working in every ad platform.
Ready to enable a use case, or still mapping what Branch data could do? Our team helps you find the right place to start.
