To get started with your field mappings, you'll want to add the Ping reference field. This system field references the ping response from the client 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.

Once you have the Ping Reference field configured, you can begin to map the rest of your lead fields. Start by clicking the Import 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 denoting if the delivery is in test mode, as shown in the example above, by clicking the New button and adding your lead field.

This is also where you’ll add enumerated values for dropdown fields. First, select the lead field 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.

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.

Next article: Request Body Tab>