Before you connect
The following are required:- A Branch dashboard account with API access.
- A Branch app key (sometimes labeled “account key”) — typically 32+ characters, beginning with
key_live_…orkey_test_…. - The matching Branch API secret.
- The Branch app ID for the app to connect.
Connect Branch
1
Open the Branch data source
On the Data Sources page, search for Branch and select it.
2
Enter the key and secret
Fill in the Key and Secret gathered from the Branch dashboard. Keys shorter than 10 characters are rejected — re-copy the full value from Branch if validation fails.
3
Submit the credentials
Click Submit to proceed to the data source settings.
4
Configure the data source
Fill in the Account ID with the Branch app ID, then set an Account Name to distinguish among multiple Branch data sources.
5
Submit
Click Submit to complete the connection. Initial data availability can take up to one business day. The first sync backfills the previous 180 days, and subsequent refreshes run daily and update the most recent 5 days.
What gets imported
The connector reads daily attribution and performance data for the connected Branch app: clicks, installs, opens, purchases, cost, and standard or custom in-app events. Reports arrive at daily granularity with 12 attribution breakdowns — campaign, ad set, ad, creative, keyword, and advertising partner, plus matching ID variants and link tags — all derived from Branch’slast_attributed_touch_data_tilde_* fields. Custom in-app events defined in Branch appear automatically the first time they fire.
For the complete metric list, breakdown-to-field mapping, refresh cadence, and limits, see the Branch data reference.
Troubleshooting
App key is too short
App key is too short
Branch app keys are typically 32+ characters; the connector rejects values under 10. Re-copy the full key from the Branch dashboard under Account Settings → Profile.
INVALID_CREDENTIALS error
INVALID_CREDENTIALS error
The app key and secret do not match, or one has been rotated in Branch. Regenerate or reconfirm both values in the Branch dashboard, then update the data source.
Some days show no data
Some days show no data
Branch does not return rows for date and breakdown combinations with no activity, and the connector does not add empty rows. A campaign with no events on a given day is absent rather than reported as zero. Confirm in the Branch dashboard that the campaign was active for the date in question.
Breakdown values appear as unknown
Breakdown values appear as unknown
When Branch cannot attribute an event to a specific value for a breakdown, the literal string
unknown is stored to keep groupings consistent in dashboards. A large unknown group usually points to traffic Branch could not attribute to a specific campaign or creative.Backfills are slower than expected
Backfills are slower than expected
Branch enforces 150 API requests per rolling hour, shared across all Branch data sources in the same process. Long backfills with many breakdowns can queue once usage crosses the 135-request safety buffer, then resume after the hour resets.
Related
Branch data reference
Metrics, breakdowns, refresh cadence, and limits for Branch.
Branch FAQs
Common questions and expected behaviors for the Branch data source.
How to connect AppsFlyer
Connect AppsFlyer, an alternative MMP with broader event coverage.
How to connect Adjust
Connect Adjust, another mobile measurement partner.
