DatriseAI-first ETL

Gong to Tableau Integration

AI-first ETL from Gong into Tableau. Governed entities, incremental sync, typed landing tables.

How Datrise loads Gong into Tableau

Datrise syncs Gong's calls, transcripts, deals, users, trackers, and call topics into Tableau as warehouse tables or a refreshed .hyper extract. Flexible or custom fields land in flattened columns for Tableau fields, and timestamps such as created, updated, and status changes are typed as date/datetime fields.

Sync is incremental: Datrise uses incremental refresh of the tables behind a live connection or extract, so re-runs update only what changed. Date-partitioned facts to keep extract refresh quick. Tableau .hyper extracts snapshot data, so Datrise keeps the source tables incremental and lets you choose live vs extract.

Ideal for visual analytics and dashboards in Tableau.

Endpoints

Gong: Revenue intelligence from recorded sales calls.

Tableau: Salesforce analytics platform for interactive dashboards and visual exploration.

How Gong entities map to Tableau

Gong entityTableau objectNotes
callsgong_callsid PK · custom fields → flattened columns for Tableau fields
transcriptsgong_transcriptsid PK · linked to gong_calls
dealsgong_dealsid PK · linked to gong_calls
usersgong_usersid PK · linked to gong_calls

FAQ

How does Datrise handle Gong's custom fields in Tableau?

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

How does the Gong to Tableau sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the tables behind a live connection or extract.

Related pipelines

Early access

Connect Gong to Tableau 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.