Why Pay-Per-Call Should Use Postbacks, Not Pixels

The Problem with Pixels

A pixel fires from the consumer's browser at the moment of
conversion. For pay-per-call this is exactly the wrong
attribution surface: the consumer is on the phone, often not
looking at the page, and may have closed the browser tab
entirely. Pixels are also vulnerable to ad blockers, browser
privacy modes, and outright fraud (anyone can fire a pixel
URL).

Why Postbacks Win for Calls

A postback is a server-to-server HTTP request that Trackdrive
sends to the buyer (or traffic source) after the call event
occurs. It does not depend on the consumer's browser, cannot
be blocked by ad blockers, and can be authenticated with a
shared token that prevents spoofed conversions.

Postbacks also fire on real telephony events: call answered,
call duration reached, conversion recorded, conversion
reversed. A pixel only fires once and cannot be retracted if
a fraudulent conversion needs to be clawed back.

How to Configure

Outgoing webhooks (postbacks) are configured per buyer or per
offer under "Triggers For Webhooks & Actions" in the sidebar.
Each webhook can be tied to a specific event (call accepted,
conversion, conversion reversal) and posted to the partner's
endpoint with their preferred token format.