Two-way sync
Changes in Intercom or Salesforce Marketing Cloud instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom and Salesforce Marketing Cloud in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Intercom owns the customer relationship and the pipeline; Salesforce Marketing Cloud 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 Companies, Conversations, Tickets, Data Events in Intercom with Data Extensions, Contacts / Subscribers, Journeys (Journey Builder), Content Assets (Content Builder) in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — Intercom can own account and opportunity status while Salesforce Marketing Cloud owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Where Salesforce Marketing Cloud builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Intercom, so who receives a campaign reflects current pipeline reality instead of a stale export.
New leads or responders captured in Salesforce Marketing Cloud flow into Intercom 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.
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.
| Intercom objects | Salesforce Marketing Cloud objects | How this pairing syncs | |
|---|---|---|---|
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Transactional Sends Triggered and transactional Email/SMS delivered through the Messaging API (/messaging/v1/email/messages/{key}); the Event Notification Service reports each message's disposition (delivered, bounced, opened, clicked). | Data Events is specific to Intercom and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Data Extensions Custom relational tables that store subscriber, audience, and arbitrary business data; rows are read via GET /data/v1/customobjectdata or SOAP Retrieve and upserted via the synchronous rowset PUT or the async /data/v1/async/dataextensions rows endpoint. This is the primary two-way surface. | Custom Data Attributes is specific to Intercom and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side. | |
| Tags Labels applied to contacts, companies, and conversations sync for routing and reporting. | Contacts / Subscribers The contact model keyed by Subscriber Key, holding channel addresses and subscription status; managed through the Contacts API (/contacts/v1/contacts) and the SOAP Subscriber object, and referenced by every send and journey. | Tags is specific to Intercom and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side. | |
| Segments Saved audience definitions are readable for targeting parity across tools. | Journeys (Journey Builder) Multi-step automated flows read and managed via /interaction/v1/interactions; contacts are injected by firing an entry event to /interaction/v1/events with an EventDefinitionKey and contact data. | Segments is specific to Intercom and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side. | |
| Admins & Teams Teammate records map conversation ownership to CRM users. | Content Assets (Content Builder) Emails, templates, images, and reusable content blocks stored in Content Builder and read or written via /asset/v1/content/assets, used to compose the messages a journey or send delivers. | Admins & Teams is specific to Intercom and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side. | |
| Articles Help center content is accessible via API for knowledge sync and audits. | Automations (Automation Studio) Scheduled or triggered workflows of import, query, extract, and send activities managed via /automation/v1/automations; SQL Query Activities read Data Views and write results into Data Extensions. | Articles is specific to Intercom and Automations (Automation Studio) to Salesforce Marketing Cloud — 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.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Salesforce Marketing Cloud through its API, with automatic retries and rate-limit backoff.
DetectionSalesforce Marketing Cloud notifies Stacksync of record changes through webhook events. The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback.
DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Salesforce Marketing Cloud connection.
Changes in Intercom or Salesforce Marketing Cloud instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Salesforce Marketing Cloud data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Salesforce Marketing Cloud record.
Track your Intercom ⇄ Salesforce Marketing Cloud sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Salesforce Marketing Cloud.
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 Intercom and Salesforce Marketing Cloud 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 Intercom and Salesforce Marketing Cloud 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 Intercom and Salesforce Marketing Cloud: authenticate both systems, choose the objects to sync (such as Intercom's Data Events and Custom Data Attributes), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Salesforce Marketing Cloud connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Salesforce Marketing Cloud integration in-house.
Yes — Stacksync ships production-grade connectors for both Intercom and Salesforce Marketing Cloud. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Intercom: Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill. On Salesforce Marketing Cloud: The Event Notification Service (ENS) issues HTTPS POST callbacks for transactional Email and SMS events (sent, bounce, open, click) once a callback URL and subscription are registered and verified. There is no general data-change feed, so Data Extension and Data View syncs poll by date fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Intercom side: Companies, Conversations, Tickets, Data Events, plus custom fields where Intercom exposes them. On the Salesforce Marketing Cloud side: Data Extensions, Contacts / Subscribers, Journeys (Journey Builder), Content Assets (Content Builder). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 473 integrations available for Intercom and Salesforce Marketing Cloud.