Skip to content
Marketing ⇄ Accounting and finance

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

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

Put revenue reality behind every campaign: Zuora and Salesforce Marketing Cloud share the same customers, contacts, and billing status in real time, in both directions.

Zuora records the money — who pays, how much, and whether they are current; Salesforce Marketing Cloud decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.

Stacksync syncs Payment, Usage, Order and Amendment, Account (Billing Account) in Zuora with Transactional Sends, Data Extensions, Contacts / Subscribers, Journeys (Journey Builder) in Salesforce Marketing Cloud field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
  • 02 Two-way sync of Accounts and Subscriptions with an operational Postgres database so product and finance teams read billing state in SQL while changes flow back into Zuora.
  • 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

Where Salesforce Marketing Cloud captures new people: clean records flow to finance

Registrants, form fills, or leads created in Salesforce Marketing Cloud create or update the matching customer or contact in Zuora, so billing and reporting start from accurate details without re-entry.

Where Zuora tracks lifecycle state: keep Salesforce Marketing Cloud current

Trial, renewal, churn, or payment state from Zuora updates the contact in Salesforce Marketing Cloud, so lifecycle campaigns and audience suppression run on current billing reality.

Consent and contact details stay aligned

Email, phone, address, and opt-out flags kept in either system stay consistent in the other, so every send and record honors the latest preferences.

What you can sync between Salesforce Marketing Cloud and Zuora

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 Marketing Cloud objects Zuora objects How this pairing syncs
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). Rate Plan and Rate Plan Charge The priced components inside a Subscription; synced so charge amounts, quantities, and effective dates stay aligned with the source system. Transactional Sends is specific to Salesforce Marketing Cloud and Rate Plan and Rate Plan Charge to Zuora — each maps to any object or custom field on the other side.
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. Product and Product Rate Plan (Product Catalog) The catalog of sellable products and their pricing; usually mastered elsewhere and written into Zuora, or read to map subscription charges. Data Extensions is specific to Salesforce Marketing Cloud and Product and Product Rate Plan (Product Catalog) to Zuora — each maps to any object or custom field on the other side.
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. Invoice Billing documents generated from rate plan charges and order line items; typically read out into an ERP or GL for revenue recognition and reconciliation. Contacts / Subscribers is specific to Salesforce Marketing Cloud and Invoice to Zuora — each maps to any object or custom field on the other side.
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. Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. Journeys (Journey Builder) is specific to Salesforce Marketing Cloud and Payment to Zuora — each maps to any object or custom field on the other side.
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. Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. Content Assets (Content Builder) is specific to Salesforce Marketing Cloud and Usage to Zuora — each maps to any object or custom field on the other side.
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. Order and Amendment Records of subscription create and change actions; written to Zuora to drive quote-to-cash and read for subscription change history. Automations (Automation Studio) is specific to Salesforce Marketing Cloud and Order and Amendment to Zuora — each maps to any object or custom field on the other side.

How changes propagate between Salesforce Marketing Cloud and Zuora

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

Zuora Salesforce Marketing Cloud Sub-second propagation

DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.

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

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.
  • Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with Salesforce Marketing Cloud ⇄ Zuora

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Salesforce Marketing Cloud and Zuora connectors work

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.

Zuora

Integration surface
REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
Authentication
OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
Change detection
Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
Capabilities
read · write · webhooks
Rate limits
Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works

How to connect Salesforce Marketing Cloud to Zuora — 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 Marketing Cloud and Zuora 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 Marketing Cloud connected
    Zuora connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Salesforce Marketing Cloud and Zuora 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 Marketing Cloud ⇄ Zuora
    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 Marketing Cloud Zuora
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

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

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 461 integrations available for Salesforce Marketing Cloud and Zuora.

Popular · 8 of 461
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.