Skip to content
Marketing ⇄ Database

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

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

Give your team Eloqua's contacts, campaigns, and engagement in Reltio: query them with SQL, push audiences built from your own data back to Eloqua, and skip the marketing API.

Eloqua holds the people, audiences, and campaign activity that marketing runs on, but that data sits behind interfaces built for marketers, not for your internal systems. Engineers and analysts who need contacts, list membership, or engagement, for reporting, attribution, or product logic, end up writing integration code against a rate-limited API and maintaining it forever. Meanwhile the customer and usage data marketers want for targeting already lives in Reltio, hard to get into campaigns without manual exports.

Stacksync mirrors Accounts, Custom Data Objects, Activities, Campaigns from Eloqua into Entities, Relations, Crosswalks, Interactions in Reltio field by field, in real time, and in both directions. Marketing records become rows your code can query and join with product and customer data; audiences and attributes computed in Reltio, from usage, orders, or account status, sync back into Eloqua to drive campaigns and ads, with Eloqua kept authoritative for engagement. You decide which side owns which fields, and Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 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

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Eloqua land in Reltio beside the matching customer record, ready for reporting and revenue attribution.

React to marketing changes as row changes

A new lead, form fill, or list change in Eloqua arrives as a row change in Reltio, so scoring, jobs, and notifications run in the tooling your team already uses.

Keep contact attributes consistent

Lifecycle stage, subscription status, or plan maintained on either side stays current on the other, ending exports and dual data entry.

What you can sync between Eloqua and Reltio

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 Reltio objects How this pairing syncs
Campaigns Multi-step campaign-canvas assets managed through the Application REST API; campaign membership and response data read out for attribution reporting. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Campaigns is specific to Eloqua and Crosswalks to Reltio — 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. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Emails is specific to Eloqua and Interactions to Reltio — 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. Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Forms and Form Submits is specific to Eloqua and Matches (Potential Matches) to Reltio — 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. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Contact Lists and Segments is specific to Eloqua and Activity Log to Reltio — each maps to any object or custom field on the other side.
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. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Contacts is specific to Eloqua and Data Change Requests (DCR) to Reltio — 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. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Accounts is specific to Eloqua and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and Reltio

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

Reltio Eloqua Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Eloqua ⇄ Reltio

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Eloqua ⇄ Reltio 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 Reltio.

How the Eloqua and Reltio 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

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

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

    Choose tables

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

Eloqua and Reltio 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 391 integrations available for Eloqua and Reltio.

Popular · 8 of 391
All Eloqua integrations All Reltio 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