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.
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 form and verify with Test Integration.
What are buyer delivery methods?
A delivery method is how a campaign buyer receives a lead once that buyer is eligible and selected. It is a separate setting from Buyer Type (for example cost per lead), which controls how the buyer is priced.
| Method | How the buyer gets the lead |
|---|---|
| Direct Post | Datahubb sends the lead straight to the buyer's endpoint in one request |
| Ping/Post | Datahubb asks first, then sends the full lead only to the buyer that accepts |
| One-to-One | A ping/post variant for one-to-one consent, where the consumer picks the brand |
| Datahubb emails the lead to an address the buyer gives you | |
| Store Leads | Datahubb records the sale and keeps the lead, with nothing sent out |
| Google Sheet | Datahubb adds the lead as a new row in the buyer's own spreadsheet |
Your workspace may show a different set of options. Treat the labels in the Delivery Method dropdown as the 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 Integration and confirm the response or delivery result.
- Send one campaign-level test lead and read the timeline.
Google Sheet is the exception to step 6. Its Google connection belongs to a buyer that already exists, so save the buyer first, then reopen it to connect the account and pick a spreadsheet.
Delivery methods in detail
Direct Post
One request per lead. As soon as the buyer wins the lead, Datahubb posts the full record to the buyer's endpoint and reads the reply to decide whether the lead was accepted or rejected.
You configure the Post URL, Request Method, Payload Type, Response Type, the fields you send, and the rules that read the buyer's reply.
Best when the buyer has a stable endpoint and a fixed price.
Ping/Post
Two steps. Datahubb first sends a ping with a trimmed set of fields so the buyer can say yes or no, and on bidding campaigns name a price. Only the winning buyer then receives the full lead in the post.
You configure everything a direct post needs, plus a Ping URL, the fields the ping carries, and the rules that read the ping reply.
Best when buyers want to qualify or bid on each lead before they commit. Expect it to take longer than a direct post, because the buyer has to answer twice.
One-to-One
A ping/post variant built for one-to-one consent. The buyer's ping reply carries a list of brands instead of a single yes or no, the consumer sees those brands and picks one, and the lead goes to the brand they chose.
You configure the ping and post settings, plus One-To-One Settings, which tell Datahubb where the brand list sits in the reply: Max Buyers, Buyer List Key, and the keys holding each brand's name, logo, bid id, and price.
Best when consent has to be tied to a single named brand the consumer actually agreed to.
The lead arrives in the buyer's inbox instead of at an endpoint, and you control exactly what the message looks like.
You configure To, Subject, and HTML Body, which are all required, plus optional Reply-To, CC, BCC, custom headers, and Attach lead as CSV with the columns you choose.
There is no reply to read, so the delivery counts as successful once the message is sent. A buyer cannot reject an emailed lead at the moment of delivery.
Best when a person, not a system, works the leads.
Store Leads
Nothing leaves Datahubb. The lead is recorded as sold to that buyer and kept in the platform. There is no endpoint, no message, and no Test Integration button, because there is nothing to call.
There is nothing method-specific to configure. Set the buyer's price, schedule, and caps as usual.
Best when you are tracking an offline or manual arrangement, or holding leads for a buyer who collects them another way.
Google Sheet
Each lead becomes one new row in a spreadsheet the buyer already owns. Datahubb does not create the spreadsheet. Every buyer connects its own Google account, so two buyers on the same campaign can write to two different accounts.
Because the connection belongs to a saved buyer, set Delivery Method to Google Sheet, click Save, then reopen the buyer and finish the setup:
- Click Connect Google and sign in.
- On Google's consent screen, keep the See, edit, create and delete only the specific Google Drive files you use with this app box checked. That single permission covers both choosing the spreadsheet and writing rows to it.
- Click Choose from Google Drive. Google's own picker opens, including files on a Shared drive. Pick the spreadsheet.
- Set Sheet/Tab name, or leave it empty to use the first tab.
- Under Columns, pair each column header in the sheet with the value that fills it. Values take
{{field_name}}tokens or plain text. - Click Save, then test.
The picker only hands Datahubb the file you select, not the rest of your Drive. Once chosen, the sheet shows its name with an Open in Google Sheets link and a Change button if you picked the wrong one.
Values line up with the sheet's header row by name, so rows land under the right columns even when you map them in a different order. Click Sync after you change the sheet in Google to refresh the pickers.
Best when the buyer works out of a spreadsheet rather than an inbox or an endpoint.
Buyers connected before the picker existed need one reconnect. If the button reads Reconnect and grant the Drive files permission to choose a spreadsheet, that buyer is still on the older authorization. Deliveries keep running in the meantime, so reconnect when it suits you rather than urgently.
Generated values in templates
Three shortcodes produce a value at delivery time instead of reading one from the lead. They work anywhere a template does: ping and post bodies, headers, URLs, email fields, and Google Sheet columns.
| Shortcode | What you get | Example output |
|---|---|---|
{{$system:uuid}} |
A UUID for this delivery | 3cffeadd-0dd9-4cee-b8de-a39b0d13d3a3 |
{{$system:random}} |
A random 8-digit number, useful as a cache-buster | 48210377 |
{{$system:now}} |
The time the request is sent, ISO-8601 UTC | 2026-08-25T12:00:00+00:00 |
The value is generated once per delivery and frozen, so the ID in an email subject matches the one in its body. A retry reuses the same value, which is what lets a buyer treat it as a duplicate check rather than a second lead.
Chain a transformer to reformat the timestamp, for example {{$system:now||date:Y-m-d H:i:s}}. Use {{$lead_date_utc}} instead when you want when the lead arrived rather than when you posted it.
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 |
| Consent must name the brand the consumer picked | One-to-One |
| Buyer wants leads in an inbox for manual handling | |
| Internal recording without an outbound send | Store Leads |
| Buyer works out of a spreadsheet | Google Sheet |
For a deeper comparison of the two HTTP models, see Direct post and ping/post.
Tips and gotchas
- Re-test after any change to the method, endpoint, template, or mapping.
- Every method still consumes eligibility, caps, and schedules. Email, Store Leads, and Google Sheet only simplify the transport.
- Email, Store Leads, and Google Sheet give the buyer no way to confirm a sale. A cost per acquisition buyer on these methods gets a pending sale that is only confirmed if a postback arrives some other way, so use cost per lead for these buyers.
- Test Integration performs a real delivery. An Email buyer gets a real message and a Google Sheet buyer gets a real row, so point the first test at an address or tab you can clean up.
- If the buyer shows "This connection is missing the required Google Drive permission", the Drive files permission was not granted. Disconnect, reconnect, and keep the specific Google Drive files box checked.
- If Choose from Google Drive does nothing, the picker window was blocked. Use Google Chrome, disable ad blockers and privacy extensions for this site, allow cookies, and avoid private or incognito windows.
- "Caller does not have permission" from Google means the connected account lost access to the spreadsheet. Fix the sharing in Google, not the buyer settings.
- Disconnecting a Google account clears that buyer's saved spreadsheet, so a newly connected account cannot inherit a sheet it can't open.
- If the timeline shows skips before delivery, fix eligibility first, not the endpoint.
- Do not paste production credentials into shared tickets while debugging delivery.
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
Comments
No comments yet — be the first to share your thoughts.