Configuring the Eloqua connector¶

Creating an Eloqua connector¶

To configure a new Eloqua connector, complete the following steps:

1. Sign in to the Personalization interface, and then click the Configure tab.
2. Click the Connectors link.
3. In the Select a connector type list, click Eloqua as the connector type that you want to configure.
4. Click Add connector.
   Personalization displays the Eloqua connector configuration settings in JSON format.
5. In the Eloqua connector configuration section, enter values in the following fields for the new connector:
   • Initial section
     • name: A descriptive name for your connector based on the type of information it will import (for example, Eloqua email information connector)
     • host: IP address of the Eloqua endpoint
     • accessKey: The Eloqua access key
     • secretKey: The Eloqua secret key
     • accountID: The Personalization account ID
     • customerId: Supplied by Acquia
   • awsConfig section
     • region: Supplied by Acquia
     • dynamoDBTablePrefix: Supplied by Acquia
     • dynamoDBEndpoint: Supplied by Acquia
   • eloquaConfig section:
     • siteName: The company name that the Eloqua user belongs to
     • username: The user’s Eloqua username
     • password: The user’s Eloqua password
     • startPullDate: The first date data can be imported from Eloqua
       If Personalization doesn’t have a date set already, the connector uses this date as a starting point. If a new activity is added to the mappings, it will use the startPullDate for the initial import.
     • bucketRegion: Supplied by Acquia
     • bucketName: Supplied by Acquia
     • personFieldMapping: Sends specific customer data to Eloqua — Learn more
     • eventFieldMapping: Sends specific activity data to Eloqua — Learn more
6. Click Save configuration.

Adding mappings to your connector¶

You can configure an Eloqua connector to import data by adding mappings. The mapping type determines the mapping configurations. You can configure the Eloqua connector to import data by adding mappings to it. A text file displayed on the connector’s configuration page defines all mappings.

Fields associated with an activity can be mapped to fields in the Person, Touch, or Event tables. For example, you can map the Eloqua activity EmailClickthrough, and it reflects in Personalization as the event Eloqua_EmailClickthrough. You would then map a field associated with the activity, such as CampaignID to event_udf5 in the Event table.

In the following examples, eloquaFieldStatement matches an Eloqua-supplied field, and the mapTo applies to a field in Personalization.

"eventFieldMapping":{
   "Subscribe": {
       "eventName": "Subscribe",
       "attributesMappings": {
           "CampaignId" : "event_udf5",
           "ExternalId" : "event_udf6",
           "AssetId" : "event_udf7"
       }
   }
  }

"personFieldMapping":{
"C_Industry1": {
"isIdentity": false,
"eloquaFieldStatement": "{{Contact.Field(C_Industry1)}}",
"mapTo": "person_udf5"
},
        }

Creating segments with Eloqua activity and lead information¶

After creating and enabling your connector, the next step is to use the imported Eloqua activity and lead data to create segments.

Managing your connectors¶

To view and manage your available connectors, complete the following steps:

1. Sign in to the Personalization interface, and then click the Admin tab.
2. Click the Manage configuration data link.
3. Click the Connectors link.

Personalization displays a list of the available connectors for your environment. The Connectors page has options for the following available actions, including enabling/disabling, deleting, or editing connectors: