Real-time
Two-way sync
Changes in Eloqua or Pigment instantly reflect in both systems. No stale data, no manual imports.
Marketing ⇄ Accounting and finance
Eloqua to Pigment integration — real-time, two-way sync
Keep Eloqua and Pigment 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 Pigment
Put revenue reality behind every campaign: Pigment and Eloqua share the same customers, contacts, and billing status in real time, in both directions.
Pigment records the money — who pays, how much, and whether they are current; Eloqua decides who hears from the business and what they hear. The two overlap wherever the same customers and contacts matter to both, and when that overlap is bridged by CSV exports or an overnight batch, campaigns target on stale billing data and finance works from lists marketing has already changed underneath it.
Stacksync syncs Users and permissions, Applications, Metrics, Dimension lists in Pigment with Emails, Forms and Form Submits, Contact Lists and Segments, Contacts in Eloqua field by field, in real time, and in both directions. You decide which system owns which fields — finance keeps the revenue and payment truth, marketing keeps consent and engagement — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 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
Where Eloqua captures new people: clean records flow to finance
Registrants, form fills, or leads created in Eloqua create or update the matching customer or contact in Pigment, so billing and reporting start from accurate details without re-entry.
Where Pigment tracks lifecycle state: keep Eloqua current
Trial, renewal, churn, or payment state from Pigment updates the contact in Eloqua, so lifecycle campaigns and audience suppression run on current billing reality.
Consent and contact details stay aligned
Email, phone, address, and opt-out flags kept in either system stay consistent in the other, so every send and record honors the latest preferences.
What you can sync between Eloqua and Pigment
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 | Pigment 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. | Tables Row-based transactional data loaded into models from source systems | Emails is specific to Eloqua and Tables to Pigment — 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. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Forms and Form Submits is specific to Eloqua and Scenarios to Pigment — 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. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Contact Lists and Segments is specific to Eloqua and Data imports to Pigment — 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. | Users and permissions Access controls governing which model areas a sync can touch | Contacts is specific to Eloqua and Users and permissions to Pigment — 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. | Applications Planning models organized by domain such as finance, sales, or workforce | Accounts is specific to Eloqua and Applications to Pigment — 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. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Custom Data Objects is specific to Eloqua and Metrics to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Eloqua and Pigment
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 Pigment 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 Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Eloqua Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
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.
- Pigment: Subject to the platform's API rate limits.
What ships with Eloqua ⇄ Pigment
Connect Eloqua and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Eloqua–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Eloqua or Pigment 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 Pigment record.
Observability
Monitoring
Track your Eloqua ⇄ Pigment 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 Pigment.
How the Eloqua and Pigment 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
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
How it works
How to connect Eloqua to Pigment — 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.
- 01
Connect your apps
Authenticate Eloqua and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Eloqua
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Eloqua and Pigment 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.
objects · Eloqua ⇄ PigmentCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Eloqua PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Eloqua and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Eloqua and Pigment: authenticate both systems, choose the objects to sync (such as Eloqua's Emails and Forms and Form Submits), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Eloqua: Import definitions accept a maximum of 100 fields and export definitions a maximum of 250 fields; posts to a staging area are capped at 32 MB and retrieves return up to 50,000 records per batch. Stacksync's field mapping accounts for these differences between Eloqua and Pigment without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Eloqua and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Eloqua and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Eloqua–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Eloqua and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Eloqua: Polling via Bulk API exports filtered on a contact/account modified-date field using EML filter syntax; no general-purpose record-change webhook. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 371 integrations available for Eloqua and Pigment.
Popular · 7 of 371
-
Eloqua ⇄ Navan -
Eloqua ⇄ Ramp -
Eloqua ⇄ Recurly -
Eloqua ⇄ Rillet -
Pigment ⇄ Demandbase -
Pigment ⇄ Iterable -
Pigment ⇄ Bingads
No integrations match .
