Skip to main content

​
What this is

Eloqua is a real-time destination. Data flows out of Zeotap CDP to Oracle Eloqua: when a customer reaches a Send to Destinations node in a journey, Zeotap sends that customer’s Eloqua contact ID to Oracle Eloqua and asks Eloqua to deliver a pre-built email asset to them. Zeotap calls Oracle Eloqua’s Email Deployment API on your behalf. You do not call any API yourself. Oracle Eloqua is a B2B marketing automation platform for building and running cross-channel campaigns across email, display advertising and landing pages. This integration uses the one capability that suits journeys: triggering an individual, event-driven email send to a named contact at the moment the journey reaches the node. Two things follow from that design:
  • Zeotap never creates or edits email content. The email asset must already exist and be approved inside Eloqua. Zeotap only instructs Eloqua to send that existing asset to a resolved contact.
  • The integration is one-way. Zeotap does not read data back from Eloqua. For the current list of what Zeotap connects to, and in which direction, see the integrations master list.
This page covers the real-time, journey-driven destination. For how destinations work in general, see Destinations; for the other journey-driven connectors, see Real-time integrations.

​
Supported identifiers and actions

The integration exposes a single action. It does not support ID extension, delete, or delta upload: The action does not send a standard Zeotap identifier such as an email address or a hashed email. It sends Eloqua’s own internal contact ID — the numeric primary key Eloqua assigns to a contact in your instance. Eloqua’s Email Deployment API addresses contacts by that key and does not accept an email address in its place, so the contact ID has to be present on the Zeotap customer profile before the journey runs.

​
Prerequisites

Complete all of the following before you create the destination. Everything in this list is done on the Oracle Eloqua side or in your Zeotap catalogue — there is no Zeotap API step.
  • An Oracle Eloqua account with REST API access enabled, and the Company Name, Username and Password for it. The account needs enough permission in Eloqua to create email deployments.
  • The Eloqua region (pod) your instance runs on — for example p03. You can read it from your Eloqua login URL after you sign in, or resolve it by calling Oracle Eloqua’s own GET https://login.eloqua.com/id endpoint with those credentials.
  • The email asset pre-built inside Eloqua, and its Email Asset ID noted down. Zeotap cannot create the asset for you.
  • The Eloqua contact ID available as an attribute on the Zeotap customer profile, so the journey has something to map. Enrich it onto the profile before you go live.
Oracle Eloqua applies a rate limit of 60 API requests per minute to your instance, shared across every integration that talks to it. Factor in any other tools already calling that instance when you size a journey that fires at volume.

​
Create the Eloqua destination

Once you have the prerequisites, create the destination in the Destinations module.
1

Open the Destinations module

Log in to the Zeotap CDP app and go to Integrate > Destinations.
2

Click + Create Destination

On the Destinations landing page, click + Create Destination in the top right.
Destinations listing page under Integrate, showing the Private Destination and Public Destination tabs, a table of existing destinations, and the Create Destination button highlighted in the top right.

Figure 1 — Destinations listing page with the Create Destination button highlighted.

3

Search for Eloqua in the catalogue

Under All Destinations, use Search for a Destination to find Eloqua, then select the Eloqua card.
All Destinations catalogue listing destination cards by platform name and category, with the Search for a Destination field highlighted.

Figure 2 — All Destinations catalogue with the search field highlighted.

4

Enter the destination details

On the Enter Destination Details screen, fill in:
  • Destination Name — a descriptive label for this connection, so you can identify it later.
  • Username — the username of your Eloqua account, prefixed with your Company Name (see the tip below).
  • Password — the password for your Eloqua account.
  • Region — the Eloqua region (pod) your instance runs on.
Eloqua authenticates on a combined company-and-user string, so the Username field is not just your login name. Enter your Company Name and Username separated by a single backslash. For example, if your company is Acme and your username is jdoe, enter:
Enter Destination Details screen for Eloqua, showing the Destination Name, Username, Password and Region fields, with a Destination Details and Mapping step indicator above and Back and Next buttons below.

Figure 3 — Enter Destination Details screen for Eloqua.

Review the values and click Next to move to the mapping step.
5

Choose the action and map the contact ID

On the mapping screen:
  1. Give the mapping a name in place of Untitled Mapping, so you can recognise it on the journey node later.
  2. Under Choose your Action, select Trigger Emails in Eloqua. This is the only action this destination offers.
  3. Under Map the Fields, the Contact Id destination field is already in place and is mandatory. Against it, use Choose Catalogue Attribute to pick the catalogue attribute that holds the Eloqua contact ID.
