This guide walks you through connecting Gong to Databook: a one way, read only connection that lets Databook receive your Gong calls and transcripts as they are processed, so conversation activity appears on the right account in Databook.
Before you start
Requirement | Why it's needed |
Access to the Databook GTM Control Center Admin Console | The integration is installed from the Integrations page of the admin console |
Gong sign-in credentials for the account you want to sync | You sign into Gong during install to authorize Databook's access. Use an account with visibility of the calls you want synced |
A user with the Gong Technical Administrator role | No other Gong role can complete part two of this guide |
Salesforce connected to Gong | Databook links each call to an account using the Salesforce records Gong attaches to it. Without this connection, calls are received but cannot be matched to an account |
Part one: install the integration in Databook
Databook uses Ampersand as the integration platform behind the Gong integration. Your Gong data is not persisted in Ampersand's systems.
1. Sign into the Databook GTM Control Center Admin Console and go to Config, then Integrations (link)
2. Under Intelligence and Data, select the Gong tile.
3. On the Install Gong Integration screen, you'll see four steps: Connect, Select Objects, Configure and Review. On the Connect step, click Next.
4. A Gong sign-in window opens. Sign in with Google, Salesforce or Office 365, or with your email address and password, then approve the access Gong asks you to grant.
5. On Select Objects, choose the Gong records to sync. Databook needs calls, transcripts and users, so leave all of these selected.
6. On Configure, review the field and frequency settings. The defaults are prefilled for Databook and should be left as they are unless your Databook contact has told you otherwise.
7. On Review, check the summary and confirm to complete the install.
Part two: how data syncs
Once installed, two schedules run automatically:
Databook reads calls and transcripts through the Gong API every 2 hours.
Databook processes that data every 6 hours, so it can be incorporated into your account intelligence.
A note on filters
Gong lets you restrict your automation rule, for example to specific participants or call types. We recommend leaving the rule unfiltered.
Databook applies its own filtering before anything reaches your account timelines, and that filtering is stricter than what most teams would configure in Gong. Any call your Gong rule excludes is never sent to Databook at all, which makes gaps harder to diagnose later. If you do need a Gong-side filter for policy reasons, tell your Databook contact what you've applied so it can be accounted for.
What Databook receives, and what it doesn't
Not every call that reaches Databook is used. A call must pass all three of the following checks before it appears on an account timeline:
Check | What it means |
Not private | Calls flagged as private in Gong are discarded, as are calls Gong classifies as internal |
Has both internal and external participants | Calls attended only by your own people, such as standups, pipeline reviews and one-to-ones, are discarded |
Linked to a Salesforce record | The call must carry a Salesforce lead, contact, account or opportunity. This is what tells Databook which account the conversation belongs to |
For calls that pass, Databook reads the call details and transcript, identifies material points such as stated requirements, stakeholders, competitive mentions, risks and next steps, and adds them to the relevant account's timeline.
Databook's access is read only. Nothing is written back into Gong, and no Gong content is modified or deleted.
When calls will appear
Gong sends the notification only after a call has finished processing and appears in your Gong call library, which can take several hours after the call ends. Transcripts can take up to 24 hours to become available.
In practice, expect a call to surface in Databook the following day. It will not appear within minutes of the meeting ending, and that delay comes from Gong's processing rather than Databook's.
Confirming it's working
Check that the Gong tile on the admin console Integrations page shows the integration as installed.
Hold, or wait for, a customer-facing call that has a Salesforce account or contact attached in Gong.
Allow a full working day after that call ends.
Open the account in Databook and check the timeline for events sourced from Gong.
If calls aren't appearing
Symptom | What to check |
No calls at all are reaching Databook | Check both halves of setup: that the integration shows as installed in the admin console |
Some calls appear, others don't | Check the missing calls against the three eligibility checks above, in order: private flag, participant mix, then Salesforce linkage. The third is the most common cause |
Calls appear but on the wrong account, or on no account | Check which Salesforce records Gong attached to the call. Databook follows Gong's own CRM linkage, so a mismatch there carries through |
Calls are missing from one team or region only | Check which Gong account was used to authorize the install. Its visibility determines which calls Databook can read |
A call from this morning isn't there yet | This is expected. Allow a full working day |
Filters were left on the Gong rule | Excluded calls are never sent, so they cannot be recovered after the fact. Remove the filter and tell your Databook contact |
Making changes later
To review or change what's synced, return to the Gong tile on the admin console Integrations page. It shows the current configuration and lets you update it.
To stop it permanently, uninstall the integration from the Gong tile in the admin console.
To load historical calls, raise this with your Databook contact. The automation rule covers new calls only.
Related article
Gong integration: what the integration does and what data it brings into Databook.