Conversation trackers become CRM data the moment they are mapped to a field. Drag trackers onto Opportunity fields and watch a taxonomy health index react to duplication, ambiguity and two-writer conflicts before they reach the forecast.
Fictional trackers, fields and owners. Nothing here reflects a real configuration. The health index is illustrative and meant to show how governance problems compound, not to measure any real system.
Drag a tracker onto a field, or click a tracker and then click a field. Hold Alt while dropping to copy instead of move.
Gong trackers
Salesforce Opportunity fields
One writer per field
A field edited by reps and written by a tracker has no owner of truth. Decide who writes it and enforce it.
Ambiguous signals stay as context
A tracker with known false positives is valuable for coaching and review, and dangerous as a field value.
Every tracker has a home or a reason
An unassigned tracker is an unowned definition. Mapping it to a field or marking it context only is a governance decision.
In a real environment
Data sources
Tracker definitions can be listed through Gong's settings API, and call data can include tracker matches, topics and highlights.
Field metadata comes from Salesforce describe and from the Tooling API FieldDefinition object, which exposes properties such as data type and whether field history is tracked.
Tracker ownership is not assumed to exist in either system. It is a registry the organization must create.
Limits and prerequisites
Gong API credentials are issued by a technical administrator.
Gong documents default limits of 3 calls per second and 10,000 calls per day for the company.
Salesforce API requests are pooled per org within a 24-hour period. For Enterprise Edition the allowance is 100,000 plus a per-license amount and any purchased add-ons, and exceeding it returns HTTP 403 REQUEST_LIMIT_EXCEEDED.
Gong's CRM API is described as import-only, so it cannot read CRM data back out of Gong. A public endpoint that links tracker results to Opportunity records was not found in the sources consulted. Confirm how tracker outcomes reach Salesforce in the target org.
How it would be validated
Estimate the precision of each tracker on a labeled sample of calls. Gong describes tuning trackers as an iterative balance between precision and volume.
Treat the Ambiguous flags in this demo as hand-assigned. In a real org they come from that measurement.
Run the conflict rules against the real field list and review the findings with the field owners.
What this demo does not claim: trackers, fields and owners here are fictional, and the demo does not write to any system.