Skip to main content

Field Mappings Tab: Map Lead Fields to Your Buyer's Fields

Field mappings let you match the fields set on your lead type to the field names the receiving system expects.

Written by Gabriel Buck

Overview

The Field Mappings tab (Mappings tab) allows you to configure how lead data is mapped between your LeadExec lead type and the fields expected by the buyer's delivery endpoint. This ensures that the correct values are delivered in the proper format.

This article covers the Field Mappings tab for Webhook, SalesExec Integration, FTP, Email, CSV Attachment, Batch Delivery and SMS Notification. Ping Post has its own article: Ping-Post Field Mappings.

Key functionality

  • Map your lead fields to the field names expected by the buyer's system, based on their posting documentation.

  • Customize field names or use the default names defined on your lead type.

  • Add additional static or custom fields required by the buyer (e.g., a static field denoting if the delivery is in test mode).

  • Configure enumerated value mappings (dropdowns) when the buyer's system requires specific value sets.

Map your fields

  1. Click the Import button in the top menu of the Mappings tab. This opens a popup window containing all the fields from your lead type.

  2. Map each of your lead fields to the field names your buyer's system requires based on their posting documentation.

  3. Update field names if necessary, or leave them as the defaults from your lead type.

  4. To add extra fields required by the buyer (such as a static "test mode" field), click New and enter the field.

  5. For fields with enumerated (dropdown) values:

    • Select the field and click Edit.

    • Toggle Has Value Mappings to Yes to enable mapping. The window expands.

    • Click Add to configure the required value mappings.

  6. If the buyer's system accepts the same enumerated values as your lead type, you can leave the default values unmapped. The system will default to the values set on the lead type.

  7. Click Save once all fields are configured.

Best practices

  • Always verify the buyer's posting instructions or technical documentation before mapping fields to avoid errors.

  • Use default field mappings when possible to reduce unnecessary customization.

  • Document any custom fields or mappings for easier future reference.

  • For dropdown fields, ensure mapped values match the buyer's required format exactly.

  • Test your configuration with sample deliveries before going live.

Troubleshooting

  • Missing fields in deliveries: Verify the field was imported and mapped correctly.

  • Incorrect field names: Check for typos, capitalization differences, or formatting mismatches.

  • Dropdown value errors: Ensure all enumerated values are mapped correctly.

  • Extra or unnecessary mappings: Simplify by removing redundant mappings if the buyer accepts default values.

Next step

After the Mappings tab, continue with your delivery method's next tab:

Related Articles
Did this answer your question?