Overview
The Field Mappings tabs allow you to configure how lead data from your LeadExec lead type is mapped to the fields expected by the client’s delivery endpoint. This ensures the correct data is passed in the proper format.
Key Functionality
Define how lead fields should map to the destination fields required by the client.
Add static, custom, and system fields when additional values are required (e.g., flags, IDs, constants, calculated expressions, functions, lead source information, etc).
Manage enumerated/dropdown value mappings when clients require specific sets of values.
Ensure the field output aligns with the client’s posting documentation.
How to Use This Feature
To get started with your field mappings, you'll want to add the Ping reference field to your Post mappings. This system field references the ping response from your client's system (after sending an initial ping) and pulls in the unique identifier for accepted pings.
The receiving system will require the correct identifier to be included with the full lead data to match the post with the ping. In the example shown above, the receiving system expects "OrderID" as the field name. Please keep in mind that the field name will vary depending on your client's system and specific setup, so it's always necessary to ensure you're given the full posting instructions for a smooth, efficient ping/post setup.
Once you have the Ping Reference field configured, you can begin to map the rest of your lead fields.
Configuration
Both the PING and POST Configuration tabs work similarly, with the Ping tab allowing you to add some of the mappings to the Post body by default.
To create your mappings, start by clicking the Bulk Add button in the top menu of the Mappings tab. This will generate a popup window containing all the lead fields from your lead type. This is where you will map the existing lead fields in your lead type to the field names your client’s system expects based on their posting documentation.
You can customize each field name or use the default values set on the lead type.
You can also add any additional fields the client requires, such as a static field with a predetermined value, as shown in the example above, by clicking the New button and selecting static field. Notice you'll also be asked if you want to add this value to the Post body as well.
This is also where you’ll edit enumerated values for dropdown fields. First, select a lead field with dropdown options, and click edit to add enumerated values.
Next, toggle the “Has Value Mappings” button to Yes, which will expand the window. Finally, click the “Add” button to begin mapping your enumerated values; you'll add the values as you have them in your lead type (source value) and how you want to send that value to your client (target value).
Note: If the receiving system is expecting the same enumerated values as set on your lead type, you can skip mapping because the system will default to the values set on the lead type.
Best Practices
Always check the client’s posting documentation for exact field requirements.
Use default field mappings when possible for simplicity.
For dropdowns, verify that mapped values match client requirements exactly.
Add notes on custom/static fields for future reference.
Run test deliveries to confirm mappings before going live.
Troubleshooting
Fields missing from deliveries → Confirm the field is imported and mapped.
Incorrect field names → Double-check against the client’s required field naming.
Errors with dropdowns → Ensure all required value mappings are configured.
Unexpected values delivered → Review custom/static fields for accuracy.
Existing Ping values are missing from the Post → Make sure you are mapping all necessary values on both PING and POST Configuration tabs.
Post is missing a Ping ID Reference → Confirm that you have configured a Ping Reference ID field. Refer to your client's posting instructions to identify this field's name.
Next article: Request Body Tab>