Skip to content
Marketing ⇄ Database

Eloqua to InterSystems IRIS integration — real-time, two-way sync

Keep Eloqua and InterSystems IRIS 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 InterSystems IRIS

Give your team Eloqua's contacts, campaigns, and engagement in InterSystems IRIS: 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 InterSystems IRIS, hard to get into campaigns without manual exports.

Stacksync mirrors Forms and Form Submits, Contact Lists and Segments, Contacts, Accounts from Eloqua into Schemas, Persistent Classes, Globals, Namespaces in InterSystems IRIS 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 InterSystems IRIS, 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 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 02 Sync operational tables in IRIS bi-directionally with a CRM so business teams work on IRIS-backed data without SQL access
  • 03 Export email opens, clicks, form submits, and bounces from the Bulk API Activities export into a warehouse for lead scoring and multi-touch attribution.
  • 04 Load purchase or product-usage records into Custom Data Objects linked to Contacts so nurture campaigns branch on behavior mastered in another system.

Common sync patterns

Engagement and results next to the customer

Opens, clicks, sends, RSVPs, or ad activity from Eloqua land in InterSystems IRIS 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 InterSystems IRIS, 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 InterSystems IRIS

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 InterSystems IRIS objects How this pairing syncs
Emails Email creative and email-group assets managed via the Application REST API; usually read for reporting rather than written by a sync. Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Emails is specific to Eloqua and Persistent Classes to InterSystems IRIS — 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. Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in syncs. Forms and Form Submits is specific to Eloqua and Globals to InterSystems IRIS — 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. Namespaces Namespaces partition databases and determine the connection context for integrations. Contact Lists and Segments is specific to Eloqua and Namespaces to InterSystems IRIS — 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. Stored Procedures Server-side logic callable over SQL supports controlled writes and transformations. Contacts is specific to Eloqua and Stored Procedures to InterSystems IRIS — 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. Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Accounts is specific to Eloqua and Tables to InterSystems IRIS — 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. Views SQL views expose curated slices of data for outbound replication. Custom Data Objects is specific to Eloqua and Views to InterSystems IRIS — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and InterSystems IRIS

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 InterSystems IRIS 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 applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

InterSystems IRIS Eloqua Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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.
  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
What ships with Eloqua ⇄ InterSystems IRIS

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits
How it works

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

    Choose tables

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

Eloqua and InterSystems IRIS 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 427 integrations available for Eloqua and InterSystems IRIS.

Popular · 7 of 427
All Eloqua integrations All InterSystems IRIS 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