Set up outbound postbacks

This article shows how to set up outbound postbacks so Datahubb tells a traffic source or an external supplier when a conversion happens.

Outbound postbacks are how a partner learns that a lead sold, a click converted, a call paid, or an exit offer converted. The recipient is a traffic source or a supplier, never a buyer.

What outbound postbacks can do

Datahubb can notify the recipient's postback URL when subscribed events fire, with the payout and ids they need to credit the conversion.

Trigger events (common)

Lead lifecycle (conversion notices to the network):

• lead_sold — umbrella for accepted or stored sold outcomes (typical default)
• lead_accepted, lead_pending, lead_rejected, lead_stored, and related statuses when the network needs finer detail
• lead_manual_fire — re-fire from tools such as Lead Import

Click / exit / call:

• click_converted — optionally filter to cpc, cpl, or cpa
• exit_offer_converted
• call_converted

What you send the network

Prefer v2 tokens in double braces. Common conversion fields:

• {{event.external_id}} — id the network already knows
• {{event.status}} — outcome
• {{event.payout}} — amount you are paying the traffic source for this event
• {{event.id}} / {{event.timestamp}}
• Lead fields such as {{lead.payload.email}} when the network requires them

Admin-only tokens (for example revenue or profit) are not available to traffic-source users.

Who receives it

A postback config is addressed to one recipient, and the type decides which leads it can ever fire for.

Buyers are never outbound postback recipients. A buyer is told about a lead through its delivery method, not a postback.

Prerequisites

• Postbacks feature enabled
• The recipient account: either an internal supplier with at least one traffic source, or an external supplier
• The recipient's postback URL and the query or body fields they expect

Create an outbound postback config

1. Open Postbacks in the sidebar.
2. Click Create.
3. Choose the recipient type, Traffic source or Supplier, then pick the account that should be notified.
4. Subscribe to the events the network should hear about (start with lead_sold for sold-lead conversion).
5. Enter the network’s postback URL and HTTP method.
6. Choose a body mode if needed: none (URL only), form, or JSON.
7. Map tokens into the URL or body so the network receives external id, status, and payout.
8. Optional gates:
   • Min payout — skip low-value fires
   • Campaign scope — only fire for selected campaigns
   • Click-type filter — on click_converted
   • Rules — advanced match conditions
   • Signing secret — if the network verifies HMAC
9. Save.
10. Use the Test panel, then confirm in outgoing postback logs. If nothing fired, open the Resolution Trace.

Traffic-source users only see and edit configs for themselves.

Expected result

• When a subscribed conversion happens for that recipient, Datahubb calls their URL
• The recipient can credit the conversion using the external id and payout you sent
• Logs show the request; Resolution Trace explains any skip

Troubleshooting

• Nothing fired — wrong trigger, inactive config, or gates (min_payout, scope, rules, click type)
• Network got empty ids — map {{event.external_id}} (and ensure the lead was submitted with that external id)
• Wrong payout — confirm traffic-source pricing and which event you subscribed to
• Need Meta pixel instead of a custom URL — use the Meta CAPI postback preset for that traffic source

Related articles

• Set up Meta CAPI postbacks
• Sync leads to ActiveCampaign
• Set up Array credit check
• Traffic sources for affiliates