Two-way sync
Changes in Gong or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Gong and Iterable in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Gong owns the customer relationship and the pipeline; Iterable 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 CRM Objects, Library, Data Privacy (Erasure), Calls in Gong with Lists, Catalogs, Commerce / Purchases, Export data in Iterable 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 Iterable owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
New leads or responders captured in Iterable flow into Gong assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.
Opens, clicks, form fills, event attendance, or ad responses recorded in Iterable post back to the contact or account in Gong, so reps see interest before they reach out.
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.
| Gong objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Library Call-library folders and folder content (curated calls and snippets) read via GET /v2/library/folders and /v2/library/folder-content. Read-only. | Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. | Library is specific to Gong and Templates to Iterable — each maps to any object or custom field on the other side. | |
| 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. | Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. | Data Privacy (Erasure) is specific to Gong and Lists to Iterable — each maps to any object or custom field on the other side. | |
| 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. | Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | Calls is specific to Gong and Catalogs to Iterable — each maps to any object or custom field on the other side. | |
| Transcripts Speaker-attributed, timestamped sentences retrieved via POST /v2/calls/transcript for one or more callIds; available only after asynchronous processing completes. Read-only. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Transcripts is specific to Gong and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| 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. | Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. | Interaction Stats (Activity) is specific to Gong and Export data to Iterable — each maps to any object or custom field on the other side. |
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.
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 Iterable through its API, with automatic retries and rate-limit backoff.
DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.
DeliveryEach detected change is written to Gong through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Gong–Iterable connection.
Changes in Gong or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Gong or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Gong or Iterable record.
Track your Gong ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Gong and Iterable.
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.
Authenticate Gong and Iterable with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Gong and Iterable 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Gong and Iterable: authenticate both systems, choose the objects to sync (such as Gong's Users and Library), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Gong and Iterable: Where Iterable generates leads: hand-off without re-keying; New and updated people stay in step; Where Iterable captures engagement: activity lands on the record. New leads or responders captured in Iterable flow into Gong assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
Gong: 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. Iterable: Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data. Authentication: API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com. Stacksync manages authentication, retries, and rate limits on both sides.
Gong: Authentication uses a Basic authorization header built from an Access Key and Access Key Secret generated by a Gong technical admin, or OAuth 2.0 Bearer tokens for marketplace apps. Iterable: Rate limits are per endpoint and return HTTP 429 when exceeded; since November 10, 2025, providing the API key in the query string or request body is throttled more strictly than the Api-Key header. Stacksync's field mapping accounts for these differences between Gong and Iterable without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Gong and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Gong and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Gong–Iterable integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 489 integrations available for Gong and Iterable.