Join our Newsletter — 33% off our NHI Course
Home› Guides› IAB TCF and Global Privacy Control Signals Guide:…
Guide Privacy & Data Protection

IAB TCF and Global Privacy Control Signals Guide: Implementing and Honouring Consent Signals Correctly

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, under the editorial direction of Lalit Choda Updated 27 October 2026 13 min read
On this page

Consent and opt-out signals only protect anyone if every tag, pixel and server on the page actually reads and obeys them, and in practice many do not. Two signal systems dominate: the IAB Europe Transparency and Consent Framework (TCF), which carries EU-style consent choices through the advertising chain as a TC String, and Global Privacy Control (GPC), a browser signal that US state regulators treat as a valid request to opt out of sale and sharing. This guide explains how each signal is encoded and transmitted, what regulators have said about honouring them, how to implement and test them, and the failures that lead to enforcement. It is for privacy engineers, web and ad operations teams, and security reviewers responsible for client-side code. For cookie banners and consent platforms in general, see the Consent Management Guide. This guide summarises legal requirements and is not legal advice.

Status checked 27 October 2026: TCF v2.3 is the current version (launched April 2025, adoption deadline 28 February 2026, per IAB Europe); the California CCPA regulations shown by the CPPA are those effective 1 January 2026; Colorado recognises GPC as a universal opt-out mechanism from 1 July 2024. Check the cited sources for later changes.

Key takeaways

  • TCF and GPC solve different problems. The TCF records opt-in consent and legitimate interest choices per purpose and per vendor for GDPR and ePrivacy; GPC is a single opt-out preference for sale, sharing and cross-context targeted advertising.
  • GPC is a legal signal in several US states. California's regulations require businesses that sell or share personal information to treat a qualifying opt-out preference signal as a valid opt-out, and Colorado names GPC as its recognised universal opt-out mechanism.
  • Ignoring GPC has already been punished. California's Attorney General settled with Sephora for $1.2 million in August 2022, alleging it did not process opt-outs sent through user-enabled global privacy controls.
  • TCF v2.3 changed the string. The Disclosed Vendors segment is now mandatory, and since v2.2 legitimate interest cannot be relied on for personalised ads and content purposes 3 to 6.
  • The hard part is enforcement in code. Tags that fire before the CMP loads, server-side integrations that never see the signal, and pixels that drop the consent macro are the usual failures; test them like security controls.

The two signal systems compared

AspectIAB Europe TCFGlobal Privacy Control
PurposeHelp parties in the advertising chain comply with GDPR and the ePrivacy Directive when processing personal data or accessing device storageExpress a preference that data not be sold or shared, or used for cross-context targeted advertising
ModelOpt-in consent and legitimate interest, per purpose, special feature and vendorSingle opt-out preference, on or absent
Who sets itA registered Consent Management Platform (CMP) on the publisher's site or appThe user's browser or extension
TransportTC String via the CMP JavaScript API (__tcfapi), URL macros (gdpr, gdpr_consent) and bid requestsHTTP request header Sec-GPC: 1 and the JavaScript property navigator.globalPrivacyControl
Site declarationVendors register on the Global Vendor List (GVL) with their purposes and legal basesOptional /.well-known/gpc.json with gpc and lastUpdate
Main legal hookGDPR and ePrivacy consent requirements in the EU and EEAUS state opt-out rights (for example California and Colorado); the specification notes GDPR Articles 7 and 21 may potentially apply
Not designed forUS opt-out signallingDeletion rights or limiting same-context collection

How the TCF works

The TCF specification, maintained by IAB Tech Lab for IAB Europe, defines the TC String, the CMP API and the Global Vendor List. Key elements:

  • TC String structure: a URL-safe base64-encoded string that must contain a Core segment and the Disclosed Vendors segment, and may contain a Publisher TC segment. The core records consent and legitimate interest signals per purpose (for example the PurposesConsent bit field, where purpose 1 maps to the first bit), special feature opt-ins, vendor consents and publisher restrictions.
  • Scope: CMPs must operate service-specific or group-specific configurations. Global scope and the shared consensu.org cookie were deprecated, and since 1 September 2021 TC Strings established with global scope are considered invalid.
  • Purpose 1: "store and/or access information on a device". The PublisherCC and PurposeOneTreatment fields tell vendors where the publisher operates and whether purpose 1 was disclosed, because jurisdictions treat it differently.
  • v2.2 changes (May 2023): reliance on legitimate interest was prohibited for purposes 3 (create a personalised ads profile), 4 (select personalised ads), 5 (create a personalised content profile) and 6 (select personalised content), and the getTCData API command was deprecated in favour of addEventListener.
  • v2.3 changes (April 2025): the Disclosed Vendors section became mandatory to remove ambiguity about vendors that declare only special purposes.
  • Re-prompting: the specification refers to DPA guidance on reminding users of their choices as appropriate and at least every 13 months, and Created and LastUpdated now hold the same day-level timestamp.

