Skip to main content

Email Field Mappings

Email field mappings allow you to configure the field names the receiving system expects to the fields set on your lead type.

Chris Arenas avatar
Written by Chris Arenas
Updated yesterday

Overview

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

Key Functionality

  • Map your lead fields to the field names expected by the client’s system.

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

  • Add additional static or custom fields required by the client (e.g., test mode flags).

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

How to Use This Feature

  1. Click the Import button. 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 client’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 client (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.

    • Click Add to configure the required value mappings.
      Screenshot Placeholder: “Enumerated value mapping UI”

  6. If the client’s system accepts the same enumerated values as your lead type, you can leave the default values unmapped.

  7. Save your mappings once all fields are configured.

Best Practices

  • Always verify client posting instructions 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 client’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/unnecessary mappings → Simplify by removing redundant mappings if the client accepts default values.


Next article: Email Template>

Did this answer your question?