Skip to content
Marketing ⇄ ERP

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

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

Feed the real customer, order, and revenue records from SAP Business ByDesign 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 Business ByDesign holds exactly that: Contacts, Sales Orders, Customer Invoices, Materials / Products 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 Contacts, Sales Orders, Customer Invoices, Materials / Products in SAP Business ByDesign 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 Business ByDesign.

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 Sync ByDesign accounts and contacts with an external CRM so sales works outside the ERP while finance keeps the master record.
  • 02 Create sales orders in ByDesign from e-commerce or CPQ systems and sync order and delivery status back.
  • 03 Load purchase or product-usage records into Custom Data Objects linked to Contacts so nurture campaigns branch on behavior mastered in another system.
  • 04 Add or remove Contacts from shared Contact Lists and Segments based on lifecycle stage computed downstream in a database.

Common sync patterns

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.

Purchase history drives segmentation

Orders, invoices, and revenue totals from SAP Business ByDesign land on the matching contact or account in Eloqua, so audiences are built from what customers actually bought and spent rather than from guesses.

Suppress or target existing customers

Because SAP Business ByDesign knows who is already a paying customer, Eloqua can exclude them from acquisition campaigns or single them out for renewal and cross-sell.

What you can sync between Eloqua and SAP Business ByDesign

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 Business ByDesign objects How this pairing syncs
Contacts Core person records, keyed on email address as the unique identifier; imported/exported via the Bulk API and upserted on email, synced two-way with CRM, warehouse, and app databases. Contacts Person records linked to accounts, aligned with CRM contact objects. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
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. Opportunities Built-in CRM records synced with external sales tools when both are in use. Activities is specific to Eloqua and Opportunities to SAP Business ByDesign — 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. Projects Project structures and tasks read for time and billing integrations. Campaigns is specific to Eloqua and Projects to SAP Business ByDesign — 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. Employees Worker records referenced by time, expense, and project data. Emails is specific to Eloqua and Employees to SAP Business ByDesign — 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. Business Partners (Accounts) Customer and supplier master data synced with CRMs and procurement tools. Forms and Form Submits is specific to Eloqua and Business Partners (Accounts) to SAP Business ByDesign — 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. Sales Orders Order documents created from external channels and read for status. Contact Lists and Segments is specific to Eloqua and Sales Orders to SAP Business ByDesign — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and SAP Business ByDesign

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

SAP Business ByDesign Eloqua Interval-based propagation

DetectionStacksync polls SAP Business ByDesign for changes on an incremental schedule, reading only records changed since the previous pass. Polling on last-changed timestamps.

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.
What ships with Eloqua ⇄ SAP Business ByDesign

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Eloqua ⇄ SAP Business ByDesign 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 Business ByDesign.

How the Eloqua and SAP Business ByDesign 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 Business ByDesign

Integration surface
SOAP web services plus OData services for analytical and custom data access
Authentication
Basic authentication over TLS for service users; OAuth-based options exist for certain scenarios
Change detection
Polling on last-changed timestamps; the platform does not offer a general webhook surface
Capabilities
read · write
How it works

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

    Choose tables

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

Eloqua and SAP Business ByDesign 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 476 integrations available for Eloqua and SAP Business ByDesign.

Popular · 7 of 476
All Eloqua integrations All SAP Business ByDesign 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