Setting Up a Source Integration to Eloqua

Overview

In this article, we will be outlining how to add and configure an Eloqua integration to a Source within the Integrate Data Acceleration platform. The Integration tab in the Source builder allows you to set up your integration unique to each individual Source to determine how data is passed into your Eloqua fields and leads are routed when received. 

Please Note: Setting up your Integrations tab can, and should, be done first on the Campaign level to act as a 'template' or 'stamp' when creating Sources so only small edits are needed to adjust Source specifics. The integration set up process is the same on either the Campaign or Source level so, for the purpose of this guide, we'll be referring to Source level integrations.

This article includes these sections:

• Adding Your Eloqua Integration
  • Option 1: Create a NEW Source Integration
  • Option 2: Load From Existing
• Configuring Your Eloqua Integration
  • Profile Settings
  • Field Mapping
  • Required Eloqua Fields (elqFields)
  • Finalize & Save
• Source Integration Updates

Before You Begin

• Connect your Eloqua instance to your Data Acceleration Platform
• Locate your values for these fields that were collected previously when completing the above step:
  • elqSiteID
  • elqFormName
  • elqCustomerGUID
  • elqCookieWrite
• It is a best practice to finalize the set-up of your Source Fields tab before adding a Source integration

Please Note: Once your integration is created, changes made to the Fields tab (including changes to the fields themselves, field names, or associated lists) will not automatically reflect, but can be manually updated.

Adding Your Eloqua Integration

Within your Data Acceleration Platform Source, navigate to the Integrations tab, and select the Add Integration button.

Adding an integration to your Source (or Campaign) will pull in the credentials added when you connected your Eloqua instance within the Integration Hub. Now, to configure the delivery of data from your Source into your Eloqua fields, you have two options:

• Option 1: Create a NEW Source Integration – Start from scratch! This will essentially create the shell of an integration with the fields currently on the fields tab. You can then map to your desired Eloqua fields and add any additional details as needed.
  
  
  • Helpful Hint: This option is most helpful when…
    • You or your team are new to the Data Acceleration Platform
    • You haven’t built any Sources with a similar set up
    • You are using very few or unique fields within this Source (e.g. Social or Webinar Sources have fewer, more specific fields)

• Option 2: Load From Existing – Start from something similar! This will copy an existing integration from a Source (or Campaign) as an exact copy. Once loaded, changes can be made to match this integration’s set up details to this new Source.
  
  
  • Helpful Hint: This option is most helpful when…
    • You already have an existing integration that used similar fields and set up details (e.g. existing builds from the same team, region, program)
    • You are creating multiples Source that use the same social / webinar form fields
    • You have complex routing rules that you’d like to copy and then manually ensure your Source fields and details match

Decide which option works best for your build. Instructions on both options are outlined below.

Option 1: Create a NEW Source Integration

Within the Add Integration pop-up modal, select your Eloqua integration from the available list.

This will load your new integration shell which you can then open to map your Eloqua fields, list mappers, routing details, etc.

Proceed to the Configuring Your Eloqua Integration section below for more details.

Option 2: Load From Existing

Within the Add Integration pop-up modal, select Load From Existing in the top right-hand corner.

You will then be presented with a list of the existing Campaign template integrations to choose from. If you wish to switch to view your Source integrations, use the Showing Campaigns button and select Source from the dropdown.

Locate your desired Source (or Campaign) integration, fill in the bubble on the left and select your integration name from the dropdown. Then click Load Integration in the top right-hand corner.

This will load a copy of your existing integration which you can then adjust according to your Source specifics. Proceed to the Configuring Your Eloqua Integration section below for more details.

Configuring Your Eloqua Integration

To open your integration, hover over the Eloqua (Outbound Form) tile and click the gear icon that appears.

Move through the sections below to configure your integration according to the needs of your Source. Be detailed and thorough in your set up and always test before allowing live lead flow.

Profile Settings

This section displays your credentials added when you connected your Eloqua instance within the Integration Hub. You can update the Name of your integration but will need to revisit the Integration Hub to alter any other credentials.

Field Mapping

One of the most important pieces of your integration, this section determines where your Source will send its data to in your Eloqua fields. Click the dropdown arrow to expand and view this section.

The Field column represents the Integrate Source fields that have data coming in from the Integrate channel in use (e.g. Content Synd comes from media partners, Social comes from your social form). The name displayed corresponds to the ‘Field Name’ section on the Fields tab.

The Output column represents the Eloqua field you wish to send that field data into. These are the Eloqua HTML field names added to the Schema section when you connected your Eloqua instance.

To map your fields, work your way down the page making the corresponding Field and Output selections until each field is represented.

If you do not wish to send a collected field to Eloqua or need to delete a field line, you may use the trashcan icon in line on the far right.

Helpful Hint: Additions to your Eloqua field list can be made within your Integration Hub Eloqua (Outbound Form) tile under the Settings > Schema section.

Please Note:

• If you loaded from an existing integration, be sure each Field selected properly matches the Field Names in use on the Fields tab.
• If a Field Name is altered on the Fields tab after an integration has been set up, please reselect the new Field Name from the dropdown and save.

Additional data configuration options are available using these columns:

• Custom – This column opens a text box to allow you to add additional details like static text values, available token data, or advanced coding (liquid markup) to your outbound lead data. Some common examples are illustrated below, but this can be used in many customizable ways so visit our Post Out Enhancements section for more details.

To open this text box, select Custom Field from the last option in the Field column dropdown list. There are many uses for these custom fields including the passing of your Eloqua values into the four required Eloqua fields (elqFields).

For example, the below is passing a few key points into the Comments field using hard coded text and two available tokens.

This next example is passing the Integrate Lead ID into an Eloqua field created to collect and store that value within their Eloqua instance. This is a recommended best practice!

• List Name – This column pulls directly from the Fields tab to show you the list that is being used (if any) to standardize inbound data on the corresponding field.

Please Note: If the associated list changes after the integration is set up, you can update the list shown by reselecting the field name in the Field column.

• Map – This is where you would select the name of the list mapper you wish to apply (if any) to map to alternative list values before sending data into the specified Eloqua field. Visit our Lists & Mappers section, to learn more about lists and mapping values.

The example below shows a field using a list to collect country data using specific values within the ‘Country’ picklist, but then maps to ‘Elq Country Codes’ before sending that data outbound.

Required Eloqua Fields (elqFields)

Every Eloqua Source integration must include these four required elqFields in order for the leads to be properly configured and routed into your Eloqua form.

• elqSiteID
• elqFormName
• elqCustomerGUID
• elqCookieWrite

These values should have been collected when you initially connected your Eloqua instance to your Data Acceleration Platform. Locate those saved values, or work with your Marketing Ops team to find them now within Eloqua and confirm whether you're using one or multiple forms.

Navigate to your Source integration's Field Mapping section and follow the steps to add a Custom field and it's corresponding value for each elqField. Below is an example of what this could look like.

Helpful Hint: Typically, the field elqCustomerGUID is left blank (but must still be included) and the value for elqCookieWrite is 0.

Finalize & Save

Once your integration set up is complete and all fields are mapped, click Save in the top right-hand corner to lock in your changes.

Please Note: If rows are left unmapped (blank) in either the Field or Output columns, your integration will not work as intended.

For instructions on testing your integration, see our article Eloqua Integration Testing and Lead Management. It is important to be thorough when finalizing and testing your Integration, so we recommend working closely with your Marketing Ops team.

Source Integration Updates

Occasionally, updates to your Source integration may be needed. We’ve outlined some example scenarios below. If you need additional assistance troubleshooting, please contact Integrate Support.