Grant the following IAM roles to the service account that you want to use for the connector:
roles/secretmanager.viewer
roles/secretmanager.secretAccessor
A service account is a special type of Google account intended to represent a non-human
user that needs to authenticate and be authorized to access data in Google APIs.
If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more
information, see
Creating a service account.
If these services or permissions have not been enabled for your project previously, you are prompted to enable them
when configuring the connector.
Configure the connector
A connection is specific to a data source. It
means that if you have many data sources, you must create a separate connection
for each data source. To create a connection, do the following:
In the Cloud console, go to the Integration Connectors > Connections page
and then select or create a Google Cloud project.
Click + Create New to open the Create Connection page.
In the Location section, choose the location for the connection.
Region: Select a location from the drop-down list.
For the list of all the supported regions, see Locations.
Click Next.
In the Connection Details section, complete the following:
Connector: Select Oracle Eloqua from the drop down list of available Connectors.
Connector version: Select the Connector version from the drop down list of available versions.
In the Connection Name field, enter a name for the Connection instance.
Connection names must meet the following criteria:
Connection names can use letters, numbers, or hyphens.
Letters must be lower-case.
Connection names must begin with a letter and end with a letter or number.
Connection names cannot exceed 49 characters.
Optionally, enter a Description for the connection instance.
Optionally, enable Cloud logging,
and then select a log level. By default, the log level is set to Error.
Service Account: Select a service account that has the required roles.
Optionally, configure the Connection node settings:
Minimum number of nodes: Enter the minimum number of connection nodes.
Maximum number of nodes: Enter the maximum number of connection nodes.
A node is a unit (or replica) of a connection that processes transactions.
More nodes are required to process more transactions for a connection and conversely,
fewer nodes are required to process fewer transactions.
To understand how the nodes affect your connector pricing, see
Pricing for connection nodes. If you don't enter any values, by default
the minimum nodes are set to 2 (for better availability) and the maximum nodes are set to 50.
Company: Specify the company's unique identifier. This field is used to authenticate to the Eloqua servers.
Bulk Polling Interval: Specify the time interval between bulk API requests. The default value is 200 ms.
Bulk Query Timeout: Specify the time in minutes to wait for a bulk query response. The default value is 25 minutes.
Data Retention Duration: Specify the time duration in hours to store bulk data on the server. You can specify values from 1 hour to 2 weeks. The default value is 24 hours.
Display Column Name: Specify the display name for columns when using the Oracle Eloqua Bulk API. You can specify an empty string, internal, or statement.
Map Data Cards Case Sensitive Match: Specify whether to use case sensitive match in data card mapping.
Map Data Cards Relationship: Enter a comma-separated list of the relationships between the custom object tables and the entity tables.
Retry Count: Specify the maximum number of times to retry a Bulk API request that fails due to an HTTP 500 status code (Internal Server Error).
Retry Interval: Specify the time interval between attempts to retry a Bulk API request that failed with an HTTP 500 status code (Internal Server Error).
Use Bulk API: Specify whether to use the bulk API to retrieve data.
Optionally, click + Add label to add a label to the Connection in the form of a key/value pair.
Click Next.
In the Destinations section, enter details of the remote host (backend system) you want to connect to.
Destination Type: Select a Destination Type.
To specify the destination hostname or IP address, select Host address and
enter the address in the Host 1 field.
To establish a private connection, select Host Address and add the endpoint attachment created for the SAP Gateway using the HTTPS protocol.
If you want to establish a public connection to your backend systems with additional security, you can
consider configuring static outbound
IP addresses for your connections, and then configure
your firewall rules to allowlist only the specific static IP addresses.
To enter additional destinations, click +ADD DESTINATION.
Click Next.
In the Authentication section, enter the authentication details.
Select an Authentication type and enter the relevant details.
The following authentication types are supported by the Oracle Eloqua connection:
The Oracle Eloqua connector can process a maximum of 12 transactions per second,
per node, and throttles any transactions beyond this limit.
By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.
For information on the limits applicable to Integration Connectors, see Limits.
Use the Oracle Eloqua connection in an integration
After you create the connection, it becomes available in both
Apigee Integration and Application Integration. You can use the connection
in an integration through the Connectors task.
To understand how to create and use the Connectors task in Apigee Integration, see Connectors task.
To understand how to create and use the Connectors task in Application Integration, see Connectors task.
Entity operation examples
This section shows how to perform some of the entity operations in this connector.
Example - List all AccountGroup
In the Configure connector task dialog, click Entities.
Select AccountGroup from the Entity list.
Select the List operation, and then click
Done.
You can perform the List operation on the following entities as well:
Event, User, and Campaign
Example - Get an AccountGroup
In the Configure connector task dialog, click Entities.
Select AccountGroup from the Entity list.
Select the Get operation, and then click
Done.
Set the entity ID to the entity of the AccountGroup. To set the entity ID, in
the Data Mapper section of the Data Mapping, click Open Data Mapping Editor and
then enter 1 in the Input Value field and choose the EntityId as Local variable.
You can perform the Get operation on the following entities as well: Email and User.
Example - Delete an AccountGroup
In the Configure connector task dialog, click Entities.
Select AccountGroup from the Entity list.
Select the Delete operation, and then click
Done.
Set the entity ID to the entity of the AccountGroup. To set the entity ID, in
the Data Mapper section of the Data Mapping, click Open Data Mapping Editor and
then enter 8 in the Input Value field and choose the EntityId as Local variable.
You can perform the Delete operation on the Email entity as well.
Example - Create a Campaign
In the Configure connector task dialog, click Entities.
Select Campaign from the Entity list.
Select the Create operation, and then click Done.
In the Data mapper section of the Task click
OpenDataMapping editor and then enter a value similar to the following in the
field:
Running this example, returns a response similar to the following in the Connector
task's connectorOutputPayload output variable:
{
"ID": 9
}
Example - Create an Event
In the Configure connector task dialog, click Entities.
Select Event from the Entity list.
Select the Create operation, and then click Done.
In the Data mapper section of the Task click
OpenDataMapping editor and then enter a value similar to the following in the
field:
{
"Name": "Marketing Experience GCP2.2",
"Description": "Modern Marketing Experience brings together Modern Marketers from around the globe",
"EmailAddressFieldId": "-2"
}
Running this example, returns a response similar to the following in the Connector
task's connectorOutputPayload output variable:
{
"Id": "16"
}
Example - Update a Campaign
In the Configure connector task dialog, click Entities.
Select Campaign from the Entity list.
Select the Update operation, and then click Done.
Set the entity ID to the entity of the Campaign. To set the EntityID, in
the Data mapper section of the Tasks, click EntityID and
then enter 5 in the given field.
In the Data mapper section of the Task click
OpenDataMapping editor and then enter a value similar to the following in the
field:
{
"Name": "AltostratCamp9",
"BudgetedCost": 100
}
Running this example, returns a response similar to the following in the Connector
task's connectorOutputPayload output variable:
{
"ID": 5
}
Example - Update an Email
In the Configure connector task dialog, click Entities.
Select Email from the Entity list.
Select the Update operation, and then click Done.
Set the entity ID to entity of the Email. To set the EntityID, in
the Data mapper section of the Tasks, click EntityID and
then enter 59 in the given field.
In the Data mapper section of the Task click
OpenDataMapping editor and then enter a value similar to the following in the
field:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-09 UTC."],[],[]]