Zentrik + Gong

These work together but have different responsibilities:

• The Gong connection stores the workspace credentials and an optional account-matching policy shared by every Gong import.
• A saved import stores a named call boundary, optional Gong tracker, eligible products, title-routing phrases, exclusions, first-run lookback, schedule, cursor, and run history.

Manage saved imports in Settings → Integrations → Imports. Disconnecting Gong leaves their history intact but prevents another run until the connection is restored.

Account matching is optional. When enabled, Zentrik checks the company domains of Gong participants marked external against existing account domains and websites. Public email domains are ignored. Configured title patterns provide another deterministic match: the first capture group becomes the observed account name. Leave title patterns empty to use participant domains only. Ambiguous or unknown identities stay unlinked, and imports never create or guess accounts. Product-routing phrases belong to the saved import, not to this account policy.

Resolved accounts are linked to the imported signal and to the insights produced from it, so account filters and evidence trails stay consistent. Calls with participants from more than one unambiguous existing account can retain all of those links.

For calls that do not match an explicit title phrase, choose one fallback:

• Import and classify insights imports every unmatched call and uses the normal transcript analysis that creates Discovery insights.
• Check transcript before importing explicitly opts the saved import into an additional LLM relevance check. Clearly unrelated calls are skipped; relevant calls are constrained to the eligible products. If Gong has not made a transcript available yet, the call is retained so evidence is not silently lost.
• Do not import ignores unmatched calls without reading their transcripts.

The relevance check is off unless an admin chooses it. A recent-call preview shows which calls are immediately included, skipped, or waiting for that check.

You can also keep only calls where Gong found any selected tracker. Select multiple trackers when several conversation signals should qualify; a call is included when at least one selection matches. Zentrik applies this boundary after retrieving the call window because Gong's call-list API does not accept a tracker filter. Add tracker details to imported signals is a separate opt-in: leave it off to use the trackers only as an intake boundary, or turn it on to add every matching selected tracker's name, mention count, and matched phrases to the signal context used during analysis.

The tracker selector loads keyword trackers from Gong settings. Smart trackers are added when Gong reports them on calls in the saved-import preview window. A call matches only when Gong reports a positive tracker mention or phrase occurrence; zero-count tracker rows do not match. For a keyword tracker to match imported calls, enable API request results for that tracker in Gong.

Test draft is a read-only safety check. It evaluates the saved first-run window and deterministic routing without creating signals, running the optional transcript-relevance check, or moving the live cursor. Its durable receipt separates calls ready from saved rules from calls that need a transcript check during a live import.

1. In Gong, open the developer or API area your org uses to issue API keys.
2. Generate a key pair with permission to read calls and transcripts you need.
3. In Zentrik → Settings → Integrations → Gong, enter both values and save.
4. Test the connection or open a Gong import in Discovery.

Zentrik does not show either value again after save.

1. Start a Gong import from Discovery.
2. Search or filter to the conversation you need.
3. Review the transcript preview and speaker attribution.
4. Import the selected calls as Discovery signals.

The imported signal keeps the call and speaker context needed to trace later insights back to the conversation. Manual and saved imports can optionally filter the reviewed calls to those containing a selected Gong tracker. Adding that tracker's details to signal analysis is a separate choice. Saved imports can also apply deterministic title phrases, exclusions, and an optional transcript-relevance check before an unmatched call enters Discovery.

Audience boundaries

You can optionally require at least one confirmed external participant. External means outside your Gong workspace, not necessarily a customer. A partially resolved call passes when one external participant is confirmed; unknown affiliation is never treated as external.

The audience rule is applied together with the other saved-import rules. All calls keeps calls with unknown affiliation eligible, while the external-only boundary holds them out. In the Signals table, Audience selections include External participant present, Internal participants only, and Audience unknown. Multiple Audience selections are combined with OR; Audience is combined with other table filters using AND.

Zentrik does not infer customer identity from affiliation alone or apply percentage thresholds. When account matching is enabled, only an unambiguous existing-account match from an external participant's company domain or a configured title capture is authoritative.