--- title: "Eloqua connector: setup and compatibility | Stacksync" description: "Eloqua integration guide: plan Contacts and Accounts, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/eloqua last_modified: 2026-09-15 --- Marketing · Two-way sync platform # Eloqua integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Eloqua workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Contacts, Accounts and Activities. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Contacts** - **Accounts** - **Custom Data Objects** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=eloqua) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Eloqua records to discuss. These Eloqua record examples help scope a technical review. They are not a list of verified Stacksync operations. Contacts Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Accounts Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Custom Data Objects Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Activities Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Campaigns Keep campaign ID, channel/account context, and separate audience membership IDs. Emails Identify this record type and the operation you need to review with Stacksync. Connection setup ## Eloqua connection requirements. Review Eloqua access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Eloqua account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Eloqua, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Eloqua integration. Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Eloqua **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Load related records in the right order Resolve the organization relationship and any owner or consent references required by the destination. ### Mapping checks by record type #### Contacts Confirm object support with Stacksync Identity Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Fields to consider Source person ID · Display name · Email address · Organization reference · Consent state Related records to resolve first Resolve the organization relationship and any owner or consent references required by the destination. Test before going live Test an email change, two records sharing an email, and a person associated with multiple organizations. #### Accounts Confirm object support with Stacksync Identity Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient. Fields to consider Source record ID · Legal or display name · Business-unit reference · Lifecycle status Related records to resolve first Resolve parent organizations, business units, and currency references before dependent transactions. Test before going live Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only. #### Activities Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. #### Campaigns Confirm object support with Stacksync Identity Keep campaign ID, channel/account context, and separate audience membership IDs. Fields to consider Source campaign ID · Channel reference · Status · Audience references · Measurement window Related records to resolve first Resolve contact/audience identities and channel-account references. Test before going live Test a removed audience member, a paused campaign, and one campaign reported across multiple channels. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Eloqua integration in four steps. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. ### View the four setup tests and expected results 1. ### Confirm the intended Eloqua account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Contacts Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test an email change, two records sharing an email, and a person associated with multiple organizations. **Expected result:** An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. 3. ### Test the operation your workflow needs Review one Eloqua record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Eloqua integration. ### Diagnose record matching, delayed changes, and rejected operations A Eloqua record appears under the wrong destination record Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Resolve the organization relationship and any owner or consent references required by the destination. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Eloqua implementation’s change-detection method for Contacts, Accounts and Activities. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Eloqua object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Eloqua workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=eloqua) ## Eloqua integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Eloqua connector FAQ ### How should I plan an integration with Eloqua? Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Eloqua connector write changes back? Write-back support is not established for this connection. Review the Eloqua records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Eloqua data? Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. ### Which related records should I load first for Eloqua? Resolve the organization relationship and any owner or consent references required by the destination. ### How do I validate Eloqua changes after the initial load? Test an email change, two records sharing an email, and a person associated with multiple organizations. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window. ### What will we cover in a Eloqua integration demo? Start with one workflow and a sample record from Contacts, Accounts and Activities. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Eloqua from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Eloqua and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Eloqua. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Eloqua record changes.” - “Create a Genie that answers questions about our Eloqua data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Eloqua connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Eloqua and Salesforce](https://www.stacksync.com/integrations/eloqua-and-salesforce) - [Cvent and Eloqua](https://www.stacksync.com/integrations/cvent-and-eloqua) - [Eloqua and Zoom](https://www.stacksync.com/integrations/eloqua-and-zoom) - [Eloqua and Rockset](https://www.stacksync.com/integrations/eloqua-and-rockset) - [Databricks and Eloqua](https://www.stacksync.com/integrations/databricks-and-eloqua) - [Eloqua and Microsoft Power BI](https://www.stacksync.com/integrations/eloqua-and-microsoft-power-bi) - [Eloqua and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/eloqua-and-salesforce-marketing-cloud) - [Eloqua and HubSpot](https://www.stacksync.com/integrations/eloqua-and-hubspot) ### CRM · 46 - [Eloqua and 6sense](https://www.stacksync.com/integrations/6sense-and-eloqua) - [Eloqua and Affinity](https://www.stacksync.com/integrations/affinity-and-eloqua) - [Eloqua and Apollo.io](https://www.stacksync.com/integrations/apollo-io-and-eloqua) - [Eloqua and Attio](https://www.stacksync.com/integrations/attio-and-eloqua) - [Eloqua and Chorusai](https://www.stacksync.com/integrations/chorusai-and-eloqua) - [Eloqua and Clari](https://www.stacksync.com/integrations/clari-and-eloqua) - [Eloqua and Clearbit](https://www.stacksync.com/integrations/clearbit-and-eloqua) - [Eloqua and Close](https://www.stacksync.com/integrations/close-and-eloqua) - [Eloqua and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-eloqua) - [Eloqua and Creatio CRM](https://www.stacksync.com/integrations/creatio-crm-and-eloqua) - [Eloqua and Crustdata](https://www.stacksync.com/integrations/crustdata-and-eloqua) - [Eloqua and DealCloud](https://www.stacksync.com/integrations/dealcloud-and-eloqua) - [Eloqua and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-eloqua) - [Eloqua and Folk CRM](https://www.stacksync.com/integrations/eloqua-and-folk-crm) - [Eloqua and Freshsales](https://www.stacksync.com/integrations/eloqua-and-freshsales) - [Eloqua and Freshworks CRM](https://www.stacksync.com/integrations/eloqua-and-freshworks-crm) - [Eloqua and Gladly](https://www.stacksync.com/integrations/eloqua-and-gladly) - [Eloqua and Gong](https://www.stacksync.com/integrations/eloqua-and-gong) - [Eloqua and Gorgias](https://www.stacksync.com/integrations/eloqua-and-gorgias) - [Eloqua and HubSpot](https://www.stacksync.com/integrations/eloqua-and-hubspot) - [Eloqua and Infor CRM](https://www.stacksync.com/integrations/eloqua-and-infor-crm) - [Eloqua and Insightly](https://www.stacksync.com/integrations/eloqua-and-insightly) - [Eloqua and Intercom](https://www.stacksync.com/integrations/eloqua-and-intercom) - [Eloqua and Kommo](https://www.stacksync.com/integrations/eloqua-and-kommo) - [Eloqua and Kustomer](https://www.stacksync.com/integrations/eloqua-and-kustomer) - [Eloqua and Microsoft Dynamics 365 Sales](https://www.stacksync.com/integrations/eloqua-and-microsoft-dynamics-365-sales) - [Eloqua and Nimble](https://www.stacksync.com/integrations/eloqua-and-nimble) - [Eloqua and Nutshell](https://www.stacksync.com/integrations/eloqua-and-nutshell) - [Eloqua and Oracle CX Sales](https://www.stacksync.com/integrations/eloqua-and-oracle-cx-sales) - [Eloqua and Outreach](https://www.stacksync.com/integrations/eloqua-and-outreach) - [Eloqua and Pipedrive](https://www.stacksync.com/integrations/eloqua-and-pipedrive) - [Eloqua and Salesforce](https://www.stacksync.com/integrations/eloqua-and-salesforce) - [Eloqua and Salesloft](https://www.stacksync.com/integrations/eloqua-and-salesloft) - [Eloqua and SAP Sales Cloud](https://www.stacksync.com/integrations/eloqua-and-sap-sales-cloud) - [Eloqua and Seismic](https://www.stacksync.com/integrations/eloqua-and-seismic) - [Eloqua and Shopify](https://www.stacksync.com/integrations/eloqua-and-shopify) - [Eloqua and Streak CRM](https://www.stacksync.com/integrations/eloqua-and-streak-crm) - [Eloqua and SugarCRM](https://www.stacksync.com/integrations/eloqua-and-sugarcrm) - [Eloqua and Twenty CRM](https://www.stacksync.com/integrations/eloqua-and-twenty-crm) - [Eloqua and Veeva CRM](https://www.stacksync.com/integrations/eloqua-and-veeva-crm) - [Eloqua and Vitally](https://www.stacksync.com/integrations/eloqua-and-vitally) - [Eloqua and Vtiger CRM](https://www.stacksync.com/integrations/eloqua-and-vtiger-crm) - [Eloqua and Xactly](https://www.stacksync.com/integrations/eloqua-and-xactly) - [Eloqua and Zoho CRM](https://www.stacksync.com/integrations/eloqua-and-zoho-crm) - [Eloqua and Zoho SalesIQ](https://www.stacksync.com/integrations/eloqua-and-zoho-salesiq) - [Eloqua and ZoomInfo](https://www.stacksync.com/integrations/eloqua-and-zoominfo) ### ERP · 38 - [Eloqua and Acumatica](https://www.stacksync.com/integrations/acumatica-and-eloqua) - [Eloqua and Blue Yonder WMS](https://www.stacksync.com/integrations/blue-yonder-wms-and-eloqua) - [Eloqua and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-eloqua) - [Eloqua and Cin7](https://www.stacksync.com/integrations/cin7-and-eloqua) - [Eloqua and DEAR Inventory](https://www.stacksync.com/integrations/dear-inventory-and-eloqua) - [Eloqua and Dynamics 365 Business Central](https://www.stacksync.com/integrations/eloqua-and-microsoft-dynamics-365-business-central) - [Eloqua and Dynamics 365 F&O](https://www.stacksync.com/integrations/dynamics-365-finance-operations-and-eloqua) - [Eloqua and Epicor ERP](https://www.stacksync.com/integrations/eloqua-and-epicor-erp) - [Eloqua and Extensiv (3PL Central)](https://www.stacksync.com/integrations/eloqua-and-extensiv-3pl-central) - [Eloqua and Fishbowl Manufacturing](https://www.stacksync.com/integrations/eloqua-and-fishbowl-manufacturing) - [Eloqua and Infor CloudSuite](https://www.stacksync.com/integrations/eloqua-and-infor-cloudsuite) - [Eloqua and Infor LN](https://www.stacksync.com/integrations/eloqua-and-infor-ln) - [Eloqua and Infor M3](https://www.stacksync.com/integrations/eloqua-and-infor-m3) - [Eloqua and Infor WMS](https://www.stacksync.com/integrations/eloqua-and-infor-wms) - [Eloqua and Linnworks](https://www.stacksync.com/integrations/eloqua-and-linnworks) - [Eloqua and Logiwa WMS](https://www.stacksync.com/integrations/eloqua-and-logiwa-wms) - [Eloqua and Macola ERP](https://www.stacksync.com/integrations/eloqua-and-macola-erp) - [Eloqua and Manhattan Associates WMS](https://www.stacksync.com/integrations/eloqua-and-manhattan-associates-wms) - [Eloqua and Microsoft Dynamics GP](https://www.stacksync.com/integrations/eloqua-and-microsoft-dynamics-gp) - [Eloqua and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/eloqua-and-microsoft-dynamics-nav) - [Eloqua and NetSuite](https://www.stacksync.com/integrations/eloqua-and-netsuite) - [Eloqua and Odoo](https://www.stacksync.com/integrations/eloqua-and-odoo) - [Eloqua and Oracle Fusion ERP](https://www.stacksync.com/integrations/eloqua-and-oracle-fusion-erp) - [Eloqua and Plex ERP](https://www.stacksync.com/integrations/eloqua-and-plex-erp) - [Eloqua and QAD ERP](https://www.stacksync.com/integrations/eloqua-and-qad-erp) - [Eloqua and Rootstock ERP](https://www.stacksync.com/integrations/eloqua-and-rootstock-erp) - [Eloqua and Sage 100](https://www.stacksync.com/integrations/eloqua-and-sage-100) - [Eloqua and Sage 300](https://www.stacksync.com/integrations/eloqua-and-sage-300) - [Eloqua and Sage Intacct](https://www.stacksync.com/integrations/eloqua-and-sage-intacct) - [Eloqua and Sage X3](https://www.stacksync.com/integrations/eloqua-and-sage-x3) - [Eloqua and SAP](https://www.stacksync.com/integrations/eloqua-and-sap) - [Eloqua and SAP Business ByDesign](https://www.stacksync.com/integrations/eloqua-and-sap-business-bydesign) - [Eloqua and SAP Business One](https://www.stacksync.com/integrations/eloqua-and-sap-business-one) - [Eloqua and SAP S/4HANA](https://www.stacksync.com/integrations/eloqua-and-sap-s4hana) - [Eloqua and SuiteAnalytics](https://www.stacksync.com/integrations/eloqua-and-suite-analytics) - [Eloqua and Syspro](https://www.stacksync.com/integrations/eloqua-and-syspro) - [Eloqua and TikTok Shop](https://www.stacksync.com/integrations/eloqua-and-tiktok) - [Eloqua and Unleashed Software](https://www.stacksync.com/integrations/eloqua-and-unleashed-software) ### Database · 50 - [Eloqua and Airtable](https://www.stacksync.com/integrations/airtable-and-eloqua) - [Eloqua and Amazon Aurora](https://www.stacksync.com/integrations/amazon-aurora-and-eloqua) - [Eloqua and Amazon DynamoDB](https://www.stacksync.com/integrations/dynamo-db-and-eloqua) - [Eloqua and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-eloqua) - [Eloqua and Amazon Lightsail](https://www.stacksync.com/integrations/amazon-lightsail-and-eloqua) - [Eloqua and Amazon RDS](https://www.stacksync.com/integrations/amazon-rds-and-eloqua) - [Eloqua and Apache Cassandra](https://www.stacksync.com/integrations/apache-cassandra-and-eloqua) - [Eloqua and AWS Aurora MySQL](https://www.stacksync.com/integrations/aws-aurora-mysql-and-eloqua) - [Eloqua and AWS Aurora PostgreSQL](https://www.stacksync.com/integrations/aws-aurora-postgresql-and-eloqua) - [Eloqua and Azure Cosmos DB](https://www.stacksync.com/integrations/azure-cosmos-db-and-eloqua) - [Eloqua and Azure SQL Database](https://www.stacksync.com/integrations/azure-sql-database-and-eloqua) - [Eloqua and Citus](https://www.stacksync.com/integrations/citus-and-eloqua) - [Eloqua and CockroachDB](https://www.stacksync.com/integrations/cockroachdb-and-eloqua) - [Eloqua and Couchbase](https://www.stacksync.com/integrations/couchbase-and-eloqua) - [Eloqua and DuckDB](https://www.stacksync.com/integrations/duckdb-and-eloqua) - [Eloqua and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-eloqua) - [Eloqua and Firebase](https://www.stacksync.com/integrations/eloqua-and-firebase) - [Eloqua and Google AlloyDB](https://www.stacksync.com/integrations/eloqua-and-google-alloydb) - [Eloqua and Google Cloud Spanner](https://www.stacksync.com/integrations/eloqua-and-google-cloud-spanner) - [Eloqua and Google Cloud SQL](https://www.stacksync.com/integrations/eloqua-and-google-cloud-sql) - [Eloqua and IBM AS/400](https://www.stacksync.com/integrations/eloqua-and-ibm-as400) - [Eloqua and IBM Db2](https://www.stacksync.com/integrations/eloqua-and-ibm-db2) - [Eloqua and IBM Informix](https://www.stacksync.com/integrations/eloqua-and-ibm-informix) - [Eloqua and InfluxDB](https://www.stacksync.com/integrations/eloqua-and-influxdb) - [Eloqua and InterSystems IRIS](https://www.stacksync.com/integrations/eloqua-and-intersystems-iris) - [Eloqua and JDBC](https://www.stacksync.com/integrations/eloqua-and-jdbc) - [Eloqua and MariaDB](https://www.stacksync.com/integrations/eloqua-and-mariadb) - [Eloqua and MarkLogic](https://www.stacksync.com/integrations/eloqua-and-marklogic) - [Eloqua and MongoDB](https://www.stacksync.com/integrations/eloqua-and-mongodb) - [Eloqua and MySQL](https://www.stacksync.com/integrations/eloqua-and-mysql) - [Eloqua and Neo4j](https://www.stacksync.com/integrations/eloqua-and-neo4j) - [Eloqua and OCI Database (Oracle Cloud)](https://www.stacksync.com/integrations/eloqua-and-oci-database) - [Eloqua and OpenSearch](https://www.stacksync.com/integrations/eloqua-and-opensearch) - [Eloqua and Oracle DB](https://www.stacksync.com/integrations/eloqua-and-oracle-db) - [Eloqua and Postgres Heroku](https://www.stacksync.com/integrations/eloqua-and-postgres-heroku) - [Eloqua and PostgreSQL](https://www.stacksync.com/integrations/eloqua-and-postgresql) - [Eloqua and RavenDB](https://www.stacksync.com/integrations/eloqua-and-ravendb) - [Eloqua and Redis Enterprise](https://www.stacksync.com/integrations/eloqua-and-redis-enterprise) - [Eloqua and Reltio](https://www.stacksync.com/integrations/eloqua-and-reltio) - [Eloqua and Render Postgres](https://www.stacksync.com/integrations/eloqua-and-render-postgres) - [Eloqua and SAP ASE (Sybase)](https://www.stacksync.com/integrations/eloqua-and-sap-ase-sybase) - [Eloqua and SAP HANA](https://www.stacksync.com/integrations/eloqua-and-sap-hana) - [Eloqua and Scaleway Postgres](https://www.stacksync.com/integrations/eloqua-and-scaleway-postgres) - [Eloqua and SingleStore](https://www.stacksync.com/integrations/eloqua-and-singlestore) - [Eloqua and SQL Server](https://www.stacksync.com/integrations/eloqua-and-sql-server) - [Eloqua and Supabase](https://www.stacksync.com/integrations/eloqua-and-supabase) - [Eloqua and TiDB](https://www.stacksync.com/integrations/eloqua-and-tidb) - [Eloqua and TimescaleDB](https://www.stacksync.com/integrations/eloqua-and-timescaledb) - [Eloqua and VoltDB](https://www.stacksync.com/integrations/eloqua-and-voltdb) - [Eloqua and YugabyteDB](https://www.stacksync.com/integrations/eloqua-and-yugabytedb) ### Data warehouse · 29 - [Eloqua and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-eloqua) - [Eloqua and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-eloqua) - [Eloqua and Apache Doris](https://www.stacksync.com/integrations/apache-doris-and-eloqua) - [Eloqua and Apache Druid](https://www.stacksync.com/integrations/apache-druid-and-eloqua) - [Eloqua and Apache Hive](https://www.stacksync.com/integrations/apache-hive-and-eloqua) - [Eloqua and Apache Impala](https://www.stacksync.com/integrations/apache-impala-and-eloqua) - [Eloqua and Apache Kylin](https://www.stacksync.com/integrations/apache-kylin-and-eloqua) - [Eloqua and Apache Pinot](https://www.stacksync.com/integrations/apache-pinot-and-eloqua) - [Eloqua and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-eloqua) - [Eloqua and BigQuery](https://www.stacksync.com/integrations/bigquery-and-eloqua) - [Eloqua and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-eloqua) - [Eloqua and Cloudera Data Platform](https://www.stacksync.com/integrations/cloudera-data-platform-and-eloqua) - [Eloqua and Databricks](https://www.stacksync.com/integrations/databricks-and-eloqua) - [Eloqua and Dremio](https://www.stacksync.com/integrations/dremio-and-eloqua) - [Eloqua and Exasol](https://www.stacksync.com/integrations/eloqua-and-exasol) - [Eloqua and Firebolt](https://www.stacksync.com/integrations/eloqua-and-firebolt) - [Eloqua and Google Cloud Platform](https://www.stacksync.com/integrations/eloqua-and-google-cloud-platform) - [Eloqua and Greenplum](https://www.stacksync.com/integrations/eloqua-and-greenplum) - [Eloqua and IBM Netezza](https://www.stacksync.com/integrations/eloqua-and-ibm-netezza) - [Eloqua and Materialize](https://www.stacksync.com/integrations/eloqua-and-materialize) - [Eloqua and MotherDuck](https://www.stacksync.com/integrations/eloqua-and-motherduck) - [Eloqua and Rockset](https://www.stacksync.com/integrations/eloqua-and-rockset) - [Eloqua and Snowflake](https://www.stacksync.com/integrations/eloqua-and-snowflake) - [Eloqua and Starburst Enterprise](https://www.stacksync.com/integrations/eloqua-and-starburst-enterprise) - [Eloqua and StarRocks](https://www.stacksync.com/integrations/eloqua-and-starrocks) - [Eloqua and Teradata Vantage](https://www.stacksync.com/integrations/eloqua-and-teradata-vantage) - [Eloqua and Tinybird](https://www.stacksync.com/integrations/eloqua-and-tinybird) - [Eloqua and Vertica](https://www.stacksync.com/integrations/eloqua-and-vertica) - [Eloqua and Yellowbrick](https://www.stacksync.com/integrations/eloqua-and-yellowbrick) ### Accounting and finance · 17 - [Eloqua and Adyen](https://www.stacksync.com/integrations/adyen-and-eloqua) - [Eloqua and Anaplan](https://www.stacksync.com/integrations/anaplan-and-eloqua) - [Eloqua and BILL](https://www.stacksync.com/integrations/bill-and-eloqua) - [Eloqua and Braintree](https://www.stacksync.com/integrations/braintree-and-eloqua) - [Eloqua and Chargebee](https://www.stacksync.com/integrations/chargebee-and-eloqua) - [Eloqua and Coupa](https://www.stacksync.com/integrations/coupa-and-eloqua) - [Eloqua and Hyperline](https://www.stacksync.com/integrations/eloqua-and-hyperline) - [Eloqua and LogiSense](https://www.stacksync.com/integrations/eloqua-and-logisense) - [Eloqua and Navan](https://www.stacksync.com/integrations/eloqua-and-navan) - [Eloqua and Pigment](https://www.stacksync.com/integrations/eloqua-and-pigment) - [Eloqua and QuickBooks](https://www.stacksync.com/integrations/eloqua-and-quickbooks) - [Eloqua and Ramp](https://www.stacksync.com/integrations/eloqua-and-ramp) - [Eloqua and Recurly](https://www.stacksync.com/integrations/eloqua-and-recurly) - [Eloqua and Rillet](https://www.stacksync.com/integrations/eloqua-and-rillet) - [Eloqua and Stripe](https://www.stacksync.com/integrations/eloqua-and-stripe) - [Eloqua and Workday](https://www.stacksync.com/integrations/eloqua-and-workday) - [Eloqua and Zuora](https://www.stacksync.com/integrations/eloqua-and-zuora) ### AI · 5 - [Eloqua and Anthropic](https://www.stacksync.com/integrations/anthropic-and-eloqua) - [Eloqua and Autopilot](https://www.stacksync.com/integrations/autopilot-and-eloqua) - [Eloqua and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-eloqua) - [Eloqua and OpenAI](https://www.stacksync.com/integrations/eloqua-and-openai) - [Eloqua and Pinecone](https://www.stacksync.com/integrations/eloqua-and-pinecone) ### Analytics · 7 - [Eloqua and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-eloqua) - [Eloqua and Microsoft Power BI](https://www.stacksync.com/integrations/eloqua-and-microsoft-power-bi) - [Eloqua and Mixpanel](https://www.stacksync.com/integrations/eloqua-and-mixpanel) - [Eloqua and Pendo](https://www.stacksync.com/integrations/eloqua-and-pendo) - [Eloqua and Splunk](https://www.stacksync.com/integrations/eloqua-and-splunk) - [Eloqua and Tableau](https://www.stacksync.com/integrations/eloqua-and-tableau) - [Eloqua and Treasure Data](https://www.stacksync.com/integrations/eloqua-and-treasuredata) ### Communications · 6 - [Eloqua and Aircall](https://www.stacksync.com/integrations/aircall-and-eloqua) - [Eloqua and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-eloqua) - [Eloqua and Gmail](https://www.stacksync.com/integrations/eloqua-and-gmail) - [Eloqua and Infobip](https://www.stacksync.com/integrations/eloqua-and-infobip) - [Eloqua and RingCentral](https://www.stacksync.com/integrations/eloqua-and-ringcentral) - [Eloqua and Zoom](https://www.stacksync.com/integrations/eloqua-and-zoom) ### E-commerce · 8 - [Eloqua and Akeneo](https://www.stacksync.com/integrations/akeneo-and-eloqua) - [Eloqua and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-eloqua) - [Eloqua and ChannelEngine](https://www.stacksync.com/integrations/channelengine-and-eloqua) - [Eloqua and EasyPost](https://www.stacksync.com/integrations/easypost-and-eloqua) - [Eloqua and Magento](https://www.stacksync.com/integrations/eloqua-and-magento) - [Eloqua and NuORDER](https://www.stacksync.com/integrations/eloqua-and-nuorder) - [Eloqua and Shipwire](https://www.stacksync.com/integrations/eloqua-and-shipwire) - [Eloqua and Shopware](https://www.stacksync.com/integrations/eloqua-and-shopware) ### Marketing · 8 - [Eloqua and Bingads](https://www.stacksync.com/integrations/bingads-and-eloqua) - [Eloqua and Cvent](https://www.stacksync.com/integrations/cvent-and-eloqua) - [Eloqua and Demandbase](https://www.stacksync.com/integrations/demandbase-and-eloqua) - [Eloqua and Iterable](https://www.stacksync.com/integrations/eloqua-and-iterable) - [Eloqua and Marketo](https://www.stacksync.com/integrations/eloqua-and-marketo) - [Eloqua and RollWorks](https://www.stacksync.com/integrations/eloqua-and-rollworks) - [Eloqua and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/eloqua-and-salesforce-marketing-cloud) - [Eloqua and Twitter Ads](https://www.stacksync.com/integrations/eloqua-and-twitter-ads) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)