privacy policy, security, data transfer, padlock, combination lock, cable, computer, digital, monitoring, privacy policy, privacy policy, privacy policy, privacy policy, privacy policy
Photo by ChristophMeinersmann on Pixabay

Supply Chain

Part of AdTech privacy and permission signals

Mapping permission signals through the ad supply chain

A permission signal can change meaning as it passes from a site to an advertising platform and downstream partners.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Supply Chain Desk.

What actually counts as a permission signal

A permission signal is a privacy choice rendered as machine-readable state: granted or denied, per purpose or per vendor, transmissible between systems without a human reading it. It is not the banner interaction, nor a request logged on a page. Only the encoded state travels; the click stays where it happened.

Framework strings carry that state. IAB Europe's Transparency and Consent String is published with a Global Vendor List format, so a string can express choices against a shared register of vendors rather than one site's list.

IAB Tech Lab's Global Privacy Protocol was designed to streamline the transmission of privacy, consent and consumer choice signals from sites and apps to ad tech providers. It supports the IAB Europe TCF, the IAB Canada TCF, the MSPA's US National string and a number of US state strings.

Consent mode is not a collection tool. It lets site owners adjust how Google tags behave based on the permissions users have given, and flags whether consent was granted for Google Analytics and Google Ads cookies. A consent collection system must already be in place upstream of it.

Mapping the handoffs, hop by hop

One page load can generate a large number of third-party requests. A sell-side column published by AdExchanger, written by Rebel AI founder and chief executive Manny Puentes, cited research putting the average page load on an ad-supported site at 172 network requests for advertising alone.

The fan-out is structural. Supply-side and demand-side platforms rarely fill all of a publisher's inventory, so they work with other platforms to fill a percentage of it, and every time one platform is called it may call others.

The column's example: on a page load, Amazon Associates may call OpenX, AppNexus and PubMatic, and PubMatic may in turn call The Trade Desk, RocketFuel and BrightRoll. Each link in that sequence is a hop where a signal is read, reinterpreted or dropped.

Each platform in the chain collects and stores audience data whether or not it fills the ad space. The signal therefore has to remain intelligible at every destination, not only at the first one to receive it.

Two dialects: encoded framework strings versus per-tag states

Framework strings carry granular, per-vendor choices and point at a shared vendor list. The TCF's Transparency and Consent String is published with a Global Vendor List format, and vendors and consent management platforms register against the framework.

Per-tag states are cruder. Consent mode pings communicate the default state configured by the site owner and the state — granted or denied — for each consent type, such as ad storage and analytics storage.

Mapping is the translation between the two dialects. A vendor entry in the vendor list has to be matched to the tags that destination actually runs, and a purpose-level choice has to be resolved into a storage flag for a single tag.

Publisher implementation choices surface at this point: which vendors are registered, which purposes map to which tags, and what default is sent before any choice is made.

Pixels are where permission meets the collection layer

A pixel or tag should only behave in line with the permission state that reached it. With Consent mode, Google tags react dynamically, using measurement tools for specific purposes only after permission has been given by the user.

The adjustments are concrete. Pings carry the default state set by the site owner and the granted or denied state for each consent type; when analytics or ads storage is denied, the associated measurement functions change behaviour. If a user does not consent to Ads cookies, tags will not use cookies for advertising purposes.

Consent mode with Ads does not switch off conversion tracking. It measures conversions that reflect the user's permission choices for third-party cookies.

In Australia, the OAIC publishes guidance on tracking pixels and privacy obligations, which places pixel deployment inside the same handling framework as other personal information.

Where the state never reaches a tag, browser monitoring tools show what actually fired. Publishers have used such tools to track data pixels on their site and chase down non-compliant partners.

Where signals decay along the way

Default states are the first decay point. A default is transmitted before the user has chosen, and the ping structure records it alongside the current granted or denied state for each consent type.

Mid-session flips are the second. Consent mode triggers some tags when the permission status changes from denied to granted and vice versa, so a reversal has to propagate to vendors already loaded on the page.

Destinations that cannot read the signal are the third. The Global Privacy Protocol carries several strings — IAB Europe TCF, IAB Canada TCF, the MSPA US National string and a set of US state sections — and a destination that parses only one dialect will miss the others.

The fourth is calls that leave without a matching permission. Each platform in a chain may call further platforms and collect and store audience data, whether or not it fills the ad space. Header bidding added more of those calls.

There is also interpretive risk. Belgium's data protection authority found in 2022 that the TCF did not give users meaningful control, and that the consent it generated was not specific, informed or freely given. The Court of Appeal later set that decision aside on procedural grounds while upholding the core findings.

The Court of Justice of the European Union held in March 2024 that Transparency and Consent strings qualify as personal data where IAB Europe or framework participants can reasonably use them to identify a person. A signal can itself be regulated data.

Key Stats on Consent Signal Transmission

Average Third-Party Requests
172
Signals Decaying at Default State
Before user consent is given
Court Ruling on TCF Signals
Qualifies as personal data under CJEU (March 2024)
Australian Privacy Guidance
Tracking pixels subject to OAIC privacy obligations

Turning the map into controls

Start with an inventory: the tags and pixels that fire, the platform each one calls, and the vendor-list entry each platform corresponds to. The TCF lists of registered vendors and registered consent management platforms, and the Global Vendor List, are the reference points for that matching.

Then confirm readability. Check that every destination can parse the string version it receives; the Global Privacy Protocol has been extended jurisdiction by jurisdiction, with new state sections moving from public comment to final release.

Test transitions, not just states. Flip from granted to denied and back, and confirm the tags react — consent mode triggers tags on a status change in either direction.

Monitor production pages with browser monitoring tools. Publishers have used them to track data pixels on their site and to chase down partners that fire without permission.

Contracts are a backstop rather than the control. Some publishers impose strict terms on who can collect their data and in some cases prohibit cookies for data capture, but enforcing those terms after a pixel fires is time-consuming and costly.

Re-run the map when the framework moves. String versions, state sections and vendor registrations change on a public comment and release cycle, and a mapping that is not refreshed drifts out of step with what the tags actually send.

More from Supply Chain

Supply Chain

Ad servers and creative delivery

Understand publisher and advertiser ad-server handoffs, creative delivery, counting differences and checks before a tag goes live.