DatriseAI-first ETL

Branch to ThoughtSpot Integration

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

How Datrise loads Branch into ThoughtSpot

Datrise syncs Branch's links, clicks, installs, events, attribution touchpoints, and campaigns into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

Branch: Deep linking and mobile attribution.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How Branch entities map to ThoughtSpot

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

FAQ

How does Datrise handle Branch's custom fields in ThoughtSpot?

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

How does the Branch to ThoughtSpot sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the indexed tables.

Related pipelines

Early access

Connect Branch to ThoughtSpot 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.