Mapping screen titled Untitled Mapping, with Choose your Action set to Trigger Emails in Eloqua and a Map the Fields table pairing a Choose Catalogue Attribute dropdown with the required Contact Id destination field of type String.

Figure 4 — Mapping screen with the action set to Trigger Emails in Eloqua and the Contact Id destination field awaiting a catalogue attribute.

6

Create the destination

Click Save Mapping, then Create Destination. The destination is now available to attach to a journey.

​
Add the destination to a journey

The Eloqua destination does nothing on its own — it fires only from a journey node. Build or open a workflow in Journeys, then attach the destination at the point where the email should go out.
1

Add a Send to Destinations action

In the workflow, click + at the point where the email should fire and choose Send to Destinations from the Choose an action menu.
Choose an action menu in a journey workflow listing Add a Condition, Add a Delay, Create a Multi-branch Split, Create a True/False Split and Send to Destinations, with Send to Destinations highlighted and a tooltip explaining that it forwards customer data to channels that send emails, show ads or run analytics.

Figure 5 — Choose an action menu in the journey workflow, with Send to Destinations highlighted.

2

Select the Eloqua destination

In the Send to Destinations panel, use Search to find the Eloqua destination you created, then select its card. You can also create one here with + Add New Destination if you skipped the step above.
Send to Destinations panel with a Search field and an Add New Destination link, showing a grid of selectable destination cards each labelled with its platform and destination name.

Figure 6 — Send to Destinations panel listing the destinations available to attach.

3

Configure the email send

The connection fields — Destination Name, Username, Password and Region — are already filled in from the destination you created. Complete the journey-specific fields:
  • Email ID — the Email Asset ID of the pre-built email in Eloqua. This is the numeric identifier of the asset you want to trigger; find it in your Eloqua instance.
  • Email Name — the email asset name as it appears in Eloqua. Used for reference only; it does not affect delivery.
  • Name — a label for this deployment instance. It identifies the send inside Eloqua and does not affect the email content or delivery.
Eloqua destination panel inside a journey, showing the pre-filled Destination Name, Username, Password and Region fields followed by the Email ID, Email Name and Name fields, with Cancel and Save Destination buttons.

Figure 7 — Eloqua destination settings inside the journey node.

4

Save the destination

Click Save Destination. The node now shows the attached Eloqua destination with its mapping and action.
Send to Destinations node showing an attached Eloqua destination card with the destination name, the mapping name and the Trigger Emails in Eloqua action, plus a delete control and an Add New Destination link.

Figure 8 — Journey node with the Eloqua destination attached.

​
Verify the trigger fired

Nothing is sent until the workflow is live, so publish first and then confirm the send from the Eloqua side.
  1. Publish the workflow. Click Publish Workflow. The workflow moves to a Published status in the workflow listing.
  2. Send one contact through. Let a single customer who has a valid Eloqua contact ID on their profile reach the node.
  3. Check the contact in Eloqua. Open that contact’s activity history in your Eloqua instance. A send triggered this way is recorded there with a send type of QuickSend, against the email asset whose ID you entered.
  4. Confirm receipt. The contact should receive the pre-built email as it is defined in Eloqua.
If the activity history shows no record at all for that contact, work through the table below before raising a ticket.

​
Troubleshoot Eloqua email triggers

If none of these apply, raise a support ticket and include: the destination name, the journey and node where the send should have fired, the Email Asset ID you configured, the Eloqua contact ID of an affected customer, and the timestamp at which the customer reached the node.

​
FAQ

No. The email asset is built, edited and approved entirely in Oracle Eloqua. Zeotap only instructs Eloqua to send an asset that already exists, identified by its Email Asset ID. Change the content in Eloqua and the next trigger picks it up — you do not need to touch the journey node unless the asset ID changes.
Eloqua’s Email Deployment API addresses a contact by Eloqua’s own internal numeric ID, which is its primary key for that contact, and will not accept an email address in its place. That ID therefore has to be resolved onto the Zeotap customer profile before the journey runs. If the attribute you map is empty for a customer, no email is triggered for them.
No. The destination holds only the connection to your Eloqua instance and the contact ID mapping. Email ID, Email Name and Name are set on the journey node, so the email a trigger sends is decided per node rather than once per destination.

​
Next steps

Last modified on November 2, 2026