Overview
Sending leads via ping post is one of the most common and flexible delivery methods in LeadExec. This two-step process allows you to “ping” a lead to a buyer to see if they’re interested, and then “post” the full lead details if the ping is accepted. Ping post is especially useful when you’re working with multiple buyers or need to optimize who receives the lead based on bid responses.
Use Case
Use ping post when:
You need to route leads dynamically to buyers based on availability, bids, or acceptance criteria.
Your clients want to approve or bid on leads before receiving the full data.
You want to maximize lead revenue by choosing the highest-bidding or first-responding buyer.
How It Works
Ping Step: A partial lead (usually limited data like zip code, age, etc.) is sent to one or more buyers.
Response: The buyer’s system responds with a bid or acceptance signal.
Post Step: Based on the response, LeadExec either sends the full lead (posts it) or skips it.
If using criteria-based delivery, it checks the buyer’s response to determine if the lead qualifies.
If optimizing by bid, LeadExec selects the highest responder to post to.
How to Set It Up
Create Two Delivery Methods:
PING: Create a delivery method with type HTTP Webhook.
POST: Create a delivery method with type Ping/Post.
Gather Client Requirements:
Your client should provide:
URL Endpoint – where the ping and post will be sent.
Content Type – format for the request (e.g., application/x-www-form-urlencoded, JSON, XML).
Required Fields – which lead fields to include in ping and post. Use field mapping to align your data with their format.
Request Body Format – how the ping/post payload should be structured.
Response Settings – the expected response format that signals acceptance or rejection of the lead.
Map Fields:
Use the field mapping tool in LeadExec to match your lead fields with the format your client requires.
Configure the Delivery Account:
Create a new delivery account.
Select the POST delivery method (Ping/Post type) as the primary method.
A field will appear prompting you to select a PING method – choose the HTTP Webhook method you previously created.
Best Practices
Always test both the ping and post endpoints separately before going live.
Clearly define and validate the response format expected by LeadExec.
Keep your PING payload minimal—only send what’s needed to get a valid response.
Monitor delivery logs to ensure leads are being sent and received as expected.
Troubleshooting
Lead Not Posting: Check that the response from the ping includes the expected acceptance keyword or bid value.
Fields Not Mapping: Double-check that all fields in your request match those defined in the field mapping configuration.
Invalid Content Type Errors: Ensure the content type matches the format of your request body (e.g., don’t send JSON with a form-encoded content type).
No Response from Buyer: Test the endpoint using Postman or another tool to verify it’s live and accepting requests.
Delivery Fails: Confirm the delivery account is linked correctly to both the PING and POST methods.