Gong captures and analyzes your sales calls, emails, and meetings. Connecting it as a data source through the Connectors library syncs that conversation-intelligence data into your Alta workspace, where it becomes training data for Alta and a foundation for your metrics, dashboards, and Luna analysis. Once it's flowing, you can measure call activity, talk patterns, and how conversations relate to pipeline — and ask Luna questions in plain English. Gong connects with credentials (an API access key and secret).

Who this is for: Sales, RevOps, and enablement teams who want Gong call and engagement data analyzed alongside the rest of their pipeline in Alta.

Before you start

Generate a Gong API key (access key + secret) from Gong's company settings → API. You typically need admin rights to create API credentials.
Decide whether you need full transcripts — they're powerful but high-volume (see Tips).
Connect a source only once per workspace. If Gong already shows Connected, edit the existing connection.

Connect Gong

Open Connectors from the sidebar.
Find Gong via the category tabs or the Search data sources box.
Click the Gong card to open the Create connector screen.
Fill in the connection fields shown (such as your access key and secret), then click Create.
Alta runs a connect test. If it fails you'll see The connect test has failed with Gong's error — fix the field and retry.
The card then shows Connected and Data is syncing until the first sync finishes.

Choose which tables sync

Open the connection. Gong brings in tables like calls, transcripts, and users.
Use the Synced toggle in the Gong tables section to control what's pulled in.
Turn off Show only synced tables to see everything available.

Key tables and fields synced

calls — one row per recorded conversation: id, title, started, duration, direction (inbound/outbound), scope, primaryUserId, participant and account associations
transcripts — sentence-level text per call: callId, speakerId, topic, start/end times
users — reps: id, emailAddress, name, title, active
interaction / stats (when available) — talk-ratio and engagement metrics per call

What you can ask this data

Once it's syncing, build it into metrics and dashboards or just ask Luna / Ask AI. For example:

"How many calls did each rep have last week?" — counts calls by primaryUserId and started.
"What's average call duration by team?" — averages duration joined to users.
"Which accounts have had the most call activity?" — counts calls by account association.
"What's the inbound vs outbound call mix?" — groups calls by direction.
"What topics come up most often in calls?" — analyzes transcripts.topic (when transcripts are synced).

Example use cases

Activity & coverage. Calls per rep and per account to see who's engaged and which deals are going quiet.
Conversation-to-outcome. Join call volume on a deal to whether it was won, to see how engagement relates to results.
Coaching & enablement. Surface talk patterns and recurring topics from transcripts to guide coaching.
Deal-risk signals. Flag opportunities with no recent call activity for follow-up.

Keep it in sync

Sync status shows Last sync (Succeeded/Failed) and the Sync frequency.
Click Sync now to refresh immediately; it's disabled while a sync runs.
Use the overflow menu (⋯) to Disable, Enable, or Delete.

Tips and common pitfalls

Transcript volume is large. Sync transcripts only if you need them — they grow quickly and lengthen sync times. Start with calls and users.
A failed connect test is usually the key. Re-copy both the access key and secret, and confirm the key is still active in Gong.
Associations power the best analysis. Keep account/deal associations so you can tie calls to pipeline.
Deleting is permanent. Disable instead to pause.