Comscore / Scorecard Research
How to configure Comscore / Scorecard Research at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Support marketing analytics
Overview
This guide explains how to implement different privacy configurations for the Comscore Publisher Tag (Scorecard Research beacon) and how to reflect them in the Consenter Manager. It covers the index entries "comScore" and "Scorecard Research".
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. The Comscore Publisher Web Page Impression Tag for Media Metrix audience measurement (beacon to sb.scorecardresearch.com). Comscore, Inc. is a US company.
What the service does in this scope. The tag sends page impression data such as page URL, referrer, browser type and cookie values with each call. Consent for audience research is communicated with the cs_ucfr label (1 = consent, 0 = no consent, blank = no action); Comscore requires recipients to have an auditable consent trail. An optional publisher-specific first-party cookie _scor_uid is disabled by default; when enabled, it is set only with a consent signal from a CMP or cs_ucfr=1, unless the publisher sets bypassUserConsentRequirementFor1PCookie.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Higher risk | Publisher tag after consent with cs_ucfr=1; first-party cookie disabled (default). |
| Configuration B — Highest risk | As A, plus the first-party _scor_uid cookie enabled. |
No configuration without prior consent. The tag sends cookie values and is used for cross-publisher audience research. Do not use the consent-bypass setting for EU visitors; block the tag until consent.
Step 1 — Configure the Comscore tag
| # | Configuration area | Where to configure it | Configuration A — Higher risk | Configuration B — Highest risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Support marketing analytics | Support marketing analytics |
| 2 | Consent label | cs_ucfr in the tag (1 after consent) | 1 | 1 |
| 3 | First-party cookie | enableFirstPartyCookie | Off (default) | On |
| 4 | Consent bypass | bypassUserConsentRequirementFor1PCookie | Not set | Not set |
| 5 | Loading | Consenter script blocking | After consent | After consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Comscore, Inc. is a US company subject to the US CLOUD Act.
| Consenter Manager field | Configuration A — Higher risk | Configuration B — Highest risk |
|---|---|---|
| Processing purposes | Support marketing analytics | Support marketing analytics |
| Tracking method | Third party tracking (crosssession, cross-website) | Third party tracking (crosssession, cross-website) |
| Identifier | Device identifiers, IP address | Device identifiers, IP address |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers, IP address, Privacy choices | Same |
| Legal role of data recipient | Individual Controller | Individual Controller |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | Not documented |
| Processing location | United States | United States |
Privacy-policy follow-up
- Comscore as recipient for audience measurement; cookies (third-party Scorecard Research cookies;
_scor_uidin B); consent transmission; US transfer and potential access by US authorities.
Verification checklist
- No
scorecardresearch.comrequests before consent. - Requests carry
cs_ucfr=1after consent.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on