Skip to content
Data warehouse ⇄ Marketing

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

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

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

BigQuery 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 Tables, Partitioned tables, Clustered tables, Datasets in BigQuery 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 BigQuery — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Land CRM and ERP records in BigQuery continuously so dashboards reflect business systems without nightly batch jobs
  • 02 Activate modeled BigQuery tables by syncing computed attributes back into sales and marketing tools
  • 03 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.
  • 04 Export email opens, clicks, form submits, and bounces from the Bulk API Activities export into a warehouse for lead scoring and multi-touch attribution.

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 BigQuery holds the current state for auditing.

Enrich records with warehouse context

Product-usage counts, plan tier, region, or account owner computed in BigQuery 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 BigQuery — 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 BigQuery 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.

BigQuery objects Eloqua objects How this pairing syncs
Clustered tables Supported; clustering is transparent to the sync. 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. Clustered tables is specific to BigQuery and Accounts to Eloqua — each maps to any object or custom field on the other side.
Datasets Organizational container — you pick which dataset’s tables to sync. 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. Datasets is specific to BigQuery and Custom Data Objects to Eloqua — each maps to any object or custom field on the other side.
Projects Connection scope: the service account grants access per project. 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. Projects is specific to BigQuery and Activities to Eloqua — each maps to any object or custom field on the other side.
Tables The syncable unit: only tables can be synced per the Stacksync docs. Campaigns Multi-step campaign-canvas assets managed through the Application REST API; campaign membership and response data read out for attribution reporting. Tables is specific to BigQuery and Campaigns to Eloqua — each maps to any object or custom field on the other side.
Partitioned tables Synced like regular tables; partition columns map to target fields. Emails Email creative and email-group assets managed via the Application REST API; usually read for reporting rather than written by a sync. Partitioned tables is specific to BigQuery and Emails to Eloqua — each maps to any object or custom field on the other side.

How changes propagate between BigQuery 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.

BigQuery Eloqua Sub-second propagation

DetectionChanges in BigQuery are captured at the source via change data capture — no polling loop against its API. Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen").

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

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

Rate-limit considerations

  • BigQuery: Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes.
  • 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 BigQuery ⇄ Eloqua

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the BigQuery and Eloqua connectors work

BigQuery

Integration surface
GoogleSQL via the BigQuery REST API, client libraries, JDBC/ODBC drivers, and the Storage Read/Write APIs
Authentication
Google Cloud service account: create a dedicated service account, grant roles (BigQuery Data Editor, BigQuery Job User, Cloud Functions Service Agent, Cloud Run Developer, Eventarc Event Receiver
Change detection
Real-time notification service deployed into your Google Cloud project: Eventarc ("a notification service that enables real-time updates to happen") with a Cloud Run "secure portal for real-time notification service in
Capabilities
read · write · CDC
Rate limits
Subject to Google Cloud quotas on queries, DML, and streaming; DML is supported but the platform favors append-heavy batch and streaming loads over row-at-a-time writes
BigQuery setup guide

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

    Choose tables

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

BigQuery 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 502 integrations available for BigQuery and Eloqua.

Popular · 8 of 502
All BigQuery 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