Cookie Consent or Browser Signal? The 14-Character Header That Decides Who Wins
Archi4 min read
Contents
Two ways to say no, one header that decides#
When you click "Reject all" on a cookie banner, your browser sends a request. When your browser is set to send a Global Privacy Control signal, it also sends a request. The difference between those two requests often comes down to a single HTTP header about 14 characters long: Sec-GPC: 1. That header is the smallest detail that matters in the fight over whether your privacy choice is respected.
The banner: visible, audited, inconsistent#
Cookie banners are the default compliance tool for most websites. The mechanics are familiar. A script loads, detects your region, and presents a dialog. You click a button. The script records your choice, usually in a cookie or local storage, and then passes that choice to the ad tech vendors on the page through a consent management platform (CMP).
The strength of this approach is that it produces a record. Regulators can ask for logs. Auditors can check whether the "reject" button actually blocks tracking scripts or just hides them. The weakness is that every site builds its own version. One banner might load tracking scripts before you click anything. Another might treat "reject" as a request to close the dialog while keeping the default ad partners active. A 2023 study of European sites found that a large share of banners loaded at least one tracking script before any consent was given, according to research from a team at KU Leuven.
The smallest detail that trips people up is the default. If the banner is configured to treat silence as consent, the absence of a click is the decision. That setting lives in the CMP configuration, not in the law, and it varies by vendor.
The browser signal: one header, no dialog#
The Global Privacy Control is a different approach. Instead of a dialog, your browser sends Sec-GPC: 1 with every request to a site. The signal is a statement: do not sell or share my personal information. It is legally enforceable in California under the CCPA, and regulators in other states have signaled similar expectations.
The strength is that it is automatic and consistent. You set it once in your browser, and every site that honors it gets the same message. There is no dialog to dismiss and no dark pattern to navigate. The weakness is adoption and verification. A site can receive the header and ignore it. There is no built-in enforcement mechanism at the protocol level. You cannot tell from the outside whether the signal was honored unless the site publishes a policy and you test it.
The smallest detail here is the header name itself. Sec-GPC is a structured field, and a server that strips unknown headers, or a proxy that rewrites them, can silently drop the signal. That means a privacy choice can vanish in transit without any error message.
CMPs in the middle: the translation problem#
Most sites do not handle either method directly. They use a consent management platform that sits between the browser and the ad tech vendors. The CMP's job is to translate your choice into something the vendors understand.
That translation is where the two methods diverge. A banner click is a local event. The CMP knows it happened and can record it. A Sec-GPC header is an inbound signal. The CMP has to read it, map it to a consent state, and pass that state to every vendor on the page. If the CMP does not support the header, the signal is ignored. If it supports the header but a vendor's script loads before the CMP initializes, the signal arrives too late.
The smallest detail that matters in this comparison is timing. A banner gives the CMP a clear moment to act: the click. A header gives the CMP a signal that must be processed before any tracking script runs. If the order is wrong, the choice is lost.
What to check before you trust either method#
For a site operator, the practical question is which method produces a defensible record. Banners produce logs, but the logs are only as good as the configuration. Browser signals produce consistency, but only if the server and the CMP both honor the header.
A few concrete checks:
, Does the banner load any tracking script before a choice is made? If yes, the default is doing the work, not the click., Does the server preserve the Sec-GPC header, or does a proxy strip it? Check the raw request, not the rendered page., Does the CMP map the header to a consent state that blocks ad partners, or does it only record the signal?
For a user, the check is simpler. Open the browser's developer tools and look at the request headers. If Sec-GPC: 1 is present and the site still loads ad trackers, the signal was not honored. That is the detail that matters, and it is visible in about 14 characters.
More articles