Follow

LeadConduit : Outbound Field Mapping

« Previously: Delivering your leads

 

Field Mapping

Connects the dots between a Source (Your Form or Lead Vendor), LeadConduit, and the Delivery Destination.

 

Example: First Name

The lead vendor / your form uses the field name fname

LeadConduit uses the field name first_name

The delivery destination (e.g. Marketo) uses the field name FirstName

 

 

Outbound Field Mapping (LeadConduit to Destination)

Outbound Field Mapping is typically configured in the Destination step. This is often a CRM or Marketing Automation platform.

Once you've selected a delivery, click the "Edit Field Mappings" button. You'll be prompted with a form to connect the LeadConduit standard field or raw value to a field used by the Destination service.

LeadConduit Built-In Integrations

Let's use the First Name + Marketo example from above.

Because LeadConduit already has a Built-In Integration with Marketo, there are a handful of fields automatically mapped for you behind the scenes, including First Name, so you don't have to include it in your Outbound Field Mapping.

Let's say you also are collecting IP Address, which the LeadConduit Built-In Integration with Marketo does not cover. You need to map that field from LeadConduit to Marketo.

On the left is the LeadConduit Standard Field

On the right is the field name for the Destination. 

NOTE the Marketo Custom prefix!

The Outbound Field Mapping section can do a lot of powerful/sneaky field and data manipulation, so the field mapping section makes no assumptions about what you are trying to accomplish. 

In this case, we want to connect a LeadConduit field name to a Marketo field name not covered in the LeadConduit Built-In Integration. So we have to select "Marketo Custom" first, then type in the field name.

If this were a Salesforce Built-In Integration instead, the prefix would be "Salesforce Custom".

LeadConduit Custom Integrations

LeadConduit won't always have a Built-In Integration for the Delivery you use. When that's the case, you set up a Custom Integration, which was covered in "Delivering your Leads".

Since this is 100% Custom, you must map all fields from LeadConduit to the Delivery.

However, you won't find a "Custom" prefix here. Instead, you'll find different prefixes depending on which type of delivery form you selected (POST, GET, JSON, XML, SOAP).

Examples:

Custom HTTP Post - Form Field (like the generic example at the top)

 

Custom GET - Parameter

 

SOAP - Arg

 

XML - Xml Path

 

JSON - JSON Property

 

Conditional Field Mapping

Sometimes you want to set a condition for the field mapping, so you can set different values based on the input. This is often the case for Campaign IDs. Here's an example:

The Velocify Campaign ID will be 1234 when the source is LendingTree and 5678 when the source is TARDIS.

 

See Advanced Field Mapping for additional outbound field mapping scenarios.

 

NOTE LeadConduit automatically URL encodes fields on outbound delivery. No additional configuration is needed.

 

Special Formatting Options

Certain field types offer a rich, built-in set of formatting options. This video explains how to recognize and use such fields.

Next: Flow Management »

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

You must be logged in to comment.