Step 3: [Import Data] Map fields and set up matching in the CDP

Context

Once you have created a Eloqua connection you can now start mapping your fields to the CDP. 

Prerequisite: 

• Step 1: [Import Data] Create a Eloqua Data Import Integration User
• Step 2: [Import Data] Create a Eloqua Data Import Connection
• You must be using the new automated data import workflow. If you are not using the new automated data import workflow, you should reach out to your customer success manager to integrate Eloqua with Rev.Up for data import. 
• Review how D&B approaches matches leads to accounts 

Step 1: Add a data source to the Eloqua connection.

Currently the automated data import feature only supports mapping Leads. Activities are supported, but require you to work with our support team. 

 

Step 2: Map fields 

For each entity from Eloqua (Leads and Activities) we have pre-mapped some common standard fields. You can click on the Edit Mapping button to add or remove field mappings. Fields that are not mapped will not be imported.

 

Step 3: Add additional fields using the edit mapping wizard.

To map fields from Eloqua to the CDP, simply drag and drop fields from the right side of the screen to the middle of the screen. You can also use the dropdown in the middle of the screen to choose which field from Eloqua you want to map to the CDP. 

 

The goal of the CDP is to unify customer and prospect data. When you add your fields from Eloqua to the CDP, there are few things to keep in mind: 

• You should map your Eloqua fields to the field in the CDP that most closely matches the meaning of the Eloqua field. You can add a Eloqua field to an existing attribute or create a new attributes. 
• You can map a field from Eloqua to more than one field in the CDP. 
• You can map fields from different connections to the same field in the CDP. This is how you can prevent the duplication of attributes that have the same meaning. An example is Company Name and Account Name may be called different names in different connections, but have the same meaning. 

 

Step 4: Matching Eloqua records within the CDP 

You can use this section to configure how you want your records to match to the CDP. If you are not sure of how you want your records to match to the CDP, you can skip this section and come back later. 

 

For additional information on creating these setting, check our our article that covers match and merge.

 

Unique Record ID: By default we will use the unique id of the record in Eloqua. This ID will be used to deduplicate your records that come from Eloqua. If you use the default setting it means that we will have the same view of your data that Eloqua does where each record is represented by the standard unique id in Eloqua and we will not try and merge records together based on other information from Salesforce.

 

Matching your records to the CDP: When it comes to matching your records to the CDP there are two methods that are used. 

D&B Identity Resolution: By default we will use all the fields that can be used by D&B matching. You can deselect a field to be used. 

ID Matching (deterministic match): If you have map an ID field from multiple data sources to the same CDP attribute, we will assume that you want to use this field to match IDs between the data sources.

 

Lead to Account Matching:

Not all contacts from Eloqua, will have an ID relationship with an account record that exists in the CDP. Leads will either be matched to an existing account in the CDP or will match to the D&B Data Cloud and an account record will be created.

By default we will use as much information as is available. You can change this setting by updated which fields are used for identity resolution on the settings page. 

Each time a record is synced to the CDP, it will go through the match process and paired with an account. Which account a lead matches to can change over time if the information used for match changes. 

 

 

 

Step 5: Give your data source a name