Skip to content
Accounting and finance ⇄ Marketing

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

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

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

Coupa 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 Users, Accounts, Contracts, Expense Reports in Coupa 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 — 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 Provision and update Users in Coupa from an HRIS or identity provider as employees join, change roles, or leave.
  • 02 Mirror Purchase Orders and their status into an operational Postgres database for spend reporting and three-way match analytics.
  • 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

One customer and contact list

Where both systems keep customer or contact records, an edit on either side propagates to the other, ending dual maintenance and the drift it creates.

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 Coupa, so billing and reporting start from accurate details without re-entry.

Where Coupa tracks lifecycle state: keep Salesforce Marketing Cloud current

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

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

Coupa objects Salesforce Marketing Cloud objects How this pairing syncs
Accounts Chart-of-accounts segments and GL codes; usually mastered in the ERP and written into Coupa so requisitions and invoices code correctly. 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 Coupa and Tracking Events to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Contracts Supplier contract records with terms and dates; read out for reporting or created from a CLM system. 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). Contracts is specific to Coupa and Transactional Sends to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Expense Reports Employee expense reports and their lines; exported to AP or ERP for reimbursement and GL posting. 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. Expense Reports is specific to Coupa and Data Extensions to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Requisitions Employee purchase requests with lines and approval chains; read out to warehouses, or created via the API from upstream intake tools. 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. Requisitions is specific to Coupa and Contacts / Subscribers to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Purchase Orders PO headers and lines; synced two-way with ERPs so orders raised in Coupa flow to the ledger and status updates flow back on the /purchase_orders resource. 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. Purchase Orders is specific to Coupa and Journeys (Journey Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.
Invoices Supplier/AP invoices with lines and approval status; polled out to accounting and ERP systems for the pay cycle, or created through the API. 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. Invoices is specific to Coupa and Content Assets (Content Builder) to Salesforce Marketing Cloud — each maps to any object or custom field on the other side.

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

Coupa Salesforce Marketing Cloud Interval-based propagation

DetectionStacksync polls Coupa for changes on an incremental schedule, reading only records changed since the previous pass. Polling on updated-at and created-at filters (e.g.

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

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

Rate-limit considerations

  • Coupa: Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.
  • 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 Coupa ⇄ Salesforce Marketing Cloud

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

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

Real-time

Two-way sync

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

Observability

Monitoring

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

How the Coupa and Salesforce Marketing Cloud connectors work

Coupa

Integration surface
REST Core API (JSON or XML)
Authentication
OAuth 2.0 / OIDC via the client-credentials grant; scopes take the service.object.right form (e.g. core.accounting.read, core.accounting.write). Legacy API keys are being retired (no new keys since R34; API-key auth unsupported from R36). Access tokens last 24 hours.
Change detection
Polling on updated-at and created-at filters (e.g. updated-at[gt]=<timestamp>); Coupa has no native webhook subscriptions, though admins can configure outbound Call Out / external notifications.
Capabilities
read · write
Rate limits
Coupa does not publish explicit rate limits or expose X-RateLimit/Retry-After headers; integrations page 50 records at a time and back off on 429/503 responses.

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

    Choose tables

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

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

Popular · 8 of 461
All Coupa 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