Skip to main content
Sign in

Integration Field Mapping

tseitz
  • Updated

Relevant to: Demand Acceleration Platform | Content Syndication | Webinar Integrations | Social Integrations

This article explains how integration field mapping is implemented in the Integrations Tab. The process of field mapping is the same for each integration type.

For additional information relating to field mapping with your specific Marketing Automation or CRM system, see the relevant article in Post-outs section:

Setting up an Integration to Marketo Setting up an Integration to Salesforce

Setting up an Integration to Eloqua
Setting up an Integration to Pardot [coming soon] Using Outbound Forms - Setting up an Integration to HubSpot [coming soon] Using Outbound Forms

 

 

Field mapping columns

This table summarizes the columns that you will see in the field mapping interface:

Column Description
Field

The values here represent the Campaign/Source fields in the Demand Acceleration Platform, which have data incoming from a particular channel.

  • The name displayed here corresponds to the Field Name section on the Fields tab.
  • Select Custom Field to add additional details to your outbound lead data. See Custom for more information.
Output

The values here represent the integrated Marketing Automation or CRM field where data will be sent.

  • These are the field names added to the Schema section when you connected your Marketing Automation or CRM system.
Custom

The additional details added to the Custom column (eg. static text values, available token data or advanced coding / liquid markup) will be sent with your outbound lead data.

  • The corresponding text box will become available when Custom Field is selected in the Field column.
  • See Adding Custom Fields for more information.
List Name

The values here are pulled directly from the Fields tab to show any lists that are being used to standardize inbound data on the corresponding field.
Map

Select the name of the list mapper to send alternative list values into the specified field.

 

How to map your integration fields

For each field row, select the corresponding Field and Output values using the drop-down menus. Work methodically down the page until all field rows are appropriately mapped. 

If rows are left unmapped (blank) in either the Field or Output columns, you will receive an error.

See additional sections for details on adding and removing rows or using custom configurations as needed.

dap-buildbasics-integrationfieldmapping-01.png

 

For example:

Field
(Campaign/Source field)		 posts to

Output
(your integrated Marketing Automation or CRM system field)
first_name posts to

firstName
last_name posts to

lastName
email posts to

email

If you can't find a particular field in the Output list, you can add it in the Integrations Hub.
 Navigate to the integrated system tile and click on Settings. Add the desired field in the Schema section.

An important note on field names.
  • If you loaded the integration from an existing Campaign/Source, double check that the selected Field (in the drop-down) matches the current Field Names on the Fields tab.
  • If a Field Name is updated on the Fields tab after an integration has been set up, you will need to manually reselect the new name from the dropdown in the Field column on the Integrations tab. 

 

Adding new rows

Select the Click to add a field mapping row... option to add any additional fields and include other data values that have not been automatically added (such as system data, static routing values or fields that need a custom set-up). 

dap-postouts-settingupeloqua-16.png

 

Removing rows

If you do not wish to send a field to your Marketing Automation or CRM system, you can use the trashcan icon to delete the field row.

dap-postouts-settingupeloqua-14.png

 

Working with fields that utilize lists and mappers

If a field uses a picklist, the integration mapping field row will automatically display the relevant list in the List Name column.

You can then assign a mapper to the field in the Map column. See more in the Lists & Mappers section.

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. 

 

Mapped list example

  • The list field asset_title is collecting the title of content assets from values on a picklist FY19Q4 Assets.
  • The asset title values on the FY19Q4 Assets list will be translated into the corresponding asset code using the mapper Asset name > codes.
  • The asset code value from the Asset name > codes mapper will be sent into the Marketo field assetDownloaded.

dap-postouts-settingupeloqua-22.png

 

Adding Custom Fields

1. Add a new field row by selecting Click to add a field mapping row....

dap-postouts-settingupeloqua-16.png

 

2. Under the Field column, select Custom Field. 

dap-buildbasics-integrationfieldmapping-02.png

 

This will open the text box display in the Custom column.

dap-buildbasics-integrationfieldmapping-05.png

 

3. In the Output column, select the corresponding system field.

dap-buildbasics-integrationfieldmapping-03.png

 

4. In the Custom column, add your custom field value as either a static value (to pass a fixed value), a token (to pass a dynamic value) or liquid markup (for more advanced customization needs).

 

Add a Static Value

Used to pass a fixed value to a field in an integrated Marketing Automation or CRM system.

Example: Using Static Values

  • The value Integrate will be passed to the integrated system field Comments.

dap-postouts-settingupeloqua-19.png

 

Add a Token

Used to pass dynamic values to a field in an integrated Marketing Automation or CRM system. See Post Out Available Tokens for more details.

Example: Using Tokens

  • The token {{lead.Id}} in the Custom column will send the Integrate Lead ID (eg.
    6004f44e-d962-4396-9f7c-484c3b25558a) as a value to the integrated system field integrateLeadID1.

dap-postouts-settingupeloqua-24.png

 

Add Liquid Markup

Use Liquid Markup to further customize how data is passed to your integrated Marketing Automation or CRM system. See Post Out Customization using Liquid Markup for more information.

Example: Using Liquid Markup

  • The Field column has been set to Custom Field in the first two rows and liquid markup {{ lead.Field |Escape|Capitalize }} added to the Custom column.
  • This will ensure that the first letter of the First Name and Last Name values is always capitalized.

dap-buildbasics-integrationfieldmapping-04.png

 

 

Recommended Reading

 

For more help, get in touch with our Support Team or your Customer Success Manager.

Related articles