Mobile marketing and attribution
Supports cross-channel branded and tagged links so marketers can tie data to links, categorize features, campaigns, and tags, and send out via Facebook, email, or SMS to encourage actions like shares, signups, or deals
Enables full funnel measurements so marketers can analyze cross-channel conversions based on stage, tag, campaign or feature to discover clicks, installs, re-opens, or purchases
Sends in-app content to users with deferred deep links, contextual deep links, URL schemes, Android links, Apple iOS universal links, and Facebook app links and monitors for accuracy
How Branch works
Branch is powered by an SDK that will need to be installed into the code base of all your apps. There’s some pretty heavy configuration to get up and running with the main feature of Branch, which is deep linking. On top of initial setup you’ll need to learn the Branch SDK methods and add a line or more of code for every important event that people can do in your apps. If your app works across multiple platforms it’s recommended that you set an identity, usually a database user ID, which requires pulling that variable data from your database and triggering another native Branch method to identify people with it.
Get more out of Branch with Segment
Using Branch via Segment makes implementation significantly easier for several reasons. Getting the Branch SDK bundled and configured into Segment’s takes the same amount of customization as if you had installed the Branch SDK directly. You’ll need to re-build your Segment SDK to include the Branch SDK and complete the same deep linking configuration.
However, an important piece of deep linking and attribution is measuring conversions, and in many cases across multiple devices. When you use Branch through Segment, all your Segment events get passed along to Branch in the format it expects, so you don’t need to go back in your code and add a bunch of new webhooks for the same events. Those events can be attributed back to links, campaigns, and channels in your Branch reporting dashboard. If you’re identifying your users in Segment, the
userId gets set via the Branch
setIdentity method so events that user takes can be traced across various devices.