Skip to content
Data warehouse ⇄ Marketing

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

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

Put modeled data to work and measure what it drives: ClickHouse and Salesforce Marketing Cloud keep contacts, audiences, and campaign results in step in real time, in both directions.

ClickHouse is where your team models customers, product usage, and revenue into trusted tables; Salesforce Marketing Cloud runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Stacksync syncs Tables (MergeTree family), Databases, Views, Materialized views in ClickHouse with Tracking Events, Transactional Sends, Data Extensions, Contacts / Subscribers in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Salesforce Marketing Cloud while sends, opens, and conversions flow back to ClickHouse — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 02 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 03 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.
  • 04 Fire Journey Builder entry events (/interaction/v1/events) from an app or database when a contact acts, so behavioral journeys trigger on live events instead of scheduled batch loads.

Common sync patterns

Keep the contact and audience list current

New and updated contacts, leads, or audience members flow between ClickHouse and Salesforce Marketing Cloud, so the marketing audience reflects the people in your warehouse and corrections propagate instead of the two sides drifting apart.

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and ClickHouse holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in ClickHouse appear on the matching record in Salesforce Marketing Cloud, so targeting, routing, and personalization use up-to-date context.

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

ClickHouse objects Salesforce Marketing Cloud objects How this pairing syncs
Distributed tables Query-routing tables over cluster shards in self-managed deployments. 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. Distributed tables is specific to ClickHouse and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. 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. Dictionaries is specific to ClickHouse and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. 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. Tables (MergeTree family) is specific to ClickHouse and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. 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). Databases is specific to ClickHouse and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. 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. Views is specific to ClickHouse and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. 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. Materialized views is specific to ClickHouse and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

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

ClickHouse Salesforce Marketing Cloud Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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

Salesforce Marketing Cloud ClickHouse 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 applied to ClickHouse as a row-level write, with types converted between the two schemas.

Rate-limit considerations

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

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the ClickHouse and Salesforce Marketing Cloud connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

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

    Choose tables

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

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

Popular · 8 of 500
All ClickHouse 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