Direct Post vs Ping-Post
Understand the difference between Direct Post and Ping-Post campaigns in Lead Distro AI. Side-by-side comparison, when to use each, how they affect distribution, pricing, and supplier integrations.
Two Ways to Receive Leads
Every campaign in Lead Distro AI uses one of two routing methods for how leads enter the system: Direct Post or Ping-Post. This choice determines the supplier-side integration flow. You set it when you create the campaign and it applies to all suppliers on that campaign.
Direct Post
Direct Post is the standard, single-step flow. The supplier sends the full lead in one API call. Lead Distro AI validates it, runs inbound filters, checks for duplicates, and distributes it to the best available buyer immediately.
- One API call from the supplier containing all lead data.
- Fastest path — no round-trip delay between ping and post.
- Simpler integration — suppliers just POST the lead and get back a success or rejection.
- Lead Distro AI handles distribution in the background (async) and the supplier gets a response right away.
Direct Post is the default for new campaigns and works well for most verticals. Start here unless your suppliers specifically need to pre-qualify leads before posting.
Ping-Post
Ping-Post is a two-step flow. The supplier first sends a "ping" with partial lead data (phone, email, state) to check if the lead will be accepted. If accepted, the supplier sends a second "post" request with the full lead data and a signed token from the ping response.
- Two API calls — a ping (partial data) followed by a post (full data + token).
- Pre-qualification — suppliers know if a lead will be accepted before sending PII.
- Bid-based pricing — buyers can return dynamic prices on each ping, so the supplier sees what the lead is worth before committing.
- Token-based — the ping returns a signed
ping_idtoken (valid 30 minutes) that the supplier includes on the post. - Distribution runs synchronously during the post step, so the supplier gets the final accept/reject in real time.
Side-by-Side Comparison
| Direct Post | Ping-Post | |
|---|---|---|
| Supplier API calls | 1 (full lead) | 2 (ping + post) |
| Latency | Low (~100ms) | Medium (~300-500ms round trip) |
| Supplier sees price before posting? | No | Yes (if V2 protocol or buyer-side ping) |
| Buyer can bid per lead? | Only with buyer-side ping enabled | Yes (built into the flow) |
| Duplicate check on ping? | N/A | Yes, before accepting |
| Filter check on ping? | N/A | Yes, inbound filters run on partial data |
| Distribution timing | Async (background) | Sync (inline with response) |
| Best for | Non-competitive verticals, simple setups | Competitive verticals, bid-based pricing |
When to Use Direct Post
- You're getting started and want the simplest integration.
- Your suppliers don't need to pre-qualify leads (they send everything).
- You're running a non-competitive vertical (home services, B2B) where buyers accept most leads at a fixed price.
- Speed matters more than per-lead price optimization.
- You still want buyer-side ping-post bidding. Direct Post campaigns can enable per-buyer ping internally, so buyers bid on each lead even though the supplier integration is one step.
When to Use Ping-Post
- Your suppliers need to check availability before posting (common in lead aggregator networks).
- You want suppliers to see the best available price before committing their lead.
- You're in a competitive vertical (legal, insurance, mortgage) where per-lead bidding is standard.
- Your suppliers send high-volume traffic and want to avoid wasting bandwidth on leads that will be rejected.
- You need synchronous accept/reject responses so the supplier can immediately route the lead elsewhere if you reject it.
You can always enable buyer-side ping-post on individual buyers within a Direct Post campaign. This gives you bid-based pricing on the buyer side without requiring your suppliers to change their integration. The supplier posts once; Lead Distro AI pings buyers internally before delivering.
Changing Campaign Type
The routing method is set at campaign creation and cannot be changed after the campaign has received leads. If you need to switch, create a new campaign with the desired type and migrate your buyers and suppliers over. You can duplicate the existing campaign as a starting point.
Frequently Asked Questions
Can I mix Direct Post and Ping-Post suppliers on the same campaign?
Does Direct Post support buyer-side bidding?
Is Ping-Post slower than Direct Post?
What happens if a supplier posts without pinging first on a Ping-Post campaign?
flo_ping_id is required. Ping-Post campaigns enforce the two-step flow. Suppliers must ping first, get an accepted response with a token, then include that token on the post.Can I convert a Direct Post campaign to Ping-Post?
Related Articles
If you have any questions, send us an email at support@leaddistro.ai