​
Ping+Post Routing

Ping+Post Routing is a real-time lead auction system. When a lead is generated, Pingtree “pings” all eligible buyers simultaneously, collects their bids, then posts the lead data to the highest bidder for final acceptance.

​
How It Works

  1. Lead Submission
    A visitor submits their information via a form, landing page, or aggregator. Pingtree receives the lead payload.

  2. Ping to Buyers
    Pingtree issues a Ping request (HTTP GET or POST) to each configured buyer endpoint. This request includes the lead’s data (name, contact details, product preferences, etc.).

  3. Buyers Respond
    Each buyer evaluates the lead against their criteria (quality, location, vertical, etc.) and returns an API response containing:

    • Accept/Reject flag
    • Bid Amount (price they’ll pay)
    • Ping ID (unique token for this auction round)

  4. Select Highest Bid
    Pingtree filters out all rejects, then sorts the remaining bids from highest to lowest. The top bidder is chosen.

  5. Post to Winning Buyer
    Pingtree sends a Post request—including the lead data and the buyer’s Ping ID—to the winning endpoint.

  6. Finalize Lead Sale

    • If accepted: The lead is marked sold, revenue is recorded, and the buyer’s response completes the transaction.
    • If rejected: Pingtree removes that buyer and repeats Step 5 with the next highest bidder.

  7. Fallback
    The process continues until a buyer accepts or all bids are exhausted.

​
Buyer Posting Specs

When integrating a Ping+Post buyer, their API docs will specify:

  • Ping endpoint URL & required fields
  • Post endpoint URL & required fields
  • Any static tokens or headers distinguishing Ping vs. Post

Ensure you capture and map all tokens (e.g., ping_id) from the Ping response for use in the subsequent Post.

​
Configuration & Setup

Follow these steps to configure a Ping+Post endpoint in your campaign:

1

Enable Ping+Post Routing

In your Custom Endpoint or Advertiser’s Lead Routing section, toggle on Ping+Post and switch to the PING tab.

2

Map Ping Request Fields

• Enter the Ping endpoint URL and HTTP method/format.
• Map all required lead fields.
• Optionally, toggle Bypass Ping to use this endpoint as a direct Post.

3

Configure Ping Response Mapping

• Set the Ping Timeout (seconds to wait for each buyer).
• Map your Ping ID token for use in the Post.
• Map Accept/Reject (response flag).
• Map Bid Amount for revenue attribution.
• (Optional) Map URL or Reject Reason for logging and debugging.

4

Map Post Request Fields

• Switch to the POST tab.
• Enter the Post endpoint URL and HTTP method/format.
• Map all required lead fields, including the captured Ping ID.
• Configure response mapping to confirm final sale or rejection.

5

Test & Activate

• Use Get Sample Response to ping your endpoint with a real transaction_id.
• Verify field mappings and bid logic in the tester UI.
• Enable and Save your endpoint.
• Run a live test to confirm end-to-end functionality.

Tip: Mapping the bid amount in the Ping step ensures your platform records the correct revenue value as soon as the lead is sold.