Any buyer, any API — every delivery kept on record.
Delivery & Integration
Connect any buyer that takes leads over HTTP, and keep proof of exactly what you sent and what came back.
There's no fixed integration list to wait for. Requests build from a JSON template with variable substitution and header-based authentication, if a buyer accepts leads over HTTP, you can connect them today.
A lead needs to reach the buyer, your tracker, and often your own team. CRM, Postback, Telegram, Email, and generic Webhook, one system handles all of it.
Many CRMs return HTTP 200 with an error buried inside the JSON. Without catching that, you record failures as successes and bill for leads that never landed, so success is defined by the response body, not just the status code.
The buyer's own lead ID is what makes later reconciliation possible. Pull it, along with an auto-login URL or status, straight out of the response with an interactive picker, no manual step required.
"We never received that lead" is the most common dispute in this business. Every attempt is recorded immutably, the exact request, the exact response, and a reconstructed curl command you can replay, ending the argument with evidence instead of memory.
Attribution has to survive the whole journey from click to FTD. Click IDs from Binom, Keitaro, Voluum, RedTrack, and ad platforms like Taboola, Google, Meta, and MGID are recognized and carried through to postbacks automatically.
Running several trackers or ad sources means each needs its own conversion endpoint. Postbacks are selected by tracker match, then traffic source match, then universal fallback, chosen automatically per lead.