Real-time
Two-way sync
Changes in Eloqua or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Marketing ⇄ CRM
Eloqua to Kustomer integration — real-time, two-way sync
Keep Eloqua and Kustomer 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 Kustomer
Keep the people you sell to and the people you market to in one shared view: Kustomer and Eloqua sync contacts, accounts, and engagement in real time, in both directions.
Kustomer owns the customer relationship and the pipeline; Eloqua runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.
Stacksync syncs Notes, Customers, Conversations, Messages in Kustomer with Custom Data Objects, Activities, Campaigns, Emails in Eloqua field by field, in real time, and in both directions. You decide which system owns which fields — Kustomer can own account and opportunity status while Eloqua owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 02 Push order and shipment records from commerce systems into Kustomer custom objects so agents answer order-status questions without switching tools
- 03 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.
- 04 Export email opens, clicks, form submits, and bounces from the Bulk API Activities export into a warehouse for lead scoring and multi-touch attribution.
Common sync patterns
Segments and audiences follow the CRM
Where Eloqua builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Kustomer, so who receives a campaign reflects current pipeline reality instead of a stale export.
Where Eloqua generates leads: hand-off without re-keying
New leads or responders captured in Eloqua flow into Kustomer assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
New and updated people stay in step
When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.
What you can sync between Eloqua and Kustomer
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 | Kustomer 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. | Tags Labels on conversations and customers sync for categorization and analytics. | Contacts is specific to Eloqua and Tags to Kustomer — each maps to any object or custom field on the other side. | |
| Accounts Company records linked to Contacts via the account-linkage field; moved through the Bulk API and typically mastered in a CRM or ERP and written into Eloqua. | Notes Internal annotations carry context alongside synced conversations. | Accounts is specific to Eloqua and Notes to Kustomer — each maps to any object or custom field on the other side. | |
| 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. | Customers The central record whose timeline aggregates every interaction; external attributes sync onto it. | Custom Data Objects is specific to Eloqua and Customers to Kustomer — 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. | Conversations Support threads across channels sync outward for analytics and CRM context. | Activities is specific to Eloqua and Conversations to Kustomer — 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. | Messages Individual messages within conversations support full-thread replication. | Campaigns is specific to Eloqua and Messages to Kustomer — 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. | Companies Organization records group customers and map to CRM accounts. | Emails is specific to Eloqua and Companies to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Eloqua and Kustomer
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 Kustomer 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 Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Eloqua Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Eloqua ⇄ Kustomer
Connect Eloqua and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Eloqua–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Eloqua or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Eloqua ⇄ Kustomer 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 Kustomer.
How the Eloqua and Kustomer 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
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Eloqua to Kustomer — 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.
- 01
Connect your apps
Authenticate Eloqua and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Eloqua
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Eloqua and Kustomer 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.
objects · Eloqua ⇄ KustomerCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Eloqua KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Eloqua and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Eloqua and Kustomer: authenticate both systems, choose the objects to sync (such as Eloqua's Contacts and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Eloqua: Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax; no general-purpose record-change webhook. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kustomer side: Notes, Customers, Conversations, Messages, plus custom fields where Kustomer exposes them. On the Eloqua side: Custom Data Objects, Activities, Campaigns, Emails. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Eloqua and Kustomer: Segments and audiences follow the CRM; Where Eloqua generates leads: hand-off without re-keying; New and updated people stay in step. Where Eloqua builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Kustomer, so who receives a campaign reflects current pipeline reality instead of a stale export.
-
Eloqua: 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. Kustomer: REST API. Authentication: API key used as a bearer token, scoped by role. Stacksync manages authentication, retries, and rate limits on both sides.
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 378 integrations available for Eloqua and Kustomer.
Popular · 7 of 378
-
Eloqua ⇄ ZoomInfo -
Eloqua ⇄ Vitally -
Eloqua ⇄ DealCloud -
Eloqua ⇄ Chorusai -
Kustomer ⇄ Iterable -
Kustomer ⇄ Bingads -
Kustomer ⇄ Twitter Ads
No integrations match .
