Overview
Pixalate is an ad fraud detection, traffic quality analytics, and brand safety platform used by publishers, advertisers, supply-side platforms (SSPs), and demand-side platforms (DSPs) to identify and filter invalid traffic (IVT) in programmatic advertising. Its technology classifies ad impressions as human, sophisticated invalid traffic (SIVT), or general invalid traffic (GIVT) to protect advertising spend and publisher monetization quality. Pixalate is accredited by the MRC (Media Rating Council) for its invalid traffic detection methodology.
What This Script Does
Pixalate's browser-side script performs visitor signal collection for traffic quality analysis:
Traffic quality signal collection
- Analyzes visitor interaction patterns: mouse movement trajectories, click timing, scroll behavior, and keyboard activity to distinguish human users from automated bots
- Measures interaction velocity and naturalness — bot traffic often exhibits unnaturally fast or perfectly timed interactions
- Collects browser environment signals: navigator properties, plugin enumeration, canvas fingerprinting signals, WebGL renderer, and audio context characteristics for device fingerprinting
- Checks for headless browser indicators (Puppeteer, Playwright, PhantomJS) by probing JavaScript APIs that differ between real browsers and headless environments
Ad viewability measurement
- Tracks whether ad units are visible within the browser viewport using Intersection Observer APIs
- Measures time-in-view for each ad impression against IAB viewability thresholds (50% of pixels visible for 1 continuous second for display; 50% visible for 2 seconds for video)
- Reports viewability rates per placement to the Pixalate dashboard for publisher optimization
Impression-level fraud reporting
- Tags each ad impression with a fraud risk score based on collected signals
- Classifies traffic into IVT categories defined by the MRC: data center traffic, known bot signatures, hijacked device behavior, and cookie stuffing patterns
- Reports are used by advertisers and agencies in post-campaign audit workflows to seek makegood credit for fraudulent impressions
Consent & Compliance
- Category: Analytics — Pixalate serves a fraud prevention and measurement function within the programmatic advertising ecosystem
- GDPR: Pixalate collects device-level signals including browser fingerprinting data, which constitutes personal data processing under GDPR. While the purpose (fraud detection) can support a legitimate interests claim, the browser fingerprinting techniques used are intrusive. Publishers and ad platforms deploying Pixalate should assess whether legitimate interests or consent is the appropriate basis — the Article 29 Working Party guidance suggests that device fingerprinting for advertising ecosystem purposes typically requires consent.
- IAB TCF: Pixalate is engaged in the programmatic advertising ecosystem and its data collection interacts with IAB TCF consent signals. Publishers using IAB TCF-compliant CMPs should review whether Pixalate's data collection is gated appropriately on consent signals.
- Data transfers: Pixalate is a US company headquartered in Santa Clara, California. Data is processed in the US. EU-US Data Privacy Framework applies for EU personal data transfers.
- MRC accreditation: Pixalate holds MRC accreditation for its desktop/mobile web, in-app, and CTV/OTT IVT detection services — a standard credential in the ad fraud measurement industry.
Should You Block This Without Consent?
Conditional. Pixalate is primarily used by publishers within programmatic advertising workflows rather than deployed directly by website operators. If Pixalate appears on your site, it is likely loaded by your ad stack (SSP, ad server, or header bidding wrapper) rather than a deliberate first-party integration. In that case, gate the entire ad stack — including Pixalate — on marketing/advertising consent. If deploying Pixalate explicitly for traffic quality reporting, treat it as an analytics tool requiring analytics consent given its browser fingerprinting data collection.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
adrta.comMarketingFrequently Asked Questions
Does Pixalate require consent before firing?
Conditional. Pixalate typically loads via the ad stack rather than as a direct integration. Gate the entire ad stack, including Pixalate, on marketing consent. If deploying Pixalate explicitly, treat it as analytics requiring consent given its device fingerprinting.
What signals does Pixalate collect for fraud detection?
Pixalate analyzes mouse movement, click timing, scroll behavior, and browser environment signals including canvas fingerprinting and WebGL renderer data to distinguish human visitors from bots. It also measures ad viewability using Intersection Observer APIs.
How does ConsentStack handle Pixalate?
ConsentStack gates Pixalate behind analytics or marketing consent, since its browser fingerprinting constitutes personal data processing under GDPR. ConsentStack blocks Pixalate from firing until the visitor has provided the appropriate consent category.
Related Vendors
Manage consent for Pixalate
ConsentStack automatically detects and manages Pixalate trackers so your site stays compliant with global privacy regulations.