The CMP API: __tcfapi(command, version, callback, parameter) must always be a function, even during initialisation. CMPs must support ping, addEventListener and removeEventListener, and must proxy postMessage calls from nested iframes. Scripts should register a listener and act only when eventStatus is tcloaded (a valid existing string) or useractioncomplete (the user has just confirmed choices), not on cmpuishown.

Pixels and URL-based services: services that cannot run JavaScript receive the string through macros. The specification's example is gdpr_consent=${GDPR_CONSENT_123} for vendor ID 123, plus gdpr=${GDPR} to state whether GDPR applies. Any caller with the string must insert it.

Legal context: on 7 March 2024 the Court of Justice of the EU ruled in Case C-604/22 (IAB Europe) on whether the TC String is personal data and whether IAB Europe is a joint controller. The Court held that a TC String is personal data where it can, by reasonable means, be associated with an identifier such as the IP address of the user's device, so treat the string itself as personal data. It also held that a sectoral organisation such as IAB Europe can be a joint controller where it influences the processing for its own purposes, even without direct access to the data, but that this does not extend automatically to later processing by publishers and other third parties. The v2.2 changes followed an action plan submitted to and validated by the Belgian data protection authority, according to IAB Europe.

How Global Privacy Control works

The GPC specification (developed in the W3C Privacy Working Group repository) is deliberately small:

  • Header: when the preference is on, the user agent sends Sec-GPC: 1 with requests. The value must be exactly "1"; servers ignore any other value. Intermediaries must not remove a "1" value.
  • JavaScript: navigator.globalPrivacyControl is a read-only boolean, true when the header would be sent, fixed at navigation time, available in window and worker contexts.
  • Support resource: a site may publish /.well-known/gpc.json as application/json with "gpc": true (the site intends to honour GPC at least as far as legally required) and a lastUpdate date. It states support, not whether a particular request was honoured.
  • Disclosure: the specification says publishers that accept the signal should disclose how they handle it and how they resolve conflicts with other choices the person has made.

What regulators require

JurisdictionRequirementSource
California (CCPA regulations, 11 CCR § 7025, effective 1 January 2026 version)A business that sells or shares personal information must process a signal in a commonly used format (such as an HTTP header field or JavaScript object) as a valid request to opt out of sale and sharing, for that browser or device and associated profiles, including pseudonymous ones, and for the consumer if known. It may not require extra information to honour it. If the signal conflicts with a business-specific setting that allows sale, the signal still applies; the business may ask for consent under § 7004CPPA regulations text
California privacy policy (§ 7011(e)(3)(F))Explain how an opt-out preference signal will be processedCPPA regulations text
California enforcementSephora: $1.2 million settlement (24 August 2022) for not processing GPC opt-outs; required to honour GPC and report on its effortsCalifornia Attorney General
Colorado (Colorado Privacy Act)From 1 July 2024, businesses meeting CPA thresholds must let consumers opt out of sale or targeted advertising through GPC, the only universal opt-out mechanism currently recognised (C.R.S. § 6-1-1306(1)(a)(IV); 4 CCR 904-3, Part 5; Rule 5.07)Colorado Attorney General
Other US statesThe GPC specification notes that at least four US states have identified GPC as valid for opt-out rights; check each state's current lawGPC specification; see the US State Privacy Laws Guide
EU and EEAConsent for device storage and access under the ePrivacy Directive and valid GDPR consent where consent is the basis; the TCF is an industry framework to help, not a legal safe harbourIAB Europe; see the ePrivacy Directive Guide

Choosing what to implement

  • EU and UK audiences with programmatic advertising: a registered TCF CMP is effectively required by the ad supply chain. Configure it for v2.3, keep the vendor list short, and make sure non-TCF tags are also gated.
  • US audiences where you sell or share data or run cross-context targeted ads: honour GPC in California, Colorado and other states that recognise it. Many organisations apply GPC nationally because geolocation is unreliable and the cost of honouring is low.
  • Global sites: run both. Treat a GPC signal as an objection signal in EU flows too where your counsel agrees, and never let a TCF consent override a GPC opt-out in a US state that requires the signal to be honoured unless the consent process meets the state's rules.
  • Small sites without advertising technology: if you do not sell or share data, you may need neither; publish a clear policy, and consider /.well-known/gpc.json only if you actually honour the signal.

