<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=134132097137679&amp;ev=PageView&amp;noscript=1">

GIVT fraud detection: What is pre-fetch or browser pre-rendered traffic?

Aug 4, 2017 12:15:44 PM

Pixalate is an MRC-accredited company for the detection and filtration of Sophisticated Invalid Traffic ("SIVT") desktop and mobile web impressions.

According to the Media Rating Council’s (MRC) standards for Invalid Traffic Detection and Filtration Guidelines, there are two types of invalid traffic:

  • GIVT (General Invalid Traffic)
  • SIVT (Sophisticated Invalid Traffic)

One example of GIVT is “pre-fetch or browser pre-rendered traffic.”

What is “pre-fetch or browser pre-rendered traffic” in the MRC definition of GIVT?

pre-rendered traffic.jpg

Modern web browsers may load some website content prior to the user accessing it. This is done to help the user have a more seamless, responsive experience on the web.  However, this preloading can result in an ad impression, and such impressions are filtered out, once it has been determined that the given pre-loaded content was never actually accessed by the user.

Much like the User-Agent header described here, many browsers use a standard field to describe the transaction as a pre-load. GIVT-accredited companies will use this field where available and other transactional data where not to map valid subsequent impressions and clicks to this activity.

MRC-accredited ad fraud detection and prevention companies must be able to identify pre-fetch or browser pre-rendered traffic (and clicks), based on the MRC’s definition of GIVT.

What are some other examples of GIVT?

Pre-fetch or browser pre-rendered traffic is just one example of General Invalid Traffic (GIVT) as defined by the MRC. To learn about some of the other examples of GIVT, click on any of the examples below:


Search Blog

Follow Pixalate

Subscribe to our blog

Subscribe to our blog