Skip to content
CRM ⇄ Marketing

Salesforce to Salesforce Marketing Cloud integration — real-time, two-way sync

Keep Salesforce 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.

  • 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 Salesforce and Salesforce Marketing Cloud

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

Salesforce 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 Opportunities, Cases, Campaigns, Tasks and Events in Salesforce with Journeys (Journey Builder), Content Assets (Content Builder), Automations (Automation Studio), Tracking Events in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — Salesforce 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.

Common use cases

  • 01 Write product usage metrics computed in a warehouse onto Account and Contact fields so reps see adoption signals on the record.
  • 02 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 03 Two-way sync Data Extension rows between Marketing Cloud and a Postgres database or warehouse so audience attributes and opt-out state stay aligned in both systems.
  • 04 Push CRM or warehouse audience segments into Data Extensions via the async rows API (background bulk insert) so marketing sends to freshly built audiences without manual CSV imports.

Common sync patterns

New and updated people stay in step

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.

Where Salesforce Marketing Cloud captures engagement: activity lands on the record

Opens, clicks, form fills, event attendance, or ad responses recorded in Salesforce Marketing Cloud post back to the contact or account in Salesforce, 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.

What you can sync between Salesforce and Salesforce Marketing Cloud

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.

Salesforce objects Salesforce Marketing Cloud objects How this pairing syncs
Cases Support records; synced with help desk tools or internal databases for escalation workflows. 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. Cases is specific to Salesforce and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Campaigns Marketing membership data; read out for attribution analysis in the warehouse. 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. Campaigns is specific to Salesforce and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. 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. Tasks and Events is specific to Salesforce and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. 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. Products and Price Books is specific to Salesforce and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. 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. Custom Objects is specific to Salesforce and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. Tracking Events Sent, Open, Click, Bounce, Unsubscribe, and NotSent events retrieved through the SOAP tracking objects (SentEvent, OpenEvent, ClickEvent, BounceEvent) or the Automation Studio Data Views (_Sent, _Open, _Click, _Bounce) - the queryable record of engagement per send. Accounts is specific to Salesforce and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between Salesforce and Salesforce Marketing Cloud

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.

Salesforce Salesforce Marketing Cloud Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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

Salesforce Marketing Cloud Salesforce Sub-second propagation

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 Salesforce through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Salesforce: Daily API request allocations vary by edition and license count.
  • Salesforce Marketing Cloud: Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
What ships with Salesforce ⇄ Salesforce Marketing Cloud

Connect Salesforce and Salesforce Marketing Cloud for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Salesforce Marketing Cloud connection.

Real-time

Two-way sync

Changes in Salesforce or Salesforce Marketing Cloud instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Salesforce or Salesforce Marketing Cloud 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 Salesforce or Salesforce Marketing Cloud record.

Observability

Monitoring

Track your Salesforce ⇄ Salesforce Marketing Cloud sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Salesforce and Salesforce Marketing Cloud.

How the Salesforce and Salesforce Marketing Cloud connectors work

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide

Salesforce Marketing Cloud

Integration surface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
OAuth 2.0 via an Installed Package (Client ID + Client Secret). Server-to-server uses the client_credentials grant and web apps use authorization_code, both against {subdomain}.auth.marketingcloudapis.com/v2/token. The 20-minute access token response also returns the account's rest_instance_url and soap_instance_url.
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
Salesforce does not publish fixed numeric REST rate limits; requests are throttled per account and can return HTTP 429, so backoff is advised. SOAP Retrieve returns at most 2,500 records per call and pages via ContinueRequest with the prior RequestID. Bulk Data Extension writes use the async rows API to queue inserts in the background.
How it works

How to connect Salesforce to Salesforce Marketing Cloud — 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 Salesforce 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Salesforce connected
    Salesforce Marketing Cloud connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Salesforce ⇄ Salesforce Marketing Cloud
    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
    Salesforce Salesforce Marketing Cloud
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Salesforce and Salesforce Marketing Cloud 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 497 integrations available for Salesforce and Salesforce Marketing Cloud.

Popular · 8 of 497
All Salesforce integrations All Salesforce Marketing Cloud 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