Implementation: a phased rollout

  1. Inventory every tag and data flow. List client-side tags, pixels, SDKs and server-side integrations that sell, share or use data for targeted advertising, and how each receives consent state. See the Client-Side Security Guide for tag governance.
  2. Load the consent layer first. Place the CMP stub with __tcfapi before any other tag, and block all non-essential tags until tcloaded or useractioncomplete.
  3. Read GPC at both layers. Check navigator.globalPrivacyControl in the browser and the Sec-GPC header on the server, and record the opt-out against the browser profile and, if known, the account.
  4. Propagate the decision. Pass TC Strings in URL macros and bid requests, and pass a do-not-sell or restricted processing flag to server-side partners when GPC is present.
  5. Handle conflicts and display status. Implement the California rule that the signal wins over a prior business-specific setting unless the consumer gives valid consent, and show the consumer's opt-out status.
  6. Update disclosures. State in the privacy policy how GPC is processed (California § 7011) and publish gpc.json if you honour it.
  7. Test in staging, then production. Use a browser with GPC enabled and a fresh profile, capture network traffic, and confirm no restricted tag fires. Repeat for reject-all and accept-all TCF choices. Rollback is reverting the tag manager container to the previous published version, but keep the opt-out records already captured.

Detection and measurement

  • Automated scans: scheduled headless browser runs with GPC on and with TCF reject-all, recording every third-party request; any request to an advertising vendor is a defect.
  • Server logs: share of requests carrying Sec-GPC: 1, and whether those sessions were flagged as opted out downstream.
  • TC String validation: sample strings for the mandatory Disclosed Vendors segment and correct policy version.
  • Evidence for regulators: keep dated scan results, tag manager change history and the opt-out records themselves. The Sephora settlement required reports to the Attorney General on efforts to honour GPC, so expect to show, not just state, that the signal works.
  • Change control: alert when a new tag is published to the tag manager without a consent classification, because most regressions arrive with routine marketing changes.

Metrics:

  1. Percentage of GPC sessions with zero requests to sale or sharing vendors (target 100 per cent).
  2. Number of tags firing before consent state is available (target zero).
  3. Percentage of pixels and URL integrations carrying the gdpr_consent macro.
  4. Time from a new tag request to consent classification and approval.
  5. Number of vendors on the CMP list without an active contract or business owner.

Common failure patterns

  • Treating GPC as optional: the Sephora settlement shows regulators check whether the signal changes data flows, not whether a policy mentions it.
  • Tags firing before the CMP: hard-coded scripts outside the tag manager load before consent state exists.
  • Server-side blind spots: conversion APIs and data feeds that run on the server never check the signal, so a client-side block is undone server-side. California's rule applies the opt-out to the browser, associated profiles and the known consumer, which server systems must carry forward.
  • Using deprecated TCF features: calling getTCData or still relying on legitimate interest for purposes 3 to 6 after v2.2.
  • Dropped macros: pixels and redirects that strip the gdpr_consent parameter, so vendors receive no signal.
  • Declaring without doing: publishing gpc.json with "gpc": true while tags still fire.

Framework mapping

FrameworkReferenceHow it applies
NIST SP 800-53 Rev 5PT-4 Consent; PT-5 Privacy NoticeCapturing and honouring choices, and disclosing signal handling
NIST SP 800-53 Rev 5PT-2 Authority to Process PII; PT-3 PII Processing PurposesPurpose-level control that the TCF encodes
NIST SP 800-53 Rev 5SA-8 Security and Privacy Engineering PrinciplesBuilding signal handling into tag and data architecture
NIST CSF 2.0GV.OC-03; ID.AM-03Legal requirements understood; data flows to third parties mapped
ISO/IEC 27001:2022 Annex A5.34 Privacy and protection of PIIMeeting privacy requirements in web and ad systems

Practitioner checklist

  • Inventory all tags, pixels, SDKs and server-side partners that sell, share or target ads.
  • Load the CMP stub first and gate every non-essential tag on TCF event status.
  • Confirm the CMP is on TCF v2.3 with the Disclosed Vendors segment, and no legitimate interest for purposes 3 to 6.
  • Read Sec-GPC and navigator.globalPrivacyControl and apply the opt-out to browser, profile and known account.
  • Pass consent and opt-out state to server-side integrations and in URL macros.
  • Update the privacy policy to explain GPC processing; publish gpc.json only if honoured.
  • Run automated GPC-on and reject-all scans after every tag change.
  • Review vendor lists quarterly and remove unused vendors.

Standards and references

Related NHI Mgmt Group resources: Consent Management Guide · Cookie and Tracking Technology Compliance Guide · US State Privacy Laws Guide · ePrivacy Directive Guide. This guide summarises TCF and GPC requirements and is not legal advice.

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick both boxes to continue.