Skip to main content

Oracle Eloqua

Oracle Eloqua is a B2B marketing automation platform for managing contacts, accounts, campaigns, emails, forms, and landing pages. The Oracle Eloqua connector reads contacts, accounts, campaigns, emails, forms and form submissions, landing pages, segments, contact lists, custom objects, contact activities, and users through the Eloqua REST API, and can create and update contacts, accounts, and custom object records.

Oracle Eloqua icon

Power end-to-end data operations for your Oracle Eloqua API with Nexla. Our bi-directional Oracle Eloqua connector is purpose-built for Oracle Eloqua, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Oracle Eloqua or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Oracle Eloqua workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla connects to the Eloqua REST API with HTTP Basic authentication as an Eloqua user. You need:

  1. An Eloqua user for the integration. Oracle recommends a dedicated integration user. The user must be in the Advanced Users - Marketing security group (or another group with API access), with read access to the assets you plan to read. The List Users template also needs user management rights, and the destination templates need write access to contacts, accounts, or custom objects.

  2. Your company (site) name, username, and password. The company name is the value you enter in the Company field on the Eloqua sign-in page. Eloqua's Basic authentication signs in as Company\Username (the company name, a backslash, and the username); Nexla builds this from two separate credential fields. See Oracle's Basic authentication guide.

  3. Your instance's base URL (pod). Each Eloqua instance runs on a pod, such as https://secure.p01.eloqua.com or https://secure.p03.eloqua.com. To find yours, send a GET request to https://login.eloqua.com/id with the same Basic credentials (for example, open the URL in a browser and sign in with Company\Username and your password), and copy the base value from the urls object in the response. See Oracle's Determining base URLs guide.

Basic authentication must be allowed for the user. If your instance enforces single sign-on only, or restricts API access to an IP allowlist, ask your Eloqua administrator to allow API access for the integration user.

Authenticate​

Credentials required​

HTTP Basic auth with user Company\Username and the user's password, against your instance's pod base URL. Tested with GET /api/REST/2.0/system/user/current.

FieldRequiredSecretDescription
Base URL (pod)YesNoYour instance's base URL, e.g. https://secure.p01.eloqua.com (no trailing slash). Find it as urls.base in the response of GET https://login.eloqua.com/id with these credentials.
Company (Site) NameYesNoThe company name you type on the Eloqua login page (site name). Sent as the part before the backslash in the Basic auth user: Company\Username.
UsernameYesNoEloqua user name (not the email unless that is the login). The user needs the Advanced Users - Marketing (or API) security group to call the REST API.
PasswordYesYesPassword of that Eloqua user. Stored encrypted.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your instance's base URL in the Base URL (pod) field, for example https://secure.p03.eloqua.com, without a trailing slash. The default is https://secure.p01.eloqua.com; change it if your instance is on a different pod.

  4. Enter your company (site) name in the Company (Site) Name field, exactly as you type it on the Eloqua sign-in page.

  5. Enter the Eloqua user name in the Username field. Enter only the user name, without the company name or a backslash.

  6. Enter the user's password in the Password field.

    Nexla signs in as Company\Username, joining the Company (Site) Name and Username fields with a backslash. If the credential test fails, check that the company name matches the sign-in page exactly, that the username field does not already contain the company name, that the base URL is the urls.base value for your instance, and that the user is allowed to use Basic authentication through the API. You can confirm the combined sign-in name by calling https://login.eloqua.com/id with it.

  7. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Nexla tests the credential by reading the signed-in user from your instance (GET /api/REST/2.0/system/user/current), which also confirms that the base URL is correct.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Oracle Eloqua connector tile, then select the credential that will be used to connect to your Eloqua instance, and click Next; or, create a new Oracle Eloqua credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Oracle Eloqua endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.

Templates that say "Results are paged automatically" read 1,000 records per page, up to 10,000 pages. Templates that need an ID, such as a contact, form, or custom object ID, read data for that one object; use the matching list or search template to find the ID. Most templates have a Depth setting that controls how much detail Eloqua returns; lower depth is faster.

Contacts​

List Contacts

Lists every contact in the instance, with ID, email address, name, account, and subscription flags. Set Depth to complete to also return custom field values.

  • Calls GET {base_url}/api/REST/1.0/data/contacts?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default partial): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • For large databases, use Search Contacts to read only the contacts you need.
  • See the Oracle Eloqua API reference for the response fields.

Search Contacts

Lists the contacts that match an Eloqua search expression, such as emailAddress=jane@example.com or C_EmailAddressDomain=example.com.

  • Calls GET {base_url}/api/REST/1.0/data/contacts?search={Search Expression}&depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Search Expression (required): An Eloqua search expression in the form <field><operator><value>, for example emailAddress=jane@example.com or C_EmailAddressDomain=example.com. Use * as a wildcard; a trailing wildcard is fastest. Do not include spaces: the expression is sent in the URL as entered.
  • Depth (required; default partial): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Get Contact

