Deal signals (like amount, intent, and timing) often consist of values from several different fields across multiple child records, such as meetings, usage logs, or product line items. These objects can’t be imported to Gong, however, you can make this data available in Gong by rolling it onto a supported parent object, such as the opportunity.
This approach is useful when you want to:
Display additional data in Gong
Map to a non-standard object
Write Gong insights into a specific field
Support an alternative to Salesforce opportunities
Trigger an engagement flow when data changes
Roll up custom object data into a report or forecast
Once rolled up, this data can be used in Gong Forecasting and reporting. Fields that may consist of data from additional fields include:
Amount: To forecast the opportunity amount, you may need additional information such as the license count, usage volume, or expansion requests
Intent: To assess customer intent, you may need information on customer-facing meetings or activity signals.
Date: To track deal activity, you may need information such as the most recent meeting or usage spike.
Define the objects as parent/child
To roll data up onto an object that can be imported, such as opportunity, contact, lead, or account, the child object must be directly related to the parent.
Supported relationship types:
Master-detail: works with native roll-ups
Lookup: required for Flow-based roll-ups
Tip:
Create a lookup field from the child object (such as Meeting, Usage Log, or Expansion Request) to the opportunity object.
Create a native roll-up summary field
If the child object has a master-detail relationship with the parent object, roll the child data up using a roll-up summary field.
Here are some example metrics you can track for forecasting:
Metric | Use case | Field type |
|---|---|---|
Amount | Total number of licenses in usage logs tied to opp | SUM(License_Count__c) |
Intent | Count of completed sales-led meetings | COUNT(Meeting__c where Status=Completed) |
Date | Latest customer-facing activity date | MAX(Activity_Date__c) |
To create a roll-up summary field:
In Salesforce, go to Setup > Object Manager > Opportunity > Fields & Relationships > New.
Select Roll-Up Summary as the field type.
Define the field settings:
Label: for example, Total License Count, Completed Meetings, or Last Touch Date
Summarized object: such as Usage_Log__c or Meeting__c
Roll-up type: SUM, COUNT, or MAX
Filters (optional): for example, Status = Completed for intent-based signals
Build a flow-based roll-up
Set up a flow in Salesforce if the child object has a lookup relationship with the opportunity, and there is a complex flow to rollup the data,.
Example: Count of completed meetings (intent)
Flow type: Record-triggered
Object: Meeting__c
Trigger: When created or updated
Condition: Meeting__c.Opportunity__c is not null and Status = Completed
Get records: All Meeting__c with the same Opportunity__c where Status = Completed
Assignment: Count the records or sum values
Update records: Update the opportunity with the number of completed meetings or total minutes engaged
Additional use cases
Other examples of data you might require:
Metric | Use case | Field type |
|---|---|---|
Amount | Sum expansion requests across related records | Expansion__c, SUM(Unit_Count__c) |
Intent | Count meaningful executive sponsor activities | Filter Activity__c by role/title, COUNT() |
Date | Most recent usage spike or activity | MAX(Activity_Date__c) |
Note:
Setting up and testing roll-ups typically takes 2–4 hours, depending on the number of child objects and fields you want to include.