Skip to main content

Impression Sync

FraudSensor relies on detection tags to collect the signals that power our post-bid detection and analysis. Some fraudsters may try to avoid being discovered by preventing our detection tags from loading properly. This process, known as tag evasion, impacts FraudSensor's ability to detect and flag invalid traffic.

Luckily, HUMAN can identify tag evasion through a notification system called Impression Sync. Impression Sync helps us look for gaps in FraudSensor data and use these gaps to determine whether someone is deliberately evading our detection tags.

How Impression Sync works

Impression Sync is an extra integration option that runs in parallel to FraudSensor's detection tag: whenever you serve an ad impression in a location where our detection tag is deployed, your backend system should also trigger a separate logging system to let us know that an impression occurred. This gives us a record of all the times that our detection tag attempted to record an impression—regardless of whether the tag actually loaded on the end user's device.

Even if fraudsters prevent our detection tag from recording a particular impression, Impression Sync data still tells us whether our tag should have loaded alongside that impression. And by comparing the number of Impression Sync events to the number of times our tag successfully loaded, we can identify instances of tag evasion. For example, if you logged 100 Impression Sync events, but FraudSensor only recorded 80 impressions, it may be the case that our tag was evaded 20 times.

Set up Impression Sync

There are two different ways to set up Impression Sync: either via a server-to-server integration or via Snowflake.

Server-to-server (S2S)

In most scenarios, we recommend using a server-to-server integration to send us your Impression Sync data. To use this method, you'll need to make a postback request to HUMAN every time you serve an impression in a location where our detection tag is deployed.

A HUMAN representative will provide you with the custom callback URL where you should send your Impression Sync data. Each postback request should include basic information about the associated impression. Similar to our detection tags, Impression Sync uses URL parameters to send data.


Alternatively, you can share Impression Sync data with HUMAN via Snowflake. A HUMAN representative will help you set up a Secure View with data about the impressions that you serve.

The information we'll ask you to include in this Secure View is identical to the information we'd ask you to send via the server-to-server method. However, instead of making a unique postback request for each impression you serve, you can combine the data for all of your impressions in a single, shared table.