Question 1

What Gong data can I load into BigQuery?

Accepted Answer

Calls with their metadata, participants, context, topics, trackers and tracker occurrences, plus interaction data. Separately there are transcripts, keyword tracker definitions, scorecards and answers, users, workspaces, library folders and contents, and Engage flows. Tracker hits tend to be the most immediately useful table, because a hit is a countable structured signal, whereas a transcript is text you still have to do something with.

Question 2

How do nested Gong call structures land in BigQuery?

Accepted Answer

As native BigQuery types on current connections, which is a real advantage here. Objects become RECORD and lists become repeated fields, so a call's participants or tracker occurrences stay queryable with dot notation instead of being flattened or stringified. Two details worth knowing: connections created before a 2024 change write structured values as JSON instead, and because BigQuery has no array of arrays type, a nested list falls back to JSON.

Question 3

Are Gong reads incremental?

Accepted Answer

For calls and transcripts, optionally yes. Those use a time watermark with a rolling seven day lookback, which matters because a transcript is not ready the moment a call ends. Be clear on the limits though. This is not complete change capture, and a change landing outside the window can be missed. If completeness matters, run a periodic full read alongside the incremental schedule rather than trusting the watermark alone.

Question 4

Does Polytomic remove deleted Gong calls from BigQuery?

Accepted Answer

Not automatically, because Gong has no delete feed for this connector. Treat it as a snapshot source. Nothing produces a tombstone, so a call removed in Gong stays in your table until a full read reconciles it. That is why the incremental path should not be described as delete aware even though it genuinely is incremental. If your reporting counts calls, schedule an occasional full read so the totals do not drift.

Question 5

Why put Gong conversation data in BigQuery?

Accepted Answer

Because a recording is not an answer. Customers describe wanting Gong in the data warehouse first so they can shape it, join it to accounts and opportunities, and only then act on the result. ETL makes tracker hits and transcript text sit next to CRM records, so a question like which objections show up before a deal is lost becomes SQL rather than an afternoon of listening.

Sync Gong to BigQuery

Sync Gong to BigQuery with Polytomic

Nested data stays nested

Calls, transcripts, trackers

Catches late transcripts

Or sync BigQuery to Gong

Trusted by businesses worldwide

Step-by-step integration guide

Connect Gong in Polytomic

Connect BigQuery in Polytomic

Create a sync between Gong and BigQuery

Map fields and enable the sync

Frequently asked questions

The sync and ETL platform that does it all

Powerful data sync

Advanced analytics

Enterprise security

Easy setup

Ready to connect Gong with BigQuery?