Overview
Integral Ad Science (IAS) is a global ad verification, brand safety, and viewability measurement company used by both publishers and advertisers. Publishers integrate IAS to prove the quality of their ad inventory; advertisers use IAS to ensure their ads appear in brand-safe environments, are actually seen by humans, and are not served next to inappropriate content.
IAS operates alongside ad serving infrastructure — its scripts fire in parallel with ad tags to score each impression in real time. The company is publicly traded (Nasdaq: IAS) and processes hundreds of billions of ad impressions globally each month. In 2022, the FTC investigated but ultimately did not take action on allegations around measurement discrepancies.
What This Script Does
IAS scripts (cdn.adsafeprotected.com/iasPET.js, pixel.adsafeprotected.com) deploy alongside ad serving and fire on every page where ads are being served:
Viewability measurement: IAS uses Intersection Observer APIs and timing measurements to determine whether each ad unit was actually viewable — defined by the MRC standard as at least 50% of the ad in viewport for at least one continuous second (two seconds for video). These measurements are reported back to IAS servers and surfaced in publisher and advertiser dashboards.
Invalid traffic (IVT) detection: IAS analyzes browser characteristics, interaction patterns, and network signals to score each impression for invalid traffic. This includes general IVT (GIVT — known bots, data center traffic) and sophisticated IVT (SIVT — harder-to-detect fraud). Signals collected include mouse movement patterns, scroll behavior, browser fingerprint, IP reputation, and timing anomalies.
Brand safety and suitability classification: IAS crawls and classifies page content against the GARM brand safety framework and IAB content taxonomy. The on-page script contributes URL and contextual signals. Classification results determine whether the page is suitable for specific advertiser categories (finance, pharma, CPG, etc.).
Cookie and storage usage: IAS sets cookies under the adsafeprotected.com domain for session and measurement purposes. Cookie names include _iasPET, IAS_IDS, and related identifiers. These are third-party cookies from the perspective of publisher sites. IAS participates in the IAB TCF (Transparency and Consent Framework) and reads TCF consent signals — IAB Purpose 7 (Measure ad performance) and Purpose 8 (Measure content performance) are most relevant.
Data transmission: Measurement events are beaconed to pixel.adsafeprotected.com and fw.adsafeprotected.com. IAS is certified under the EU-US Data Privacy Framework.
Consent & Compliance
IAS falls under the analytics consent category for consent management purposes:
- GDPR / ePrivacy: IAS sets third-party cookies and collects device-level signals (browser fingerprint, interaction patterns). Under the ePrivacy Directive, this requires prior opt-in consent. IAS participates in IAB TCF 2.x — its processing relies on IAB TCF Purpose 7 (ad measurement) and Purpose 8 (content measurement). Without TCF consent signals, IAS can operate in a limited cookieless mode but with reduced measurement capability.
- CCPA/CPRA: IAS's collection of device identifiers and behavioral signals qualifies as collection of personal information. Publishers and advertisers should ensure their privacy policies disclose IAS measurement.
- Brand safety vs. targeting: IAS primarily serves verification rather than user targeting, but the legal analysis under ePrivacy focuses on what data is collected and how, not on the purpose. Cookie-based measurement requires consent regardless of whether it is used for targeting.
Should You Block This Without Consent?
Conditional. IAS serves a legitimate ad verification and fraud prevention function rather than behavioral targeting. However, it sets third-party cookies and collects device-level signals, which require ePrivacy consent. If your ad stack depends on IAS for fraud detection, check whether your IAS configuration supports cookieless or consent-conditional operation. Otherwise, block alongside other ad-related scripts until consent is obtained.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
adsafeprotected.comMarketingFrequently Asked Questions
Does Integral Ad Science require cookie consent on publisher websites?
Yes. IAS sets third-party cookies under adsafeprotected.com and collects device-level signals including browser fingerprint and interaction patterns for ad viewability and invalid traffic measurement. These are not strictly necessary and require ePrivacy opt-in consent. IAS participates in IAB TCF 2.x for consent signal integration.
What does the IAS script measure on a publisher page?
IAS measures whether ads were actually viewable (MRC standard: 50% in viewport for 1+ seconds), scores impressions for invalid traffic and bot activity using browser interaction signals, and classifies page content for brand safety against the GARM framework. Measurement beacons are sent to pixel.adsafeprotected.com.
How does ConsentStack handle Integral Ad Science in a publisher consent setup?
ConsentStack gates IAS scripts behind analytics consent and integrates with IAB TCF 2.x to pass Purpose 7 and Purpose 8 consent signals. If consent is denied, ConsentStack blocks the IAS pixel. Publishers can optionally configure a cookieless IAS mode through ConsentStack for non-consenting visitors to retain partial measurement.
Related Vendors
Manage consent for Integral Ad Science
ConsentStack automatically detects and manages Integral Ad Science trackers so your site stays compliant with global privacy regulations.