Skip to main content

​
Overview

Oracle Eloqua is a B2B marketing automation platform that enables marketers to create, manage, and execute sophisticated cross-channel campaigns including email, display advertising, and landing pages. It provides advanced tools for lead management, campaign orchestration, and real-time email triggering, helping marketers deliver personalised experiences at scale. The platform offers an Email Deployment API to trigger individual email sends to specific contacts in real time, making it well suited for event-driven, transactional, and journey-based communication. Integrated with Zeotap, it helps marketers deliver contextually relevant email experiences driven by unified first-party customer data.

​
Available Actions and Supported Features

The following table lists the available action types for the integration and the supported features for each action type:

​
Prerequisites

Before pushing data to Eloqua, ensure that you have completed the setup as mentioned below.
  • Create an Eloqua account with REST API access enabled and obtain your Company Name, Username, and Password.
  • Identify the POD your Eloqua instance is hosted on (e.g., p03) from the login URL, or use GET https://login.eloqua.com/id to resolve it programmatically.
  • Pre-build the email asset you want to trigger inside Eloqua and note down its Email Asset ID.
  • Ensure the Eloqua internal contactId is available on the Zeotap customer profile.

​
Create a Destination for Eloqua

Once you have obtained the prerequisites mentioned above, perform the following steps to create a destination for Eloqua:
1

Open the Destinations module

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

Click + Create Destination

On the Destinations landing page, click + Create Destination in the top right.
Destinations module listing existing destinations with the Create Destination button highlighted.

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

3

Search for Eloqua in the catalogue

Under All Destinations, search for Eloqua and select the Eloqua card.
Destination catalogue showing the search field for finding destinations.

Figure 2 — Destination catalogue. Search for Eloqua to surface the destination card.

4

Enter the connection details

On the Enter Destination Details screen, fill in the required fields:
  • Destination Name — a descriptive label (e.g., Eloqua — Production).
  • Username — the Eloqua username, prefixed with your Company Name separated by a backslash.
  • Password — the password for your Eloqua account.
  • Region — select the POD your Eloqua instance is hosted on.
The Username field must be entered as your Company Name and Username separated by a single backslash. For example, if your company is Acme and your username is jdoe, enter:
Eloqua destination details form with the Destination Name, Username, Password, and Region fields.

Figure 3 — Eloqua destination details form (Destination Name, Username, Password, and Region).

Review the values you have entered and click Next to proceed to mapping.
5

Choose the action and map the Contact ID

On the Action and Mapping screen:
  1. Under Choose your Action, select Trigger Emails in Eloqua — this is the only action available for this destination.
  2. Under Map the Fields, the Contact Id destination field is pre-populated. Against it, select the Zeotap profile attribute that holds the Eloqua internal contactId.
Action and Mapping screen with Trigger Emails in Eloqua selected and the Contact Id destination field shown.

Figure 4 — Action set to Trigger Emails in Eloqua, with the Contact Id destination field ready to map.

6

Create the destination

Once the mapping is complete, click Save Mapping, then Create Destination. The created destination now appears in the Journeys application and can be linked from a Journey node.

​
Activate the Destination on Journeys

After creating the destination, link it inside the Send to Destinations node of a Journey workflow.
1

Add a Send to Destinations action

In the Journey workflow, click + at the point where the email should fire and choose Send to Destinations.
Journey Choose an action menu showing options including Send to Destinations.

Figure 5 — Choose an action menu inside the Journey workflow with Send to Destinations highlighted.

2

Select the Eloqua destination

Use the search field to locate the Eloqua destination you just created, then select its card.
Send to Destinations search panel showing destination cards with IDs.

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

3

Confirm destination details and configure the email send

On the Destination Details tab, the connection fields populate automatically from the values you saved when creating the destination. Fill in the journey-specific email fields:
  • Email ID — the Email Asset ID of the pre-built email in Eloqua. This is the unique numeric identifier of the email template you want to trigger; you can find it inside your Eloqua instance.
  • Email Name — the email asset name as it appears in Eloqua. This is used for reference only and does not affect the delivery of the email.
  • Name — a label for this deployment instance. This is an internal tracking identifier inside Eloqua and does not impact the email content or delivery.
Destination Settings panel for Eloqua inside a journey showing the Email ID, Email Name, and Name fields.

Figure 7 — Eloqua destination settings inside the journey node — Email ID, Email Name, and Name fields.

4

Save the destination

Click Save Destination. The Eloqua destination is now attached to the Journey node and ready to fire emails on the journey’s schedule.
Send to Destinations node showing the attached Eloqua destination card and mapping label.

Figure 8 — Journey node with the attached Eloqua destination card and the Trigger Emails in Eloqua mapping.

Last modified on May 12, 2026