Skip to content
Marketing ⇄ ERP

Eloqua to SAP integration — real-time, two-way sync

Keep Eloqua and SAP 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 Eloqua and SAP

Feed the real customer, order, and revenue records from SAP into Eloqua so campaigns run on who actually bought what, and let contact and consent changes flow back in real time.

Marketing runs on lists of people, but the list rarely knows which of those people are paying customers, what they ordered, or what they are worth. SAP holds exactly that: Cost Centers, Business Partners, Materials (Products), Sales Orders that record who the customer is, what they bought, and what they owe. When the two are joined only by a periodic export, campaigns go out against stale audiences, existing customers get prospecting emails, high-value accounts look the same as cold leads, and a canceled order still counts toward a segment.

Stacksync syncs Cost Centers, Business Partners, Materials (Products), Sales Orders in SAP with Activities, Campaigns, Emails, Forms and Form Submits in Eloqua in real time, and where both sides accept writes, in both directions. Customer, order, and invoice data maps field by field onto the contacts, audiences, or accounts Eloqua works with, so segmentation and personalization run on current purchase history instead of a month-old snapshot. Contact details and consent changes that originate in Eloqua flow back onto the record in SAP.

The strongest bridge between the two is identity and purchase history, who the customer is and what they have bought, so that is where most of the value sits. Because the sync is field-level, each system keeps the attributes the other has no use for; only the shared records are held in agreement.

Common use cases

  • 01 Replicate journal entries and billing documents to a warehouse for finance analytics without loading the ERP.
  • 02 Keep MES and WMS systems aligned with production orders and goods movements.
  • 03 Add or remove Contacts from shared Contact Lists and Segments based on lifecycle stage computed downstream in a database.
  • 04 Two-way sync Contacts between Eloqua and a Postgres or warehouse table, matched on email, so ops teams query and update marketing profiles in SQL while marketers keep working in Eloqua.

Common sync patterns

Lifecycle triggers from back-office events

A first order, a renewal, or a lapsed account recorded in SAP appears in Eloqua within seconds, ready to start or stop a lifecycle campaign.

Where Eloqua captures new people: signups become customer records

Registrations, form fills, or new subscribers in Eloqua create or update the corresponding record in SAP, so the back office sees them without anyone re-keying.

Consent and contact changes travel

Email, address, or subscription-status changes stay aligned across both systems, so a customer who updates their details or opts out is respected everywhere.

What you can sync between Eloqua and SAP

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.

Eloqua objects SAP objects How this pairing syncs
Custom Data Objects Auxiliary data tables (CDOs) linked to Contacts for records like event registrations or purchases; synced via the Bulk API so nurture campaigns can branch on them. Billing Documents Invoices read for AR status and replicated for revenue reporting. Custom Data Objects is specific to Eloqua and Billing Documents to SAP — each maps to any object or custom field on the other side.
Activities Engagement events (email opens, clicks, form submits, bounces, page views, subscribes/unsubscribes) exported through the Bulk API activities export; read-only feed for scoring and attribution. GL Accounts and Journal Entries Financial postings replicated to warehouses for group finance analytics. Activities is specific to Eloqua and GL Accounts and Journal Entries to SAP — each maps to any object or custom field on the other side.
Campaigns Multi-step campaign-canvas assets managed through the Application REST API; campaign membership and response data read out for attribution reporting. Production Orders Manufacturing orders exchanged with MES and scheduling systems. Campaigns is specific to Eloqua and Production Orders to SAP — each maps to any object or custom field on the other side.
Emails Email creative and email-group assets managed via the Application REST API; usually read for reporting rather than written by a sync. Inventory / Stock Plant and storage-location quantities synced to storefronts and planning tools. Emails is specific to Eloqua and Inventory / Stock to SAP — each maps to any object or custom field on the other side.
Forms and Form Submits Form definitions and their submission data, accessed through the Application REST API; submissions read out into a warehouse for lead capture and analysis. Cost Centers Controlling masters read for mapping costs in finance integrations. Forms and Form Submits is specific to Eloqua and Cost Centers to SAP — each maps to any object or custom field on the other side.
Contact Lists and Segments Shared lists (static) and segments (dynamic audiences); Contacts are added to or removed from shared lists based on lifecycle stage computed downstream. Business Partners The unified customer and supplier master in S/4HANA, the anchor object for CRM and procurement syncs. Contact Lists and Segments is specific to Eloqua and Business Partners to SAP — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and SAP

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.

Eloqua SAP Interval-based propagation

DetectionStacksync polls Eloqua for changes on an incremental schedule, reading only records changed since the previous pass. Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax.

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

SAP Eloqua Sub-second propagation

DetectionSAP notifies Stacksync of record changes through webhook events. Business events via SAP Event Mesh on S/4HANA.

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

Rate-limit considerations

  • Eloqua: Per-instance soft limits by sync type (Export 2,000/hr, Import 2,000/hr, Sync Action 4,000/hr); 32 MB cap per POST to a staging area and 50,000 records per retrieve batch.
  • SAP: Throttling is configured at the gateway and tenant level rather than as a single published rate limit.
What ships with Eloqua ⇄ SAP

Connect Eloqua and SAP for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Eloqua–SAP connection.

Real-time

Two-way sync

Changes in Eloqua or SAP instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Eloqua or SAP 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 Eloqua or SAP record.

Observability

Monitoring

Track your Eloqua ⇄ SAP sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Eloqua and SAP.

How the Eloqua and SAP connectors work

Eloqua

Integration surface
Bulk API 2.0 (contacts, accounts, custom data objects, activities) plus Application REST API (campaigns, emails, forms, lists)
Authentication
OAuth 2.0 (Authorization Code or Resource Owner Password Credentials grant; Client Credentials not supported) or HTTP Basic Auth with siteName + username + password; the instance base URL must first be discovered via the login.eloqua.com/id endpoint
Change detection
Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax; no general-purpose record-change webhook
Capabilities
read · write
Rate limits
Per-instance soft limits by sync type (Export 2,000/hr, Import 2,000/hr, Sync Action 4,000/hr); 32 MB cap per POST to a staging area and 50,000 records per retrieve batch

SAP

Integration surface
OData (v2/v4) APIs on S/4HANA; BAPI/RFC and IDoc on ECC and on-prem systems; SOAP services
Authentication
OAuth 2.0 or basic auth via communication arrangements on cloud editions; SAP user credentials for RFC on-prem
Change detection
Business events via SAP Event Mesh on S/4HANA; change pointers with IDocs or timestamp polling on ECC
Capabilities
read · write · webhooks
Rate limits
Throttling is configured at the gateway and tenant level rather than as a single published rate limit
How it works

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

    Choose tables

    Pick the Eloqua and SAP 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 · Eloqua ⇄ SAP
    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
    Eloqua SAP
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Eloqua and SAP 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 490 integrations available for Eloqua and SAP.

Popular · 8 of 490
All Eloqua integrations All SAP 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