Returns one contact by ID, with all standard and custom fields.

  • Calls GET {base_url}/api/REST/2.0/data/contact/{Contact ID}?depth={Depth}.
  • Contact ID (required): The numeric ID of the contact. Use Search Contacts to find it.
  • Depth (required; default complete): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Get Contact Activities

Lists one contact's activities of one type in a date range: email sends, opens, click-throughs, subscribes, or unsubscribes, form submissions, website visits, or campaign membership.

  • Calls GET {base_url}/api/REST/1.0/data/activities/contact/{Contact ID}?type={Activity Type}&startDate={Start Date}&endDate={End Date}&count=1000.
  • Contact ID (required): The numeric ID of the contact. Use Search Contacts to find it.
  • Activity Type (required; default emailOpen): Which activity to return for the contact. Options: emailOpen, emailSend, emailClickThrough, emailSubscribe, emailUnsubscribe, formSubmit, webVisit, campaignMembership.
  • Start Date (required; default {now-30}): Start of the date range. Nexla sends it to Eloqua as a Unix timestamp in seconds.
  • End Date (required; default {now}): End of the date range. Nexla sends it to Eloqua as a Unix timestamp in seconds.
  • Eloqua returns at most 1,000 activities per request, and this template makes one request. For a contact with more activity, use shorter date ranges.
  • See the Oracle Eloqua API reference for the response fields.

Get Contact's List Memberships

Lists the shared contact lists that a contact belongs to, with each list's ID, name, and counts.

  • Calls GET {base_url}/api/REST/2.0/data/contact/{Contact ID}/membership.
  • Contact ID (required): The numeric ID of the contact. Use Search Contacts to find it.
  • See the Oracle Eloqua API reference for the response fields.

Accounts​

List Accounts

Lists every account (company) in the instance, with address and phone. Set Depth to complete to also return custom field values.

  • Calls GET {base_url}/api/REST/1.0/data/accounts?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default partial): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Search Accounts

Lists the accounts that match an Eloqua search expression, such as name=Acme* or M_City=Boston.

  • Calls GET {base_url}/api/REST/1.0/data/accounts?search={Search Expression}&depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Search Expression (required): An Eloqua search expression in the form <field><operator><value>, for example name=Acme* or M_Country=Canada. Use * as a wildcard; a trailing wildcard is fastest. Do not include spaces: the expression is sent in the URL as entered.
  • Depth (required; default partial): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Get Account

Returns one account (company) by ID, with its fields.

  • Calls GET {base_url}/api/REST/1.0/data/account/{Account ID}?depth={Depth}.
  • Account ID (required): The numeric ID of the account. Use Search Accounts to find it.
  • Depth (required; default complete): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Marketing assets​

List Campaigns

Lists campaigns (multi-step canvases) with name, status, type, start and end dates, and budget.

  • Calls GET {base_url}/api/REST/2.0/assets/campaigns?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

List Emails

Lists email assets with name, subject, sender, status, and folder.

  • Calls GET {base_url}/api/REST/2.0/assets/emails?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

List Forms

Lists forms with ID, name, and HTML name. partial depth adds the form fields, and complete depth adds processing steps.

  • Calls GET {base_url}/api/REST/2.0/assets/forms?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Get Form Submissions

Lists the processed submissions of one form in a date range, with the field values of each submission.

  • Calls GET {base_url}/api/REST/2.0/data/form/{Form ID}?startAt={Start Date}&endAt={End Date}.
  • Results are paged automatically, 1,000 records per page.
  • Form ID (required): The numeric ID of the form. Use List Forms to find it.
  • Start Date (required; default {now-30}): Earliest submission time. Nexla sends it to Eloqua as a Unix timestamp in seconds.
  • End Date (required; default {now}): Latest submission time. Nexla sends it to Eloqua as a Unix timestamp in seconds.
  • See the Oracle Eloqua API reference for the response fields.

List Landing Pages

Lists landing pages with name, relative path, microsite, and status.

  • Calls GET {base_url}/api/REST/2.0/assets/landingPages?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

List Segments

Lists contact segments with name and last calculated count. complete depth adds the segment criteria.

  • Calls GET {base_url}/api/REST/2.0/assets/contact/segments?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

List Contact Lists

Lists shared contact lists with name, member count, and scope.

  • Calls GET {base_url}/api/REST/1.0/assets/contact/lists?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Custom objects​

List Custom Objects

Lists custom object definitions and their fields. Use it to find the custom object IDs that the record templates need.

  • Calls GET {base_url}/api/REST/2.0/assets/customObjects?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default minimal): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

