Oracle Eloqua

The Oracle Eloqua connector lets you perform read, insert, update, and delete operations on Oracle Eloqua data.

Supported Versions

The following is the minimum supported version for this connector: Oracle Eloqua 10-24C (Standard).

Before you begin

Before using the Oracle Eloqua connector, do the following tasks:

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.

    Go to the Connections page

  • Click + Create New to open the Create Connection page.
  • In the Location section, choose the location for the connection.
    1. Region: Select a location from the drop-down list.

      For the list of all the supported regions, see Locations.

    2. 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:

  • 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:

    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.
    1. 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.

    2. Click Next.
  • In the Authentication section, enter the authentication details.
    1. Select an Authentication type and enter the relevant details.

      The following authentication types are supported by the Oracle Eloqua connection:

      • User Password
      • OAuth 2.0 Authorization code/li>
    2. To understand how to configure these authentication types, see Configure authentication.

    3. Click Next.
  • Review: Review your connection and authentication details.
  • Click Create.
  • Configure authentication

    Enter the details based on the authentication you want to use.

    Connection configuration samples

    This section lists the sample values for the various fields that you configure when creating the connection.

    Username and password connection type

    Field name Details Location europe-west1 Connector Oracle Eloqua Connector version 1 Connection Name oracle-eloqua-googlecloud Service Account SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com Minimum number of nodes 2 Maximum number of nodes 50 Company AltostratLtd Username USERNAME Password PASSWORD Secret Version 1

    OAuth 2.0 connection type

    Field name Details Location europe-west1 Connector Oracle Eloqua Connector version 1 Connection Name oracle-eloqua-googlecloud-oauth Description oracle-eloqua-googlecloud-oauth Service Account SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com Minimum number of nodes 2 Maximum number of nodes 50 Company AltostratLtd Client ID CLIENT_ID Scopes full Client Secret CLIENT_SECRET Secret Version 4

    System limitations

    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.

    Entity operation examples

    This section shows how to perform some of the entity operations in this connector.

    Example - List all AccountGroup

    1. In the Configure connector task dialog, click Entities.
    2. Select AccountGroup from the Entity list.
    3. 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

    1. In the Configure connector task dialog, click Entities.
    2. Select AccountGroup from the Entity list.
    3. Select the Get operation, and then click Done.
    4. 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

    1. In the Configure connector task dialog, click Entities.
    2. Select AccountGroup from the Entity list.
    3. Select the Delete operation, and then click Done.
    4. 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

    1. In the Configure connector task dialog, click Entities.
    2. Select Campaign from the Entity list.
    3. Select the Create operation, and then click Done.
    4. In the Data mapper section of the Task click OpenDataMapping editor and then enter a value similar to the following in the field:
      {
        "Name": "AltostratCampaign1.11",
        "BudgetedCost": 100000
      }

      Running this example, returns a response similar to the following in the Connector task's connectorOutputPayload output variable:

      {
        "ID": 9
      }
      

    Example - Create an Event

    1. In the Configure connector task dialog, click Entities.
    2. Select Event from the Entity list.
    3. Select the Create operation, and then click Done.
    4. 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

    1. In the Configure connector task dialog, click Entities.
    2. Select Campaign from the Entity list.
    3. Select the Update operation, and then click Done.
    4. 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.
    5. 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
      }
      
    6. Running this example, returns a response similar to the following in the Connector task's connectorOutputPayload output variable:

      {
        "ID": 5
      }
      

    Example - Update an Email

    1. In the Configure connector task dialog, click Entities.
    2. Select Email from the Entity list.
    3. Select the Update operation, and then click Done.
    4. 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.
    5. In the Data mapper section of the Task click OpenDataMapping editor and then enter a value similar to the following in the field:
      {
        "Name": "My Googlecloud email updated",
        "EmailGroupId": 1,
        "HtmlContent_Type": "RawHtmlContent",
        "IsPlainTextEditable": false,
        "IsTracked": false,
        "PlainText": "\r\n",
        "BouncebackEmail": "AltostratLtd@s119222.m.en25.com",
        "ReplyToEmail": "newclient@en25.com",
        "ReplyToName": "AltostratLtd",
        "SenderEmail": "newclient@en25.com",
        "SenderName": "AltostratLtd",
        "SenderPlainTextOnly": null,
        "Subject": "New subject line",
        "Description": null,
        "FolderId": 42,
        "EmailHeaderId": 1,
        "EmailFooterId": 1,
        "Permissions": "Retrieve,SetSecurity,Delete,Update,Activate",
        "AccessedAt": null,
        "CurrentStatus": "Draft",
        "Depth": "complete"
      }
      
    6. Running this example, returns a response similar to the following in the Connector task's connectorOutputPayload output variable:

      {
        "ID": 59
      }
      

    Get help from the Google Cloud community

    You can post your questions and discuss this connector in the Google Cloud community at Cloud Forums.

    What's next