Impression Sync

Beta

Some fraudsters try to suppress detection tags — stripping the script before it loads or blackholing the request, intercepting it. When that happens, Post-bid sees no impression at all, which can make the traffic look cleaner than it is.

Impression Sync is how we close that gap. It is a server-to-server postback that fires from your backend every time you serve an impression where the detection tag should have loaded. Even if the tag itself gets blocked on the device, the postback still tells us the impression happened.

By comparing the two streams — tags Pinokio actually received and Impression Sync events you reported — we can identify where tag evasion is happening. If you report 100 impressions but the tag only fired 80 times, those missing 20 are suspicious.

How it works

Impression Sync runs in parallel to your detection tag. Whenever your ad server serves an impression with a Pinokio tag attached, your backend also sends a postback to Pinokio with details about that impression.

Setup: server-to-server (S2S)

Pinokio’s Impression Sync integration is server-to-server. Your account manager will provide a callback URL. For every impression that should have a detection tag, your backend makes a single POST to that URL with the impression’s details.

The parameters mirror the detection-tag parameters — see Parameters for the list. Most of the values come from the same source you use to populate the tag itself, so the integration is usually a matter of duplicating the call from your ad-serving code path.

Pinokio uses Transaction ID (ti) to link Impression Sync postbacks to the corresponding detection-tag events. Make sure the same value is sent on both sides.