You can configure connectors to import visitor information from Oracle Eloqua marketing software into Personalization.
To configure a new Eloqua connector, complete the following steps:
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 endpointaccessKey
: The Eloqua access keysecretKey
: The Eloqua secret keyaccountID
: The Personalization account IDcustomerId
: Supplied by AcquiaawsConfig
sectionregion
: Supplied by AcquiadynamoDBTablePrefix
: Supplied by AcquiadynamoDBEndpoint
: Supplied by AcquiaeloquaConfig
section:siteName
: The company name that the Eloqua user belongs tousername
: The user’s Eloqua usernamepassword
: The user’s Eloqua passwordstartPullDate
: The first date data can be imported from
Eloqua startPullDate
for the
initial import.bucketRegion
: Supplied by AcquiabucketName
: Supplied by AcquiapersonFieldMapping
: Sends specific customer data to Eloqua —
Learn moreeventFieldMapping
: Sends specific activity data to Eloqua —
Learn moreYou 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.
In Eloqua, a lead (a visitor Eloqua is tracking) performs activities
which are captured by Eloqua, such as opening an email or signing up for a
mailing list. The Eloqua connector allows you to map the activities to
events in Personalization, along with corresponding attributes (such as
the associated CampaignID
).
In Personalization, activities are prefixed with Eloqua_{activityname}
,
where {activityname}
is the name of an activity tracked in Eloqua. You must
manually create these activities in Personalization as events. For more
information, see Creating and managing events.
As an example, activity mapping in the connector configuration file to map the
Subscribe
activity and several associated fields into Personalization event
fields can display like the following:
"eventFieldMapping":{
"Subscribe": {
"eventName": "Subscribe",
"attributesMappings": {
"CampaignId" : "event_udf5",
"ExternalId" : "event_udf6",
"AssetId" : "event_udf7"
}
}
}
For a full list of mappable activities, see Oracle’s documentation regarding activity fields.
Adding contact mappings to your Eloqua connector enables you to import data related to visitors’ contact information and create segments from that information. When you have mapped a lead to a field, it can be imported into Personalization and the added data can be used in segments.
As an example, adding contact mapping in the connector configuration file to
map the C_Industry1
field from Eloqua can display like the following:
"personFieldMapping":{
"C_Industry1": {
"isIdentity": false,
"eloquaFieldStatement": "{{Contact.Field(C_Industry1)}}",
"mapTo": "person_udf5"
},
}
For a full list of mappable contact fields, see Oracle’s documentation regarding contact fields.
After creating and enabling your connector, the next step is to use the imported Eloqua activity and lead data to create segments.
To view and manage your available connectors, complete the following steps:
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:
For your connectors to start importing Eloqua information into Personalization, they must be enabled.
To enable a connector, set the switch to On for that connector. To disable the connector, set the switch to Off
To permanently remove a connector or its mapping information, complete the appropriate steps depending on your needs:
eventFieldMapping
section.personFieldMapping
section.