> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/marketing-automation/eloqua/setup-guide.md). # Eloqua setup guide Mobly's Oracle Eloqua integration syncs every captured-and-enriched lead into your Eloqua Contact database. A Mobly-specific Custom Data Object (CDO) is created automatically to hold the Mobly-side fields that don't have a home on the standard Contact record. Connection runs through Mobly's new integration platform, so there's no external Eloqua app to configure on your side. ## What you can do * **Sync leads to Eloqua Contacts** — every Mobly-captured lead becomes an Eloqua Contact, matched by Email (Eloqua's canonical Contact identifier) * **Map any Mobly field to any Eloqua Contact field** — standard or custom * **Auto-created Mobly Custom Data Object** — Mobly-specific fields (Mobly ID, capture event, capture timestamp, etc.) live on a CDO named **Mobly** that Mobly creates for you at connection time * **Use Eloqua picklist fields** for qualifier mapping * **Toggle Automatic vs Manual sync** — see [Sync modes](/help-center/integrations/marketing-automation/sync-modes.md) ## What's not supported (yet) * **Activity logging** — Mobly doesn't write per-activity records (calls, emails, meetings, notes) to Eloqua. Outreach actions reps take in Mobly stay in Mobly's activity history; Eloqua sees the resulting field updates (e.g., last touch timestamp) but no discrete activity events. For what activity logging looks like on the CRMs that support it (HubSpot, Salesforce, Zoho), see [Finding Mobly activities in your CRM](/help-center/integrations/crm/finding-activities-in-your-crm.md) * **Per-event Campaign / Program sync** — Mobly doesn't yet write per-event membership to Eloqua Campaigns or Programs. Use an Eloqua Program Canvas or Campaign Canvas keyed off a Mobly field change as an alternative * **Custom object sync beyond the Mobly CDO** — Mobly writes to the Contact object and the auto-created Mobly CDO. Other CDOs in your Eloqua instance aren't mapped * **Account / Company sync** — Contact-only today. Company info lives on the Contact record as fields, not as a separate Account object * **Multi-integration** — running Eloqua alongside another Marketing Automation tool in the same Mobly org isn't supported today ## Before you connect You'll need: * An **Eloqua user account** with: * Permission to **create and manage Custom Data Objects** (used at setup time to create the Mobly CDO) * **Create + Edit** access to Contacts and their custom fields * Read access to Contact fields (used when populating the Mapping tab dropdowns) * Access to the correct **Eloqua instance** (Oracle runs multiple regional pods; make sure the user belongs to the instance you want Mobly to write to) * A **Mobly admin account** to view and configure Integrations If your team uses a dedicated integration user in Eloqua, use that account rather than an individual employee's — the connection survives team changes without breaking. ## Connect the integration 1. Go to **Integrations → Eloqua** in Mobly 2. Click **Connect** on the Connect tab 3. Sign in to Eloqua in the OAuth window that opens 4. Approve the requested permissions Detailed walkthrough of the Connect flow: see [Connecting a Marketing Automation tool](/help-center/integrations/marketing-automation/connecting.md). ### The Custom Data Object step After the OAuth handshake, Mobly automatically creates a **Custom Data Object named "Mobly"** in your Eloqua account, plus the fields Mobly needs on it. You'll see a **"Custom Object Created"** confirmation with a **Got It** button — no yes/no choice to make; the CDO is already in flight. {% hint style="info" %} **Give it a few minutes.** The CDO and its fields can take a few minutes to appear in Eloqua and in Mobly's Mapping tab. If the Mapping tab loads with an empty field list right after you connect, wait a beat and refresh — Eloqua's fields propagate asynchronously on their side. {% endhint %} If you later re-authenticate (auth token expired, user changed), the CDO isn't recreated — Mobly reuses the existing "Mobly" CDO on your Eloqua instance. ## Configure data flow Work through the tabs in order: 1. [**Mapping**](/help-center/integrations/marketing-automation/field-mapping.md) — match Mobly fields to Eloqua Contact fields. Mobly-specific fields (Mobly ID, capture event, etc.) map onto the auto-created Mobly CDO; standard persona fields (first name, last name, email, company) map onto the Contact record. 2. [**Qualifiers**](/help-center/integrations/marketing-automation/qualifiers.md) — define qualifiers and map values to Eloqua picklist field options. 3. [**Sync mode**](/help-center/integrations/marketing-automation/sync-modes.md) — Automatic by default; switch to Manual on the Connect tab if needed. Per-event Campaign sync isn't supported for Eloqua yet, so Eloqua events don't show a **Sync Event** connect option. ## Eloqua-specific configuration tips **Contact fields load asynchronously.** The Mapping tab dropdowns for Eloqua Contact fields are populated by an on-demand call to Eloqua's REST API. If a dropdown is unexpectedly empty or slow, Eloqua may be temporarily unavailable — wait a minute and reopen the tab. **Custom fields on the Mobly CDO.** The Mobly-created CDO ships with the fields Mobly needs. If you want to add your own fields to it in Eloqua, you can — Mobly won't remove them. Just don't rename or delete the Mobly-created fields, or field sync will fail with a mapping error in [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md). **Contact-level fields vs CDO fields.** Standard person data (name, email, company, job title) should map to Eloqua Contact fields directly. Mobly-specific metadata (Mobly ID, capture event, scanner, capture timestamp) belongs on the Mobly CDO. Mobly's default mappings already reflect this split — use **Set Defaults** on the Mapping tab as a starting point. **Picklist fields.** Eloqua picklist fields (also called "select list" fields) are the target for qualifier mapping. Every Mobly qualifier value needs a corresponding option on the Eloqua picklist, or you'll see `NO_TAG_MAPPING` errors in Reconciliation. **Instance and pod.** Eloqua runs on regional pods. If the connecting user is in the wrong instance, syncs will land in a Contact database you didn't intend. Confirm the correct instance during the OAuth flow. **Eloqua Contact activity limits.** Eloqua rate-limits contact-write API calls per instance. High-volume events may see occasional throttling — Mobly retries automatically and the leads land eventually. Persistent throttling shows up in [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md). ## Troubleshooting If a synced lead shows up in **Reconciliation → Failed**, see [Fixing Eloqua sync errors](/help-center/integrations/marketing-automation/eloqua/troubleshooting.md). For broader integration questions (auth, permissions, what data lands where), revisit [Connecting a Marketing Automation tool](/help-center/integrations/marketing-automation/connecting.md) and [How data flows from Mobly to your MA tool](/help-center/integrations/marketing-automation/how-data-flows.md). ## Related articles * [Connecting a Marketing Automation tool](/help-center/integrations/marketing-automation/connecting.md) * [Sync modes](/help-center/integrations/marketing-automation/sync-modes.md) * [Field mapping](/help-center/integrations/marketing-automation/field-mapping.md) * [Qualifiers](/help-center/integrations/marketing-automation/qualifiers.md) * [Reconciliation](/help-center/integrations/marketing-automation/reconciliation.md) * [Fixing Eloqua sync errors](/help-center/integrations/marketing-automation/eloqua/troubleshooting.md)