comScore

Overview

comScore is one of the leading digital audience measurement companies, providing cross-media audience analytics used by publishers, broadcasters, advertisers, and media agencies worldwide. comScore's measurement data is used as a currency in media buying decisions — publishers use comScore ratings to demonstrate audience scale and demographics to advertising buyers, and agencies use comScore data for media planning and post-campaign verification. comScore measures digital audiences across desktop browsers, mobile web, mobile apps, connected TV, and streaming video. Its Unified Digital Measurement (UDM) methodology combines census-level tag data from publisher websites with panel-based demographic calibration to produce audience estimates.

What This Script Does

The comScore beacon script (sb.scorecardresearch.com/beacon.js) is placed on publisher pages and fires on every page load to contribute census-level measurement data.

Script file: beacon.js loaded from sb.scorecardresearch.com

Data transmitted per page view:

• Page URL (full URL including path, may include query parameters)
• Referrer URL (the previous page the visitor came from)
• Page load timestamp
• A hashed or encoded visitor identifier derived from comScore's cookie
• Publisher-configured metadata: content category, section, content ID, and custom labels used for content classification in comScore's reporting system

Cookies set:

• UIDR — third-party persistent cookie set from scorecardresearch.com, typically 13-month expiry, stores comScore's unique visitor identifier for cross-publisher audience deduplication and visit frequency measurement
• UID — companion persistent cookie also from scorecardresearch.com, used in comScore's unified measurement methodology
• First-party variants may be configured by publishers operating their own measurement tags to improve measurement in Safari's ITP environment

Cross-site data aggregation:

• comScore's methodology depends on the same UIDR cookie being read across multiple publisher sites to deduplicate audiences — the same visitor reading news on three different sites counts as one unique visitor in comScore's total digital audience figures
• This cross-publisher measurement is what makes comScore a third-party audience measurement service rather than a first-party analytics tool

Panel integration:

• comScore recruits opted-in panelists who consent to detailed monitoring; panel data calibrates the census-level tag data with demographic attributes
• Individual site visitors are not panelists — their data contributes to census-level counts without demographic enrichment at the individual level

Consent & Compliance

comScore falls under the analytics consent category and requires consent under the ePrivacy Directive due to its use of persistent third-party cookies for cross-publisher visitor identification. The UIDR cookie enables cross-site behavioral tracking — the same identifier appears across multiple unrelated publisher sites — which constitutes non-essential tracking requiring prior consent.

Under GDPR, comScore processes personal data (online identifiers) for audience measurement purposes that serve the advertising ecosystem. The data controller argument (that each publisher controls their own comScore tag) does not eliminate the consent requirement for the underlying cookie storage. Major European DPAs have consistently treated third-party measurement cookies as requiring consent.

Under CCPA/CPRA, data sharing with comScore for audience measurement purposes should be disclosed. comScore participates in the EU-US Data Privacy Framework and maintains IAB Europe TCF registration (Vendor ID: 77) with consent required for Purposes 1, 7, 8, and 9.

Should You Block This Without Consent?

Yes. comScore scripts set persistent third-party tracking cookies (UIDR, UID) for cross-publisher audience measurement. This is non-essential analytics processing that requires prior consent under ePrivacy. Block until analytics consent is granted.