Skip to content
Database ⇄ Marketing

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

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

Give your team Salesforce Marketing Cloud's contacts, campaigns, and engagement in OpenSearch: query them with SQL, push audiences built from your own data back to Salesforce Marketing Cloud, and skip the marketing API.

Salesforce Marketing Cloud holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in OpenSearch, hard to get into campaigns without manual exports.

Stacksync mirrors Content Assets (Content Builder), Automations (Automation Studio), Tracking Events, Transactional Sends from Salesforce Marketing Cloud into Indexes, Documents, Index aliases, Index templates in OpenSearch field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in OpenSearch, from usage, orders, or account status, sync back into Salesforce Marketing Cloud to drive campaigns and ads, with Salesforce Marketing Cloud kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Keep Postgres as the source of truth while mirroring rows to OpenSearch for full-text and vector queries.
  • 02 Index support tickets and activity logs from SaaS tools for operational dashboards.
  • 03 Stream Event Notification Service callbacks for transactional sends, bounces, opens, and clicks into a database in near real time alongside CRM contact records.
  • 04 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.

Common sync patterns

Query Salesforce Marketing Cloud like a database

Contacts, leads, audiences, and campaign metrics from Salesforce Marketing Cloud live in OpenSearch as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Build audiences from your own data

Segments computed in OpenSearch from product usage, orders, or account status sync into Salesforce Marketing Cloud as lists or audiences, so campaigns and ads target the people your data says they should.

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Salesforce Marketing Cloud land in OpenSearch beside the matching customer record, ready for reporting and revenue attribution.

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

OpenSearch objects Salesforce Marketing Cloud objects How this pairing syncs
Index aliases Stable names over rotating indexes, used for zero-downtime reindex during backfills 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. Index aliases is specific to OpenSearch and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Index templates Mapping and settings presets applied to new indexes a sync creates 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. Index templates is specific to OpenSearch and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Ingest pipelines Server-side processors that transform documents as they are written 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. Ingest pipelines is specific to OpenSearch and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Data streams Append-oriented time-series storage for logs and events pushed from source systems 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. Data streams is specific to OpenSearch and Automations (Automation Studio) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Snapshots Backup artifacts, relevant when reseeding an index from a repository 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. Snapshots is specific to OpenSearch and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Indexes The core container; synced records land in indexes with defined mappings 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). Indexes is specific to OpenSearch and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

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

OpenSearch Salesforce Marketing Cloud Interval-based propagation

DetectionStacksync polls OpenSearch for changes on an incremental schedule, reading only records changed since the previous pass. No native change feed.

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

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

Rate-limit considerations

  • OpenSearch: Throughput bounded by cluster sizing rather than fixed API quotas.
  • 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 OpenSearch ⇄ Salesforce Marketing Cloud

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the OpenSearch and Salesforce Marketing Cloud connectors work

OpenSearch

Integration surface
REST API over HTTP(S) with JSON payloads
Authentication
basic authentication with the security plugin, or AWS IAM request signing on Amazon OpenSearch Service
Change detection
no native change feed; reads rely on queries with scroll or point-in-time polling
Capabilities
read · write
Rate limits
throughput bounded by cluster sizing rather than fixed API quotas

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

    Choose tables

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

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

Popular · 7 of 384
All OpenSearch 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