List Custom Object Records

Lists the records (instances) of one custom object, with their field values.

  • Calls GET {base_url}/api/REST/2.0/data/customObject/{Custom Object ID}/instances?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Custom Object ID (required): The numeric ID of the custom object. Use List Custom Objects to find it.
  • Depth (required; default complete): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • See the Oracle Eloqua API reference for the response fields.

Users​

Get Current User

Returns the Eloqua user that this credential signs in as, with ID, login name, email address, and security groups. Use it to check the connection.

List Users

Lists Eloqua users with login name, display name, email address, last login, and default account.

  • Calls GET {base_url}/api/REST/2.0/system/users?depth={Depth}.
  • Results are paged automatically, 1,000 records per page.
  • Depth (required; default partial): How much detail Eloqua returns: minimal (ID, name, and dates; fastest), partial (all properties), or complete (also custom field values; slowest). Options: minimal (id, name, dates; fastest) (minimal), partial (all properties, related ids) (partial), complete (everything incl. field values; slowest) (complete).
  • The credential's user needs rights to view users.
  • See the Oracle Eloqua API reference for the response fields.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Oracle Eloqua data sources can also be manually configured to ingest data from any valid Oracle Eloqua API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Eloqua API URLs start with your instance's base URL (pod), such as https://secure.p03.eloqua.com, followed by /api/REST/1.0/ or /api/REST/2.0/. The credential's Basic authentication is added to every request.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Oracle Eloqua data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Oracle Eloqua destination, and select the Send to Destination option from the menu. Select the Oracle Eloqua connector from the list of available destination connectors, then select the credential that will be used to connect to your Eloqua instance, and click Next; or, create a new Oracle Eloqua credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Oracle Eloqua endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

These templates create or change records in your Eloqua instance. Test them with a single record before sending a full Nexset.

Contacts and accounts​

Create Contact

Creates a contact for each record.

  • Sends POST {base_url}/api/REST/1.0/data/contact.
  • Each record is sent as the JSON request body, one request per record. emailAddress is required; other common fields are firstName, lastName, accountName, and title. Set custom fields with fieldValues, a list of objects with id and value.
  • Eloqua rejects the record if a contact with the same email address already exists. Use Update Contact for existing contacts.
  • See the Oracle Eloqua API reference for the request fields.

Update Contact

Updates an existing contact for each record. The contact ID is read from the record's id field.

  • Sends PUT {base_url}/api/REST/1.0/data/contact/{id}.
  • Each record is sent as the JSON request body, one request per record, to the URL of the contact in its id field.
  • Include emailAddress and every field you want to keep. Eloqua may clear fields that are left out of the request.
  • See the Oracle Eloqua API reference for the request fields.

Create Account

Creates an account (company) for each record.

  • Sends POST {base_url}/api/REST/1.0/data/account.
  • Each record is sent as the JSON request body, one request per record. name is required; other common fields are address1, city, country, and businessPhone. Set custom fields with fieldValues, a list of objects with id and value.
  • See the Oracle Eloqua API reference for the request fields.

Update Account

Updates an existing account (company) for each record. The account ID is read from the record's id field.

  • Sends PUT {base_url}/api/REST/1.0/data/account/{id}.
  • Each record is sent as the JSON request body, one request per record, to the URL of the account in its id field.
  • Include name and every field you want to keep. Eloqua may clear fields that are left out of the request.
  • See the Oracle Eloqua API reference for the request fields.

Custom object records​

Create Custom Object Record

Adds a record to a custom object for each Nexset record.

  • Sends POST {base_url}/api/REST/2.0/data/customObject/{Custom Object ID}/instance.
  • Custom Object ID (required): The numeric ID of the custom object. Use List Custom Objects to find it.
  • Each record is sent as the JSON request body, one request per record. Set the field values with fieldValues, a list of objects with id and value; the field IDs are listed by List Custom Objects. Optionally include contactId or accountId to link the record to a contact or account.
  • See the Oracle Eloqua API reference for the request fields.

Update Custom Object Record

Updates an existing custom object record for each Nexset record. The record ID is read from the record's id field.

  • Sends PUT {base_url}/api/REST/2.0/data/customObject/{Custom Object ID}/instance/{id}.
  • Custom Object ID (required): The numeric ID of the custom object. Use List Custom Objects to find it.
  • Each record is sent as the JSON request body, one request per record, with the field values in fieldValues, a list of objects with id and value.
  • See the Oracle Eloqua API reference for the request fields.

Manual configuration​

Oracle Eloqua destinations can also be manually configured to send data to any valid Oracle Eloqua API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Oracle Eloqua endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Oracle Eloqua endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.