DatriseAI-first ETL

Branch to Amazon QuickSight Integration

AI-first ETL from Branch into Amazon QuickSight. Governed entities, incremental sync, typed landing tables.

How Datrise loads Branch into Amazon QuickSight

Datrise syncs Branch's links, clicks, installs, events, attribution touchpoints, and campaigns into Amazon QuickSight as warehouse tables or a SPICE-loaded dataset. Flexible or custom fields land in flattened columns for analyses, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind SPICE or direct query, so re-runs update only what changed. Date-partitioned facts to bound SPICE refresh. QuickSight SPICE is an in-memory copy, so Datrise keeps the backing tables incremental so refreshes stay cheap.

Ideal for AWS-native dashboards with pay-per-session pricing.

Endpoints

Branch: Deep linking and mobile attribution.

Amazon QuickSight: AWS serverless BI with SPICE and embedded analytics.

How Branch entities map to Amazon QuickSight

Branch entityAmazon QuickSight objectNotes
linksbranch_linksid PK · custom fields → flattened columns for analyses
clicksbranch_clicksid PK · linked to branch_links
installsbranch_installsid PK · linked to branch_links
eventsbranch_eventsdate/time fields events

FAQ

How does Datrise handle Branch's custom fields in Amazon QuickSight?

Flexible values are stored as flattened columns for analyses, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Amazon QuickSight types.

How does the Branch to Amazon QuickSight sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind SPICE or direct query.

Related pipelines

Early access

Connect Branch to Amazon QuickSight the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.