Sometimes you need to set a new field value based on existing lead data. For example, your lead vendors send a variety of phrases in a comments field, which you then translate into one of five Campaign IDs you’re using for the month or perhaps you’re buying Facebook Lead Ads and need to associate each Facebook Ad ID with the proper Campaign ID in your CRM. Let’s see what this looks like in practice.
Configure a Mapping
Following the first example above, one of your vendors sends a lead with the comment “ActiveProspect Inbound Mapping”, which should be associated with a Campaign Name of “Example Campaign” and a Campaign ID of “CS-47”. To do this, you’d create two Inbound Field Mappings to set additional field values – one for Campaign Name and the other for Campaign ID, as you can see in this screenshot.
Now, in any leads coming from that vendor, you can see the values for Campaign ID and Campaign Name are set and available, even though that information was not included in the original lead data.
This is useful for a few reasons:
- These newly mapped values are available as lead data to every step in the Flow, so you can make routing decisions based on the data.
- This can dramatically simplify the Outbound Field Mapping on your CRM delivery step by moving many of the source-specific mappings to Inbound Field Mappings. Set all of your field mappings on the Source and you may never need to touch the Outbound delivery again.
- Keeping all vendor-specific field mappings on the source makes it easier to find, organize, and maintain them, compared to juggling all of the logic for every source in your outbound delivery step.