Skip to content
CRM ⇄ Marketing

Crustdata to Salesforce Marketing Cloud integration — real-time data sync

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

Flow Crustdata data into Salesforce Marketing Cloud in real time — no exports, no schedulers, no custom scripts.

Crustdata is a read-only source: Stacksync reads its data in real time and delivers it into Salesforce Marketing Cloud, so Salesforce Marketing Cloud always reflects the current state of Crustdata — without exports, scripts, or schedulers.

Crustdata 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.

Common use cases

  • 01 Append enrichment at lead-capture time so new records arrive scored and routable.
  • 02 Enrich CRM accounts with firmographics, headcount growth, and tech stack so scoring and routing run on complete data.
  • 03 Land tracking events - Sent, Open, Click, Bounce, Unsubscribe - from the SOAP tracking objects or Automation Studio Data Views into a warehouse table for per-send deliverability reporting.
  • 04 Sync Contacts and Subscriber Key subscription status between Marketing Cloud and a CRM so suppression and opt-in state stay current before the next send.

Common sync patterns

Segments and audiences follow the CRM

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

Where Salesforce Marketing Cloud generates leads: hand-off without re-keying

New leads or responders captured in Salesforce Marketing Cloud flow into Crustdata assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.

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.

What you can sync between Crustdata 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.

Crustdata objects Salesforce Marketing Cloud objects How this pairing syncs
Enrichment Responses Real-time enrichment lookups keyed by domain or profile URL; read to append fresh firmographic and contact data at form-fill or record-creation time. 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). Enrichment Responses is specific to Crustdata and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Companies Firmographic records — industry, size, funding, growth signals; read out to enrich CRM accounts and warehouse company tables. 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. Companies is specific to Crustdata and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
People Contact and profile data for decision-makers; read into a CRM or outreach tool to fill missing titles, emails, and LinkedIn profiles. 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. People is specific to Crustdata and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Headcount and Growth Metrics Time-series employee counts by department and region; read to score accounts on hiring momentum and expansion signals. 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. Headcount and Growth Metrics is specific to Crustdata and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Tech Stack Detected technologies per company; read to build segments and route accounts by the tools they already use. 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. Tech Stack is specific to Crustdata and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Screener Results Saved company searches with filter criteria; read on a schedule so target-account lists in the CRM refresh as companies enter the criteria. 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. Screener Results is specific to Crustdata and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

How changes propagate between Crustdata 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.

Crustdata Salesforce Marketing Cloud Interval-based propagation

DetectionStacksync polls Crustdata for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets.

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

Salesforce Marketing Cloud Crustdata 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.

DeliveryCrustdata does not accept inbound record writes, so this direction carries requests rather than records: Crustdata's output flows back as field updates on the originating Salesforce Marketing Cloud records.

Rate-limit considerations

  • Crustdata: Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.
  • 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 Crustdata ⇄ Salesforce Marketing Cloud

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

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

Real-time

Real-time sync

Changes in Crustdata 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 Crustdata 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 Crustdata or Salesforce Marketing Cloud record.

Observability

Monitoring

Track your Crustdata ⇄ 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 Crustdata and Salesforce Marketing Cloud.

How the Crustdata and Salesforce Marketing Cloud connectors work

Crustdata

Integration surface
REST API (JSON)
Authentication
API token — Authorization: Token header issued per workspace
Change detection
Pull-based: real-time enrichment endpoints for on-demand lookups plus periodic re-pulls of screeners and datasets; no webhooks or change feed
Capabilities
read
Rate limits
Requests are metered by plan credits and per-minute rate limits; bulk dataset pulls are the efficient path for large refreshes rather than per-record enrichment calls.

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 Crustdata 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 Crustdata 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
    Crustdata connected
    Salesforce Marketing Cloud connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Crustdata 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 · Crustdata ⇄ 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
    Crustdata Salesforce Marketing Cloud
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

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

Popular · 8 of 264
All Crustdata 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