Skip to content
CRM ⇄ Marketing

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

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

Keep the people you sell to and the people you market to in one shared view: Close and Eloqua sync contacts, accounts, and engagement in real time, in both directions.

Close 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 Custom Activities, Custom Fields, Users, Smart Views in Close with Accounts, Custom Data Objects, Activities, Campaigns in Eloqua field by field, in real time, and in both directions. You decide which system owns which fields — Close 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 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • 02 Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • 03 Add or remove Contacts from shared Contact Lists and Segments based on lifecycle stage computed downstream in a database.
  • 04 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.

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 Close, 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 Close 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 Close and Eloqua

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.

Close objects Eloqua objects How this pairing syncs
Contacts People nested under a lead, with emails and phone numbers used for outreach 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. 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. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. 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. Opportunities is specific to Close and Contact Lists and Segments to Eloqua — each maps to any object or custom field on the other side.
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. 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. Tasks is specific to Close and Accounts to Eloqua — each maps to any object or custom field on the other side.
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. 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. Custom Activities is specific to Close and Custom Data Objects to Eloqua — each maps to any object or custom field on the other side.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Campaigns Multi-step campaign-canvas assets managed through the Application REST API; campaign membership and response data read out for attribution reporting. Custom Fields is specific to Close and Campaigns to Eloqua — each maps to any object or custom field on the other side.

How changes propagate between Close and Eloqua

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.

Close Eloqua Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

DeliveryEach detected change is written to Eloqua through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • 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 Close ⇄ Eloqua

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Close ⇄ Eloqua sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Close and Eloqua.

How the Close and Eloqua connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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
How it works

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

    Choose tables

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

Close and Eloqua 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 489 integrations available for Close and Eloqua.

Popular · 8 of 489
All Close integrations All Eloqua 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