Branch
Source — Vendo imports install attribution data from the Branch Daily Exports API.
What Vendo Syncs
Install Attribution Data
| Field | Description |
|---|---|
| Timestamp | When the install happened (Unix epoch) |
| Campaign | Attributed campaign name |
| Campaign ID | Campaign identifier |
| Channel | Marketing channel |
| Feature | Branch feature tag |
| Ad Set Name | Ad set / ad group |
| Ad Name | Ad creative name |
| Click Timestamp | When the attributed click/touch happened |
| Device ID | IDFA (iOS) or AAID (Android) |
| Country | User’s country |
| OS | iOS or Android |
Device Properties
| Property | Description |
|---|---|
| IDFA | iOS advertising identifier |
| AAID | Android advertising ID |
| IDFV | iOS vendor identifier |
| OS | Operating system |
| Country | Geo country |
| Language | Device language |
| Environment | App environment |
Identity Resolution
Branch provides device-level identifiers (IDFA/AAID) that Vendo joins with your identity graph:
- IDFA (iOS) and AAID (Android) are matched against the identity graph
- Matched installs are linked to their cross-platform vUID (Vendo User ID)
- Post-ATT installs without IDFA remain in the dataset but without identity links
Unified Mobile Schema
Branch data is normalized into the mobile_installs table alongside AppsFlyer and Adjust data for cross-MMP analysis.
Setup
- Log into your Branch Dashboard
- Navigate to Account Settings
- Copy your Branch Key (starts with
key_live_orkey_test_) - Copy your Branch Secret
- Ensure Data Feeds is enabled (requires Data Feeds subscription)
- In Vendo, go to Apps → Add App → Branch
- Paste your Branch key and secret
- Create a source and trigger your first sync
Requirements
- Data Feeds subscription required (Branch paid feature)
- Admin access required in Branch dashboard
- Data Export API must be enabled via Data Feeds Manager
API Details
| Setting | Value |
|---|---|
| API | Daily Exports API (async) |
| Auth | Access-Token header |
| Sync Frequency | Daily |
| Data Format | Gzipped CSV (S3 presigned URLs) |
| Export Process | Submit → poll → download |
| Historical Data | 7 days (full device IDs), older data has hashed fields |
How It Works
Branch uses an async export pattern:
- Vendo submits an export request for install events
- Branch processes the export and returns S3 download URLs
- Vendo downloads the gzipped CSV files
- Data is parsed, normalized, and loaded into BigQuery
Export processing typically takes 1-10 minutes depending on data volume.
BigQuery Tables
| Table | Description |
|---|---|
branch_{id}_installs | Raw Branch export data |
branch_{id}_mobile_installs | Normalized unified schema |
Last updated on