Eloqua Destination

Segment makes it easy to send your data to Eloqua (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Eloqua in the format they understand. Learn more about how to use Eloqua with Segment.


Page view tracking is achieved via an integration with the Eloqua Asynchronous Visitor Tracking Script.

Page tracking with Eloqua is, by default, achieved with a third party cookie. This cookie is generated upon successful completion of an Eloqua form. Once a user submits one of these forms, Segment .page() events will start populating as Website Visits in their Eloqua contact profile.


Segment integrates with Eloqua’s REST API to provide the ability to create or update contacts in Eloqua following events that do not use an Eloqua form.

Segment supports populating the following Eloqua contact fields:

  • Email
  • First Name
  • Last Name
  • Address 1
  • City
  • Country
  • Title

Please adhere to our spec to ensure proper mapping of these fields from Segment .identify() traits: https://segment.com/docs/spec/identify/#traits.


Segment .track() events trigger the creation of Eloqua Custom Object records and associate them with a specific contact.

To get started, please provide a mapping in your destination settings specifying the Segment event names with the corresponding Custom Object you would like to associate it with in Eloqua.

Segment will also map the properties of .track() events with Custom Object fields of the same name. Our integration does a case and formatting insensitive match so that if you have a field called Account Type in Eloqua and a property called accountType in your Segment event, the mapping will get handled.

User Email

By default, Eloqua uses email address as a contact ID. Therefore, in order to successfully associate a contact with a Custom Object, the Segment .track() event needs to include the user’s email as a property.

Because email is usually not a property of a typical .track() event, the destination will look for it as an integration specific property. Here is an example using our node.js library:

analytics.track('Account Created', {
  type: 'Free Trial'
}, {
  integrations: {
    Eloqua: {
      email: 'billbrasky@segment.com'


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Company Name

Enter your login company name

Map Track Events to Custom Objects

Please input the Segment event names on the left and their corresponding Eloqua Custom Object names on the right. This mapping is required for all events you would like in Eloqua as Custom Objects


Enter your login passord

Site ID

Enter your Site ID


Enter your login username

If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!