Event tracking helps you understand how a user moves through your app and what actions they are taking along the way. Commerce, Content, and User Lifecycle events can all be tracked this way.
View Branch.io's documentation and status page.
Supported syncing
| Sync Type | Description | Supported Sync Modes | API Reference |
|---|---|---|---|
| Events | Sync data from any source to Branch.io events | Insert | GitHub docs and Event docs |
For more information about sync modes, refer to the sync modes docs.
Connect to Branch.io
Go to the Destinations overview page and click the Add destination button. Select Branch.io and click Continue. You can then authenticate Hightouch to Branch.io.
Enter the following fields into Hightouch:
- App ID
- Branch Key
- Branch Secret
All of these fields can be found by managing the your Branch.io profile settings. The Branch Key and Branch Secret are considered sensitive information.
Sync configuration
Once you've set up your Branch.io destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Branch.io destination you want to sync to.
Syncing events
Sync data from any source to Branch.io events.
Field mapping
Hightouch lets you sync event properties via field mapping.
At least one of the following fields must be mapped so that events can be uniquely identified with a user:
- Developer Identity
- Browser Fingerprint ID
- IDFA
- IDFV
- AAID
- Android ID
Tips and troubleshooting
Common errors
To date, our customers haven't experienced any errors while using this destination. If you run into any issues, please don't hesitate to . We're here to help.
Live debugger
Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.
Sync alerts
Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.