Beyond call recording: getting real ROI from Gong
Most teams treat Gong as expensive call storage. The return is in coaching, deal execution, and forecast accuracy. Here is how to move from recording to results.
Read the full post → The Practice
Gong is most valuable when it is not a separate tool.
Gong on its own is useful. Gong wired tightly into Salesforce and the rest of your revenue stack is a different thing entirely: forecast data, activity, and conversation insight all living in one system instead of scattered across tabs. When the integration is shallow, managers bounce between tools and the data never quite agrees. When it is deep, the revenue team works from a single source of truth.
What we actually do
We build the bi-directional sync between Gong and Salesforce, surface Gong forecast data inside Salesforce where managers already work, automate Gong Engage workflows with Salesforce Flow, and integrate the adjacent tools, ZoomInfo, Outreach, DocuSign. We also handle migrations onto Gong, including Chorus.io call history and Outreach content, so nothing is lost in the switch.
Where integrations go wrong
The common failures: a sync that moves data but does not surface deal risk where decisions get made, forecast insight trapped in Gong instead of in the Salesforce pipeline review, automation that breaks the first time a record looks different, and a migration that quietly drops call history or content. We build the integration so the data agrees, the insight shows up where managers work, and the migration loses nothing.
Why Abstrakt Solutions
We run both the Gong and the Salesforce practices, and as a Salesforce Consulting Partner since 2017 and a Gong services partner, the integration between them is core to how we work. The goal is one revenue system, not two tools that occasionally talk. We are an independent Gong services partner; Gong.io is not a party to our engagements.
What We Deliver
How we help with Gong + Salesforce Integration.
The engagements we run most often on Gong + Salesforce Integration, from first implementation through optimization.
Gong-Salesforce Sync
Bi-directional sync so calls, activities, and insights log against the right accounts, opportunities, and reps.
Forecast Data in Salesforce
Configure and enable Gong Forecast data inside Salesforce with proper mapping, validation, and dashboards.
Gong Engage Automation
Salesforce Flow design and build for routing, data updates, and integration points across Gong Engage.
Chorus.io Migration
Migrate call history and metadata from Chorus.io to Gong without losing your archive.
Outreach Content Migration
Move sequences, snippets, and templates from Outreach into the Gong ecosystem.
Outcomes We Deliver
The metrics we actually move with Gong + Salesforce Integration.
Engagements are measured by movement on the numbers that matter. These are the directions of travel we commit to.
Data consistency CRM and Gong
Single source of truth
Manual logging
Reduce sharply
Forecast workflow
Unified in Salesforce
How We Work
The engagement model.
Predictable phases. Clear deliverables. No surprises.
01
Discovery
One to two working sessions to map your current state, business goals, and gaps. We come out with a written scope and recommendation.
02
Design
Documented architecture, realistic timeline, and transparent commercial proposal. No surprises and no hidden scope.
03
Build
Configuration, development, integrations, data migration, and QA, with weekly demos and on-the-fly adjustments.
04
Launch & Optimize
Training, change management, hypercare, and ongoing optimization. We do not disappear at go-live.
Featured Insight
Insights on Gong + Salesforce Integration.
Consultant-level analysis from the consultants delivering the work.
Revenue Operations
Inside Gong + Salesforce Integration
What Gong + Salesforce Integration actually includes.
Salesforce data import into Gong
Gong reads accounts, opportunities, contacts, leads and users from Salesforce through an OAuth connection, and admins choose which standard and custom fields come across. Those fields let managers filter conversations by stage, amount or segment. Multi-select, address, location and encrypted fields cannot be imported, so plan alternatives if your segmentation depends on them.
Conversation-to-record matching
Gong matches call and email participants to Salesforce contacts, leads and accounts by email address and domain. When an account has one open opportunity, the conversation attaches there; with several, Gong chooses using opportunity owner and last modified date. Reps can reassign a call from its call page when the automatic choice lands on the wrong deal.
Gong for Salesforce managed package
The managed package adds a Conversation object with related child records for participants, trackers, briefs and interaction stats, plus canvas apps showing highlights and transcripts on record pages. Gong Users and Gong Admin permission sets control access. Because each exported call creates many child records, check data storage headroom before exporting historical calls in bulk.
Activity logging as Salesforce tasks
Gong can log recorded conversations as tasks under the matched contacts, and captured emails may export as tasks depending on company settings. That gives reps activity history without manual logging. Decide early whether Gong, Einstein Activity Capture or another tool owns activity logging, because two sources writing tasks produce duplicates that distort activity reports.
Deal board edits that write back
Reps and managers can edit opportunity fields directly on Gong deal boards. Gong checks the user’s Salesforce permissions and validation rules before saving, and rejected edits revert with an error message. Salesforce stays the record of truth, so the field-level security, required fields and validation rules you already maintain govern what Gong users can change.
Forecast boards built on CRM fields
Gong Forecast takes its categories from your CRM. Admins map the fields that define actuals, open deals and each forecast category, usually stage and forecast category. Gong also pulls amount, close date, owner and opportunity type. If those picklists are inconsistent across teams, the forecast board inherits the mess rather than correcting it.
Good fit
When Gong + Salesforce Integration is the right call.
- Opportunities, contacts and account ownership in Salesforce are reasonably clean, so conversations can attach to the right deal without reps fixing associations by hand.
- Sales leaders want conversation evidence, such as next steps and competitor mentions, visible on the Salesforce opportunity where pipeline reviews already happen.
- Reps spend meaningful time logging calls and emails, and you want activity history captured automatically against matched contacts instead of entered after each meeting.
- Managers run forecast calls from Gong boards but need every committed change to land on the Salesforce opportunity, respecting validation rules and field permissions.
- Revenue operations wants to report on call trackers, talk ratios or scorecard results alongside Salesforce pipeline data in one reporting layer.
Think twice
When something else fits better.
- Contacts are routinely missing email addresses or tied to the wrong accounts; matching depends on email and domain, so association will fail until hygiene improves.
- Your team already records calls in a Salesforce-native tool such as Einstein Conversation Insights and mainly needs transcripts on the record, not deal and forecast boards.
- Salesforce data storage is close to its limit and cannot absorb the many child records each exported conversation creates without purchasing additional capacity.
- No administrator can own field mappings, permission sets and association exceptions after launch, so mismatched calls and failed writebacks would pile up unnoticed.
Rollout
How a Gong + Salesforce Integration rollout comes together.
- 01
Audit data before connecting
Before authorizing anything, check the Salesforce data Gong will depend on: contact email coverage, account domains, duplicate accounts, opportunity ownership and forecast category values. Fix the patterns that will break matching, such as personal email addresses on business contacts or several open opportunities per account without clear owners. Cleaning first is far easier than reassociating thousands of calls later.
- 02
Create a dedicated integration user
Set up a Salesforce user reserved for Gong so the connection survives staff changes. Grant read access to accounts, opportunities, contacts, leads, stage and history objects, plus write access to tasks and Gong objects if you export data. Add the Approve Uninstalled Connected Apps permission, then approve the Gong connected apps for that user.
- 03
Install the package and map fields
Test the Gong for Salesforce package in a sandbox first, noting that only one instance, sandbox or production, connects to Gong at a time. Assign the Gong Users and Gong Admin permission sets and add the Conversations related list and canvas components to page layouts. Then choose which fields Gong imports for filtering and boards.
- 04
Decide what writes back
Agree which Gong outputs belong in Salesforce: tasks for calls and emails, conversation records, trackers or opportunity edits from deal boards. Check which system already logs activities to avoid duplicates. Confirm validation rules and field-level security produce sensible errors for Gong users, and watch API consumption during any historical export, since each call triggers its own request.
- 05
Monitor associations and adoption
After launch, review unassigned and misassociated conversations weekly, trace recurring causes back to contact or account data and fix them at the source. Check that forecast boards reconcile with Salesforce reports and that rejected deal board edits are understood. Retire manual logging steps only once reps trust that automated activity capture is complete and accurate.
Before you buy licenses
Gong is licensed directly by Gong. The Salesforce connection and Gong for Salesforce managed package are generally part of the Gong platform rather than a Salesforce purchase, but confirm this for your agreement. Packaging changes over time, so ask Gong which modules you hold, such as Forecast or Engage, and whether deal and forecast boards need a specific tier. On the Salesforce side, confirm your edition supports API access and managed packages. Check data storage for exported conversation records, and decide whether the integration user can run on an API-only integration license. Finally, ask both vendors how their terms treat call data stored in Salesforce, especially retention and deletion.
Avoid These
Common Gong + Salesforce Integration mistakes.
Connecting before cleaning contacts
Teams often authorize the integration first and discover afterward that many calls are unassigned or attached to the wrong opportunity. Because matching relies on email addresses and domains, missing emails, shared personal addresses and duplicate accounts all break it. Budget time for contact and account cleanup before launch, and track unassigned conversations as an ongoing data quality signal.
Using an admin’s personal login
When the connection runs under an administrator’s own Salesforce user, deactivating that person quietly stops the sync. Their broad permissions also hide missing object access that surfaces later. Give the connection its own integration user, limited to the objects Gong needs, document its permission sets and include it in your offboarding and credential review checklists.
Letting two tools log activities
Gong, Einstein Activity Capture, a dialer and a sales engagement tool can all create tasks for the same meeting or email. The result is inflated activity counts, cluttered timelines and reports nobody trusts. Pick one system of record for each activity type, turn off the overlapping settings and test with a handful of reps before enabling broadly.
Ignoring deletions and storage
Deleting a call in Gong, including through retention policies, also deletes the related meeting record in Salesforce. Teams that assume Salesforce keeps an archive can lose history they expected to keep. Align Gong retention with your records policy, confirm legal and compliance agree, and monitor the data storage consumed by conversation child records as volume grows.
FAQ
Gong + Salesforce Integration questions.
Does Gong change our Salesforce opportunities?
Only in defined ways. Gong mostly reads opportunity data to power search, deal boards and forecasts. It writes when users edit fields on deal boards, or when admins enable exports of tasks and conversation data. Deal board edits pass through the user’s own Salesforce permissions and validation rules. A rep cannot change a field in Gong that they could not change in Salesforce.
Why are some calls not attached to any opportunity?
Gong associates conversations by matching participant email addresses and domains to Salesforce contacts, leads and accounts. If no participant matches, or the matched account has no open opportunity, the call stays unassociated. With several open opportunities, Gong picks one using owner and last modified date, which is sometimes wrong. Reps can reassign calls manually, but recurring gaps usually point to contact data that needs fixing.
How much Salesforce API capacity does Gong use?
Gong’s documentation describes roughly one API call per exported recorded call, with that call creating a set of child records. Everyday usage is usually modest, but spikes appear during historical exports or when tracker changes trigger reprocessing of past calls. Check your org’s daily allocation, schedule large backfills during quiet periods and watch consumption alongside other integrations that share the same limit.
Can we test the integration in a sandbox?
Yes, but only one Gong for Salesforce instance, production or sandbox, connects at a time. A sensible approach is to validate the package, page layouts, permission sets and field mappings in a sandbox, then reconnect to production for go-live. Plan the switch deliberately, because conversations exported while pointed at the sandbox would not automatically appear in production. Confirm the current procedure with Gong support first.
Should forecasting live in Gong or in Salesforce?
Gong Forecast builds on Salesforce fields, so the real question is where managers prefer to work. Gong boards add conversation context and deal activity beside the numbers, while Salesforce Collaborative Forecasts and native reports suit teams that want everything in one platform. Either way, keep forecast categories, stages and amounts defined in Salesforce, and make sure submitted numbers reconcile with Salesforce reporting.
Related Platforms
Other Gong platforms we implement.
Gong Practice Overview
A Gong services partner: implementation, optimization, training, and integration as an independent partner.
Gong Implementation
Stand Gong up right, from Foundation to Forecast, packaged by scope so revenue teams actually adopt it.
Gong Optimization
Already on Gong but underusing it? An audit-led tune-up that turns Gong into a real revenue engine.
Gong Training & Enablement
Role-based Gong enablement that drives adoption, for reps, managers, and revenue leaders.