Branch
Connect Branch mobile attribution and deep-linking to Ours Privacy so your app's Install, Open, Purchase, and custom events flow into your event pipeline.
Branch
The Branch source brings your mobile app's attribution and engagement events into Ours Privacy. Once connected, Branch sends events like Install, Open, Purchase, Add to Cart, Complete Registration, and your own custom events into your event pipeline, where you can route them to destinations alongside your web and server-side events.
Ours Privacy is set up with Branch as a managed Data Integration partner, so you do not configure a webhook URL by hand. You copy one key from Ours Privacy and paste it into your Branch integration.
What you get
- Mobile events in one place. App-side events join your web and server-side activity, so a person's mobile and browser behavior live on the same profile.
- Standard and custom events. Branch's standard events map to readable names automatically (
PURCHASEbecomesPurchase,ADD_TO_CARTbecomesAdd to Cart). Custom event names pass through unchanged. - Attribution and device context. Campaign, channel, ad set, creative, platform, OS, and commerce details (revenue, currency, transaction ID) arrive as event properties.
- No mapping required. The Branch source ships ready to use. You do not need to configure field mappings for events to land correctly.
How to connect Branch
- In Ours Privacy, open the Sources section and create a new Branch source.
- Copy the Branch Key shown in the source settings. This key identifies your account, so keep it secret.
- In your Branch dashboard, enable the Ours Privacy data integration and paste the key where Branch asks for it.
- Trigger an event in your app (or use Branch's test tooling), then open the Recent Events Dashboard in Ours Privacy to confirm the event arrived.
How people are identified
Branch events are matched to a person using the developer identity you set in Branch for the logged-in user. Set this identity in your app so mobile events tie back to the same profile as the rest of that person's activity. Events without a developer identity are still ingested, but they cannot be linked to a known person until an identity is available.
Next Steps
- Webhooks: send events from any other external system.
- Recent Events Dashboard: verify and debug incoming events.
If you have questions about connecting Branch, reach out to support@oursprivacy.com.
How is this guide?