Skip to content
Marketing ⇄ Database

Eloqua to IBM AS/400 integration — real-time, two-way sync

Keep Eloqua and IBM AS/400 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 IBM AS/400

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

Stacksync mirrors Contacts, Accounts, Custom Data Objects, Activities from Eloqua into Libraries, Physical files (tables), Logical files (views), Members in IBM AS/400 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 IBM AS/400, 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 Feed shipment and invoice data from the AS/400 into logistics and finance tools in near real time.
  • 02 Expose AS/400 order, inventory, and item master data to modern SaaS tools without rewriting green-screen applications.
  • 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

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.

Query Eloqua like a database

Contacts, leads, audiences, and campaign metrics from Eloqua live in IBM AS/400 as ordinary tables or collections, joinable with the rest of your data and reachable without touching the vendor API.

Build audiences from your own data

Segments computed in IBM AS/400 from product usage, orders, or account status sync into Eloqua as lists or audiences, so campaigns and ads target the people your data says they should.

What you can sync between Eloqua and IBM AS/400

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 IBM AS/400 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. Physical files (tables) The Db2 for i tables mapped directly to sync targets. Contacts is specific to Eloqua and Physical files (tables) to IBM AS/400 — 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. Logical files (views) Indexed or filtered views over physical files, usable as read sources. Accounts is specific to Eloqua and Logical files (views) to IBM AS/400 — 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. Members Sub-partitions of files in legacy applications, flattened or selected during syncs. Custom Data Objects is specific to Eloqua and Members to IBM AS/400 — 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. Rows / records The unit of read and write, accessed via SQL or record-level access. Activities is specific to Eloqua and Rows / records to IBM AS/400 — 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. Journals and journal receivers The change log that enables log-based CDC on journaled files. Campaigns is specific to Eloqua and Journals and journal receivers to IBM AS/400 — 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. Data queues Program-to-program messaging objects sometimes used to hand events off to integrations. Emails is specific to Eloqua and Data queues to IBM AS/400 — each maps to any object or custom field on the other side.

How changes propagate between Eloqua and IBM AS/400

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 IBM AS/400 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 IBM AS/400 as a row-level write, with types converted between the two schemas.

IBM AS/400 Eloqua Sub-second propagation

DetectionChanges in IBM AS/400 are captured at the source via change data capture — no polling loop against its API. Journal-based CDC by reading journal receivers on journaled files.

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.
  • IBM AS/400: Bounded by system resources and subsystem configuration rather than an API quota.
What ships with Eloqua ⇄ IBM AS/400

Connect Eloqua and IBM AS/400 for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Eloqua–IBM AS/400 connection.

Real-time

Two-way sync

Changes in Eloqua or IBM AS/400 instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Eloqua or IBM AS/400 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 IBM AS/400 record.

Observability

Monitoring

Track your Eloqua ⇄ IBM AS/400 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 IBM AS/400.

How the Eloqua and IBM AS/400 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

IBM AS/400

Integration surface
SQL over JDBC/ODBC to Db2 for i (for example the JTOpen/jt400 driver), alongside native record-level access
Authentication
IBM i user profile credentials (database credentials)
Change detection
Journal-based CDC by reading journal receivers on journaled files; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Bounded by system resources and subsystem configuration rather than an API quota.
How it works

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

    Choose tables

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

Eloqua and IBM AS/400 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 393 integrations available for Eloqua and IBM AS/400.

Popular · 8 of 393
All Eloqua integrations All IBM AS/400 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