Skip to content
Marketing ⇄ CRM

Demandbase to Gong integration — real-time, two-way sync

Keep Demandbase and Gong in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Demandbase and Gong

Keep the people you sell to and the people you market to in one shared view: Gong and Demandbase sync contacts, accounts, and engagement in real time, in both directions.

Gong owns the customer relationship and the pipeline; Demandbase runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.

Stacksync syncs Transcripts, Users, Interaction Stats (Activity), Trackers & Scorecards in Gong with Campaigns, Account & Person Lists (Audiences), Company Details (B2B enrichment), Change Subscriptions in Demandbase field by field, in real time, and in both directions. You decide which system owns which fields — Gong can own account and opportunity status while Demandbase owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Upload warehouse- or CRM-derived Accounts, Opportunities, and stages into Gong through the CRM integration API so deal context shows alongside conversations.
  • 02 Submit data-privacy erase-data-for-email requests to Gong to fulfill GDPR/CCPA deletion across recorded conversations.
  • 03 Push warehouse-computed account scores, custom fields, and audiences into Demandbase via the Data Import API so ABM campaigns and sales plays target the segments the warehouse defines.
  • 04 Enrich CRM Company and Contact records with Demandbase firmographics, technographics, and verified business emails through the B2B Company and Contact Details endpoints.

Common sync patterns

Where Demandbase captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Demandbase post back to the contact or account in Gong, so reps see interest before they reach out.

Lead and lifecycle status agree

Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.

Segments and audiences follow the CRM

Where Demandbase builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Gong, so who receives a campaign reflects current pipeline reality instead of a stale export.

What you can sync between Demandbase and Gong

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Demandbase objects Gong objects How this pairing syncs
Change Subscriptions Company firmographic, company news, family-tree (ownership), and DB person employment subscriptions delivered as webhook alerts with a signing secret; the real-time change feed. Data Privacy (Erasure) GDPR/CCPA deletion handled by POST /v2/data-privacy/erase-data-for-email, with data-for-email lookups on the read side; a write path used for compliance deletions. Change Subscriptions is specific to Demandbase and Data Privacy (Erasure) to Gong — each maps to any object or custom field on the other side.
Accounts Company/account records with firmographics, intent, and Demandbase qualification and engagement scores; exported via the Data Export API and imported or updated via the Data Import API. Calls Retrieved via POST /v2/calls/extensive with participants, topics, trackers, scorecards, and media URLs, filtered by fromDateTime/toDateTime; external recordings are also imported via POST /v2/calls with media uploaded via PUT /v2/calls/{id}/media. Read and write. Accounts is specific to Demandbase and Calls to Gong — each maps to any object or custom field on the other side.
Opportunities Opportunity records synced from the CRM into Demandbase; exported with calculated insights and imported or updated through the Data Import API. Read and write. Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. Opportunities is specific to Demandbase and Transcripts to Gong — each maps to any object or custom field on the other side.
People (Persons) Contact/person records with verified business email, title, seniority, and quality grades; fetched and matched via the B2B Contact endpoints and exported or imported. Users Gong users and team members with roles, titles, email, and settings, read via GET /v2/users to map call owners and participants to CRM and warehouse identities. Read-only. People (Persons) is specific to Demandbase and Users to Gong — each maps to any object or custom field on the other side.
Activities Engagement and custom activity records (web, campaign, intent); exported via Data Export and pushed in through the Data Import API using custom activity types. Interaction Stats (Activity) Aggregated talk/listen ratios, interaction stats, and day-by-day user activity retrieved via POST /v2/stats endpoints; read out for coaching and engagement reporting. Read-only. Activities is specific to Demandbase and Interaction Stats (Activity) to Gong — each maps to any object or custom field on the other side.
Campaigns Marketing campaign records and creative assets exported through the Data Export API; read-only reporting feed. Trackers & Scorecards Keyword and topic tracker definitions plus coaching scorecards, including answered scorecards, read from Settings as coaching and deal-risk signals. Read-only. Campaigns is specific to Demandbase and Trackers & Scorecards to Gong — each maps to any object or custom field on the other side.

How changes propagate between Demandbase and Gong

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Demandbase Gong Sub-second propagation

DetectionDemandbase notifies Stacksync of record changes through webhook events. Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL.

DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.

Gong Demandbase Interval-based propagation

DetectionStacksync polls Gong for changes on an incremental schedule, reading only records changed since the previous pass. Polling POST /v2/calls/extensive on fromDateTime/toDateTime.

DeliveryEach detected change is written to Demandbase through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Demandbase: Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.
  • Gong: 3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
What ships with Demandbase ⇄ Gong

Connect Demandbase and Gong for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Demandbase–Gong connection.

Real-time

Two-way sync

Changes in Demandbase or Gong instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Demandbase or Gong data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Demandbase or Gong record.

Observability

Monitoring

Track your Demandbase ⇄ Gong sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Demandbase and Gong.

How the Demandbase and Gong connectors work

Demandbase

Integration surface
REST APIs (Demandbase One) - a B2B API (company/contact search, details, and match with async bulk enrichment jobs), a read-only Data Export API and a write-capable Data Import API (both async bulk jobs), and a Subscription API for webhook change alerts.
Authentication
JWT bearer tokens minted from Demandbase One API Key Sets at the platform level; each credential set expires after 8 hours and is rotated. Legacy single-user API tokens are deprecated.
Change detection
Subscription API webhooks - company firmographic, company news, family-tree (ownership), and person employment-change alerts to a configurable URL secured with a signing secret; bulk reads run as async export jobs (submit, poll, download). No log-based CDC.
Capabilities
read · write · webhooks
Rate limits
Credit-based per API call; bulk jobs accept up to 10,000 records per submission, CSV uploads up to 5GB, and result URLs stay valid 24 hours; subscription alerts page up to 5,000 entities and list endpoints up to 100 per page.

Gong

Integration surface
REST API on api.gong.io/v2 - retrieval endpoints (calls, transcript, users, stats, settings, library, logs) plus write endpoints for importing calls, uploading CRM data, and data-privacy erasure
Authentication
Basic authorization header combining an Access Key and Access Key Secret (created by a Gong technical admin, base64-encoded as key:secret); OAuth 2.0 Bearer tokens are supported for marketplace apps
Change detection
Polling POST /v2/calls/extensive on fromDateTime/toDateTime; the public API exposes no outbound webhooks or CDC, though a Gong admin can configure a product-side automation Rule that POSTs matching calls to a URL. Transcripts and analysis appear only after asynchronous processing.
Capabilities
read · write
Rate limits
3 API calls per second and 10,000 calls per day per company by default; exceeding returns HTTP 429 with a Retry-After header, and limits can be raised by contacting Gong.
Gong setup guide
How it works

How to connect Demandbase to Gong — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Demandbase and Gong with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Demandbase connected
    Gong connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Demandbase and Gong objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Demandbase ⇄ Gong
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Demandbase Gong
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Demandbase and Gong integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 489 integrations available for Demandbase and Gong.

Popular · 8 of 489
All Demandbase integrations All Gong integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own