What are tags, pixels, and the data layer in consent setups?
Terms you often see when wiring analytics, ads, and consent together. This is help text, not legal advice.
Tag (marketing / analytics)
Meaning: A snippet of code (often JavaScript) that runs in the browser to load a vendor script, send a hit, or set identifiers.
In practice: Many tags set cookies or read storage — that is why they are usually non-essential until consent allows them.
Pixel / beacon
Meaning: A tiny request (often a 1×1 image or fetch) used to record an event — page view, conversion, email open (in other contexts), etc.
In practice: Pixels can still carry identifiers or join data across sites; treat them like other tracking mechanisms for consent purposes.
Tracker / tracking
Meaning: Loosely, any tech used to measure behaviour or profile visitors across sessions or sites — analytics, ads, many embeds.
In practice: Your policy text and legal position decide what counts as “tracking” for you; technically, assume tags that talk to third-party domains need a clear consent story unless your lawyer says otherwise.
Data layer
Meaning: A structured JavaScript object (often dataLayer) where your site pushes events or variables before tags read them — common with Google Tag Manager and similar tools.
In practice: The data layer is not a cookie by itself, but it often feeds tags that set cookies or send personal data — align it with when those tags are allowed to run.
Server-side tagging / server container
Meaning: A pattern where the browser talks to your (or a vendor’s) server, and that server forwards events to analytics or ads APIs — sometimes reducing what runs directly in the visitor’s browser.
In practice: Server-side setups can change who is data controller/processor and what is still personal data — consent and privacy analysis still apply; follow your legal guidance and the vendor’s docs.
Fingerprinting
Meaning: Building a probabilistic identifier from browser signals (fonts, canvas, WebGL, headers) without a traditional cookie.
In practice: Many regimes treat fingerprinting like other tracking; do not use it to bypass consent choices.
ITP / ETP (Safari / Firefox)
Meaning: Intelligent Tracking Prevention (Safari) and Enhanced Tracking Protection (Firefox) — browser features that limit third-party cookies and sometimes partition storage.
In practice: Test your banner and tags in Safari; first-party flows and early consent initialization behave differently than in Chrome-only testing.
Last updated