What is it?
LeadConduit’s real-time bidding lets your sources check, in real-time, a flow’s purchase bid price and volume cap status for a lead before they submit it.
How do I enable it?
Real-time bidding is only available to professional and enterprise tier clients who have pricing agreements in place for real-time bidding pings. Reach out to your Client Success Manager for more information.
Enter the flow editor and access the gear icon in the top right corner of your screen. Select the real-time bidding option and enable this feature by turning the toggle to the ‘on’ position. Save your flow.
Once enabled, we’ll automatically populate ping-related reports in your account and you’ll have an additional ‘ping’ tab in your Submission Docs.
How it works:
A real-time Bidding "ping" determines the flow’s lead purchase bid price and checks the status of applicable volume caps by applying the flow's cap and cost-pricing rules to the fields provided in a “/ping” request.
The response returned to the requestor’s “ping” request may be “success” with a price, “failure” with a reason, or “error”. The failure reasons can be based on the cap being reached ('Cap reached') , the fact that no bid was returned ('No bid'), or a more dynamic reason based on the acceptance criteria ('State must be included in TX, SC').From this information, the requestor may choose to accept the bid by submitting the lead.
Acceptance criteria that evaluate against specific values, such as a list of accepted states, will also be checked, but acceptance criteria that don’t involve specific values, such as a required field that doesn’t specify which values are accepted, are not evaluated. Because of this, and because the source can’t know what fields are involved in determining the price, sources should include the full lead data with a “/ping” request.
No data from a “/ping” request is either stored by or exposed to the buyer. Real-time Bidding pings do not appear in the flow's events tab. The lead data are evaluated in the background against the flow’s cap and pricing rules, then the data are discarded.
How To Perform a Real-time Bidding "ping":
Submit a request to the “ping” URL just as you would submit the full lead. The "ping" URL is identical to the LeadConduit submission URL, except that the "/submit" parameter is replaced by "/ping". These instructions are available in the source’s submission docs.
If this is your Source's "/submit" URL:
This is the matching "/ping" URL:
Complete "Ping" Request with field data:
https://next.leadconduit.com/flows/5e4j7703c63e50c74904f338/sources/63128b75e9969f5d1cef5n7/ping?first_name=Mike&last_name=Jonesfirstname.lastname@example.org&address_1=12 Main Street&address_2=Unit C&city=Fayetteville&state=PA&postal_code=17201&trustedform_cert_url=https%3A%2F%2Fcert.trustedform.com%2F351a4f1154d40415f8b2f295104566cd62b5d6
( GET is shown here for illustration purposes. You may send a "ping" request using any valid LeadConduit request method; GET, Form POST, Json POST, or XML POST )
Ping "Success" response body with price:
Volume caps for this lead are still open, and the buyer will pay $2.00 for the accepted lead.
Ping "Failure" response:
"reason": "Cap reached",
Volume cap has already been met. If submitted now to “/submit”, the lead will be rejected.
Note that ping responses do not contain lead IDs. That's because real-time bidding pings do not create LeadConduit lead events.