Overview
Sending leads through Ping/Post delivery is one of the most common and flexible delivery methods in LeadExec. This process allows LeadExec to first send a lightweight PING request to determine buyer interest or retrieve a bid price, and then send the full POST payload only if the lead is accepted.
Ping/Post delivery is especially useful when working with multiple buyers or when routing decisions depend on real-time bids, availability, or qualification rules.
Unlike older configurations that required separate delivery methods, LeadExec now supports configuring both the PING and POST settings within a single Delivery Method.
Common Use Cases
Ping/Post delivery is ideal when:
Leads need to be routed dynamically based on buyer availability or bid price
Buyers must approve or bid on leads before receiving full lead data
You want to maximize lead revenue by selecting the highest bidder
Different buyers have different acceptance criteria
How Ping/Post Works
Step 1 - PING Request
LeadExec sends a partial lead payload to one or more buyers. This usually contains limited information such as:
Zip code
State
Age range
Lead type
Other qualifying data
The purpose of the ping is to determine whether the buyer is interested in the lead before delivering the full payload.
Step 2 - Buyer Response
The buyer responds with:
A bid value
An acceptance/rejection response
Qualification information
LeadExec then evaluates the response based on the configured response settings.
Step 3 - POST Request
If the ping is accepted, LeadExec sends the full lead payload to the selected buyer.
Depending on the configuration:
LeadExec may choose the highest bidder
Or route based on criteria-based acceptance rules
If the ping response is rejected or invalid, the post request is skipped.
Setting Up Ping/Post Delivery
Create the Delivery Method
Navigate to Delivery Methods
Click Create
Enter a Description
Select the appropriate Lead Type
Within the Delivery Method, configure both:
PING Configuration
POST Configuration
Each section contains its own:
URL Endpoint
Authentication
Mappings
Request Body
Response Settings
Retry Settings
Information Required From the Buyer
Before configuring the integration, collect the following information from the buyer:
URL Endpoints
PING endpoint
POST endpoint
Content Type
Examples include:
JSON
XML
application/x-www-form-urlencoded
Required Fields
The buyer should specify:
Which fields are required for the ping
Which fields are required for the post
Use field mappings to align LeadExec fields with the buyer’s expected format.
Request Body Format
The buyer should provide examples or documentation showing how the payload must be structured.
Response Settings
The buyer must specify:
What response indicates acceptance
What response indicates rejection
Where the bid value is located (if applicable)
For more details click here
Mapping Fields
Use the Mappings section within the delivery method to match your LeadExec fields to the format required by the buyer.
Examples:
FirstName → first_name
ZipCode → zip
Phone → phone_number
Correct field mapping is critical for successful delivery and response parsing.
Configuring the Delivery Account
Navigate to Delivery Accounts
Click Create
Enter a Description
Select the configured Ping/Post Delivery Method
Because both ping and post configurations now exist within a single delivery method, there is no longer a need to create or link separate delivery methods.
Best Practices
Always test both the PING and POST requests before going live
Keep the PING payload minimal to reduce processing time
Validate response parsing carefully
Monitor delivery logs regularly
Confirm authentication and content type settings match the buyer requirements
Troubleshooting
Lead Is Not Posting
Verify that:
The ping response contains the expected acceptance value
The bid value is being parsed correctly
Response settings are configured properly
Fields Are Not Mapping Correctly
Check that:
Field names match the buyer requirements
Required fields are included
Mapping values are configured correctly
Invalid Content Type Errors
Ensure the configured content type matches the actual request format.
Examples:
JSON requests should use
application/jsonForm-encoded payloads should use
application/x-www-form-urlencoded
No Response From Buyer
Test the endpoint externally using tools like:
Postman
Curl
RequestBin
This helps verify the endpoint is active and responding properly.
Delivery Failures
Confirm:
The Delivery Account is using the correct Delivery Method
Authentication settings are valid
The endpoint URL is correct
Request body formatting is valid