Integrating with Eloqua for Universal Consent & Preference Management

You can establish a connection between Eloqua and OneTrust's Universal Consent & Preference Management in order to properly maintain consent records within Eloqua. This allows you to leverage your marketing automation tool in a way that is respectful of individuals’ preferences by keeping consent accurate and up-to-date.

To create an Eloqua Integration using Native Integrations

You can set up a connection with Eloqua directly in the Universal Consent & Preference Management module using Native Integrations. Native integrations provide an out-of-the-box method to authenticate into third parties and offer a simplified configuration process by seeding Universal Consent & Preference Management data to easily transfer the data back and forth.

  1. On the Universal Consent & Preference Management menu, select Interfaces > Native Integrations. The Integrations screen appears.

  2. Click the Add New button. The Create New Integration modal appears.


  3. Enter a name and description for the integration. Then click the Create button. The Integration Details screen appears.

  4. Click the Add Task button. The Add Task pane appears.


  5. Select the Eloqua system to populate a list of available template connections. Then select a connection using the radio button next to one of the connection names to start the connection wizard. Once selected, click the Next button.

    The following connections are available for Eloqua:

    Connection Name

    Description

    Consent: Wizard Delete Eloqua contact on DS profile delete

    Select this connection to delete Eloqua contacts when a data subject profile is deleted in OneTrust.

    Consent: Wizard Update Eloqua Contact Subscriptions on DS profile update

    Select this connection to update Eloqua Contact Subscriptions when a data subject profile is updated in OneTrust.

    Eloqua: Wizard Update Eloqua Consent on DS consent Update

    Select this connection to update Eloqua consent when a data subject's consent is updated in OneTrust.
  6. On the Workflow Wizard, enter a name for the connection and enter a valid email address. Then, either create a new credential or select an existing credential from the available list. Click the Test button to verify that the credentials are valid. If valid, a green check mark with a Connected message will appear. Click the Next button when ready.
    Note:

    For more information, see Configuring Integration Credentials.



  7. In the Configure Trigger step, select a value associated with a Collection Point from the Select Value dropdown menu.

    1. Configure the action with parameters, operators, and values to produce the necessary logic. Use the ANY or ALL condition setting within the condition to further customize the sequence criteria.

    2. Click the Add Condition button to add another condition setting within the condition to further customize the sequence criteria.

    3. Click the Add icon to add additional conditions to the initial condition, which is subject to the ANY or ALL selection. Click the Remove icon button to remove the additional condition.

    4. Click the Next button when ready.



  8. In the Mapping step, select an option from the Collection Point Settings dropdown menu, then select a OneTrust Field and an Eloqua Field to map to. Click the Next button when ready.


  9. In the Integration Summary step, you can review the workflow mapping. Click the Add button when ready.


To create an Eloqua Integration using Integrations

Privacy Information

Given the way the current integration works, if you choose to establish a connection between Eloqua and OneTrust, there will be identifiers such as an email address that need to be shared and transferred between the OneTrust and Eloqua servers. The identifiers synced between OneTrust and Eloqua are related to a customers’ end users. This only happens when you select the consent updated workflow.                

All of the personal information transferred is rendered in the HTTP body, with the exception of the end users' email addresses which are part of the resource path. Both the HTTP body and resource path are encrypted in transit.

There are, however, security concerns associated with such a transfer because the resource path (which contains end users’ email addresses) may be logged in Eloqua's servers (e.g., for monitoring purposes) which means that personal information could potentially reside in log entries at rest. An example of how this may look is as follows: 

  • https://{eloqua-host}/services/data/v43.0/sobjects/contact/Email/jdoe@onetrust.com

The risk of exposing email addresses is that they may be seen by intelligence agencies, retrieved by malicious actors, and otherwise misused.  This is a risk that cannot currently be avoided and OneTrust and Eloqua will work to mitigate this going forward.

The basis on which OneTrust is sharing these identifiers with Eloqua is to give effect to the contracts we have in place with our customers who choose to establish a connection between OneTrust and Eloqua. Customers must be aware that such transfer of data comes with risks as further detailed above. Please ensure that you understand and have discussed the above risks with your legal, privacy and security teams before integration.

Please reach out to OneTrust Support with any further questions.