Buyer delivery methods
This article gives a high-level overview of how buyers can receive leads in Datahubb. Use it to pick a delivery method before you configure URLs, templates, or mappings in the buyer form.
It does not cover request body formats. Configure those in the buyer UI and verify with Test Buyer Integration.
What are buyer delivery methods?
A delivery method is how a campaign buyer receives a lead after they are eligible and selected. Pricing type (for example cost per lead) and delivery method are separate settings on the buyer.
| Method | What the operator should expect |
|---|---|
| Direct post | One-step delivery of the lead to the buyer |
| Ping/post | Two-step path: ping eligible buyers, then post to the winner |
| Lead delivered to the buyer by email | |
| Store | Lead recorded as sold or stored for that buyer without an outbound buyer post |
Your workspace may show additional options depending on features. If you see methods beyond this list, treat the in-product labels as source of truth and test before go-live.
Prerequisites
- Buyer user created in Manage Users
- Campaign Buyers tab access
- Agreement with the buyer on how they want to receive leads
Configure delivery
- Go to Campaigns and open the campaign.
- Open the Buyers tab and click Add Buyer, or open an existing buyer.
- Select the Buyer user.
- Choose Buyer Type and Price.
- Choose Delivery Method.
- Complete the method-specific sections the form reveals.
- Optionally set Schedule and Caps so the buyer is only eligible when they should be.
- Click Save.
- Click Test Buyer Integration and confirm the response or delivery result.
- Send one campaign-level test lead and read the timeline.
Caps and schedules (briefly)
Delivery only happens if the buyer is eligible.
- Schedules define when the buyer is online.
- Caps limit volume or budget for a period.
A correctly configured delivery method still receives nothing while the buyer is offline or capped. See Caps and schedules.
When to use each method
| Situation | Start with |
|---|---|
| Fixed-price buyer with an HTTP endpoint | Direct post |
| Buyers bid or pre-qualify per lead | Ping/post |
| Buyer wants leads in an inbox for manual handling | |
| Internal recording without outbound post | Store |
For a deeper comparison of the two HTTP models, see Direct post and ping/post.
Tips and gotchas
- Always re-test after changing method, endpoint, or mappings.
- Email and store simplify transport but still consume distribution eligibility, caps, and schedules.
- Ping/post needs more validation time than direct post.
- Do not paste production credentials into shared tickets while debugging delivery.
- If the timeline shows skips before delivery, fix eligibility first, not the endpoint.
Expected result
Each buyer has an intentional delivery method, optional caps and schedules that match business hours, and a passing delivery test before live traffic.
Frequently asked questions
Is delivery the same as distribution? No. Distribution picks the winning buyer. Delivery is how that buyer receives the lead.
Can two buyers on one campaign use different methods? Yes. Keep the mix understandable, especially on day one.
Where do I map buyer field names? In the buyer configuration UI for that delivery method. Verify with Test Buyer Integration.
Does store still count as a sale for reporting? Store is designed to record the buyer outcome without an outbound post. Confirm the status you see on the test lead timeline before relying on it in production.
What should I do if email delivery fails? Check the buyer email settings in the form, then use the delivery logs or timeline detail available in your workspace. Re-test after fixes.
Which method is best for Highest Bidder? Ping/post, because buyers need a way to return bids before the final post.
Related articles
Comments
No comments yet — be the first to share your thoughts.