Branch
Branch is a mobile measurement and deep linking platform that unifies user measurement across different devices, platforms, and channels.
Features
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | ||
History mode | ||
Custom data | ||
Data blocking | check | |
Column hashing | check | |
Re-sync | check | |
API configurable | check | API configuration |
Priority-first sync | ||
Fivetran data models | ||
Private networking | ||
Authorization via API |
Supported deployment models
We support the SaaS Deployment model for the connector.
Setup guide
Follow our step-by-step Branch setup guide to connect Branch with your destination using Fivetran connectors.
Schema information
We sync the events using Branch's webhook system into a primary standard table, EVENT
.
See Branch's documentation for more information on the Event Ontology data schema.
Undisclosed data
We convert "undisclosed" data for all data types from the source to null
in your destination tables.
The event_data
object is used to sync the following columns:
event_data_transaction_id
event_data_revenue
event_data_revenue_in_usd
event_data_exchange_rate
event_data_currency
event_data_shipping
event_data_tax
event_data_coupon
event_data_affiliation
event_data_search_query
event_data_description
event_data_ad_type
The event_data
object is only passed in webhooks for Branch Standard Commerce and Content events. If the webhooks are not configured to send these events, the Branch API doesn't send the event_data
object and the above columns contain null
values.
Custom fields
The last_attributed_touch_data_type
column is a custom column that we get from Branch. We expect an integer value for this column. If the value isn't an integer, we write null
for this column in the destination.
Automatically hashed data
Branch automatically salt and sha256 hashes certain data parameters over time. Learn when each parameter is hashed in Branch's Data Branch Automatically Hashes documentation.
If these hashed values are re-sent by Branch to your connection, Fivetran cannot unhash these values. This may result in data integrity issues in your destination table and type-widening of the data types of your columns.