Overview
This article will guide you through setting up the ping post delivery method, which handles the "post" component of the process. You will also need to set up the "ping" using an HTTP Webhook delivery method.
Understanding Ping Post Delivery
Using Ping Post allows you to deliver partial lead data to buyers before the lead is sold. The method comprises two parts: a "ping", which allows clients to preview the lead and bid if they want to buy it, and a "post", which will be sent to clients only if they bid on or accept the initial ping.
Ping: Send partial, basic lead data such as state, loan amount, etc., if accepted by the buyer, then the post is sent
Post: After the bid is accepted, deliver full lead details (including the ones sent in the initial ping).
How to Configure a Ping Post Delivery
Configuring a Ping Post delivery requires the use of two delivery methods: the ping delivery method, which is typically a standard HTTP Webhook delivery method, and the POST delivery method, using the PING/POST delivery method type. These two delivery methods work together through the delivery account to control the delivery of the initial ping through the webhook method as its secondary delivery method, followed by the post, to send out the complete lead data when using the PING/POST delivery method as the primary delivery method in the delivery account.
Step-by-Step Setup
Create the PING/POST Delivery Method
Go to Delivery Methods → Click Create
Configure the basic settings:
Description → Custom name for your method (e.g., "Mortgage Ping-Post")
Delivery Type → PING/POST
Lead Type → Select the desired lead type
Environment → Production/Testing - if your client has a separate test endpoint, you can leave this as "Testing" while setting up before deployment, otherwise, leave it to the default "Production"
Click Create → Once done, review the settings you created in the General Settings tab, then let's proceed to URL Endpoint tab
Key Considerations
Lead Type Lock-In: Cannot change after creation
Testing: Use the "Testing" environment for client sandbox endpoints
Bid Requirements: Buyers must meet revenue rules set in the campaign settings
Best Practices
Naming Convention:
Include client name or any other key identifier + ping/post for easier handling (e.g., "Solar Co - Water Heater Post")Test Thoroughly:
Validate ping responses before going liveMonitor Bids:
Adjust revenue requirements if buyers rarely bid, and ensure the response settings are correct based on your buyers' posting instructions
Troubleshooting
Posts not sending:
Verify the PING/POST method URL endpointNo buyer bids:
Review campaign revenue requirements
Next article: URL Endpoint Tab >