Skip to content
Data warehouse ⇄ Marketing

Azure Synapse Analytics to Eloqua integration — real-time, two-way sync

Keep Azure Synapse Analytics 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 Azure Synapse Analytics and Eloqua

Put modeled data to work and measure what it drives: Azure Synapse Analytics and Eloqua keep contacts, audiences, and campaign results in step in real time, in both directions.

Azure Synapse Analytics is where your team models customers, product usage, and revenue into trusted tables; Eloqua runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.

Stacksync syncs Schemas, Materialized views, SQL pools, Tables (dedicated SQL pool) in Azure Synapse Analytics with Campaigns, Emails, Forms and Form Submits, Contact Lists and Segments in Eloqua field by field, in real time, and in both directions. You decide which system owns which fields — a computed score or segment can flow out to Eloqua while sends, opens, and conversions flow back to Azure Synapse Analytics — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Sync curated Synapse views into an operational Postgres or Azure SQL database that applications can query cheaply.
  • 02 Consolidate SaaS data alongside lake data so analysts join both through one SQL surface.
  • 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

Suppression and consent stay aligned

Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Azure Synapse Analytics holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in Azure Synapse Analytics appear on the matching record in Eloqua, so targeting, routing, and personalization use up-to-date context.

Activate a modeled audience

A segment or score built in Azure Synapse Analytics — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Eloqua, so campaigns target the people your data actually points to instead of a static export.

What you can sync between Azure Synapse Analytics 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.

Azure Synapse Analytics objects Eloqua objects How this pairing syncs
SQL pools Dedicated or serverless compute contexts that determine how and where queries run. 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. SQL pools is specific to Azure Synapse Analytics and Forms and Form Submits to Eloqua — each maps to any object or custom field on the other side.
Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. 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. Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Contact Lists and Segments to Eloqua — each maps to any object or custom field on the other side.
External tables Tables over files in the data lake, queried through serverless SQL and often read-only in 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. External tables is specific to Azure Synapse Analytics and Contacts to Eloqua — each maps to any object or custom field on the other side.
Views Curated projections used when downstream tools should not read base tables directly. 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. Views is specific to Azure Synapse Analytics and Accounts to Eloqua — each maps to any object or custom field on the other side.
Schemas Namespaces that separate staging, integration, and presentation layers. 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. Schemas is specific to Azure Synapse Analytics and Custom Data Objects to Eloqua — each maps to any object or custom field on the other side.
Materialized views Precomputed aggregates that speed reads of frequently synced result sets. 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. Materialized views is specific to Azure Synapse Analytics and Activities to Eloqua — each maps to any object or custom field on the other side.

How changes propagate between Azure Synapse Analytics 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.

Azure Synapse Analytics Eloqua Interval-based propagation

DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.

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

Eloqua Azure Synapse Analytics 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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.

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.
What ships with Azure Synapse Analytics ⇄ Eloqua

Connect Azure Synapse Analytics and Eloqua for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Eloqua.

How the Azure Synapse Analytics and Eloqua connectors work

Azure Synapse Analytics

Integration surface
SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint
Authentication
SQL authentication or Microsoft Entra ID
Change detection
Polling on watermark columns; Synapse SQL pools do not expose log-based CDC for downstream consumers
Capabilities
read · write

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 Azure Synapse Analytics 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 Azure Synapse Analytics 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
    Azure Synapse Analytics connected
    Eloqua connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Synapse Analytics 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 · Azure Synapse Analytics ⇄ 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
    Azure Synapse Analytics Eloqua
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Synapse Analytics 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.

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 501 integrations available for Azure Synapse Analytics and Eloqua.

Popular · 8 of 501
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.