Tracking Jargon Explained in Plain Language
Anyone working in tracking uses words like container, pixel, and consent mode all day long. For a client walking into that conversation, it quickly sounds like a different language. This glossary explains the most common terms without detours, so you can explain them yourself to someone who does not work with this daily.
This is part of our series for tracking and data specialists. See the full overview here: Server-Side Tracking for Tracking & Data Specialists.
The building blocks: GTM, containers, and tags
Google Tag Manager (GTM) is the tool used to manage measurement code (tags) on a website or in an app, without a developer having to dig into the source code every time. You set everything up inside GTM, and GTM makes sure the right code fires at the right moment.
A container is the collection of settings that belongs to one website or app. Inside that container sit tags (the bits of code that do something, like reporting a conversion to Google Ads), triggers (the condition that decides when a tag fires, such as "on form submit"), and variables (the data a tag needs, like a price or a customer ID).
The data layer is a kind of middle layer on the website that makes data available to GTM. Instead of GTM having to search the page itself for a price or product name, it simply reads that value from the data layer.
Web versus server: where the work happens
Client-side tracking is the classic approach: the measurement code runs in the visitor's own browser. This is how tracking has worked for years, and it is where most GTM containers start out by default.
Server-side tracking moves part of that work to a server you control, sitting between the browser and platforms like GA4 or Meta. Data goes to that server first, and the server forwards it from there. That gives you more control over exactly what gets sent, and makes tracking less dependent on what a browser does or does not allow.
The distinction between a web container (which runs in the browser) and a server container (which runs on your own server) comes from this. Both work together within the same GTM account, just in different places.
For more information about the difference between client-side and server-side tracking, check out Client-Side vs Server-Side Tracking, Explained.
Cookies and privacy
A cookie is a small piece of data a website stores in a visitor's browser, for example to remember that someone is already logged in or which pages they visited earlier.
A first-party cookie is set by the website the visitor is actually on. A third-party cookie is set by a different domain, such as an advertising platform. Browsers like Safari now block third-party cookies by default, which is a large part of why server-side tracking has become popular.
ITP (Intelligent Tracking Prevention) is the name of Apple's system in Safari that blocks third-party cookies and shortens the lifespan of first-party cookies. It is one of the main reasons tracking data looks different on iPhones and iPads compared to other devices.
Consent Mode is Google's way of indicating whether a visitor has given consent for tracking, and adjusting measurement accordingly. Without consent, data is simplified or estimated rather than measured directly, so you stay within privacy rules as an agency or website owner.
Measuring what works
A pixel is, at its core, the same thing as a tag: a piece of code that tells a platform like Meta or LinkedIn that something happened, such as a purchase or a page view. The name comes from when this was literally an invisible one-pixel image.
A Conversions API (CAPI) is a way of passing those same events not through the browser, but directly from server to server. That makes measurement less sensitive to ad blockers and browser restrictions, and it is exactly where server-side tracking proves its value.
Deduplication prevents a single event from being counted twice when it arrives both through the browser and through a server-to-server connection. Without proper deduplication, you might count one purchase twice, making a campaign look like it is performing better than it actually is.
Attribution is the process of crediting a conversion to the ad, search query, or page that led to it. And UTM parameters are the bits of text you add to a link (like ?utm_source=newsletter) so you can see exactly where a visitor came from.
Where TrackLead fits
These terms are the everyday language of tracking, but most clients do not need to know them. What matters is that the configuration behind them is correct: that tags fire at the right moment, that consent is passed through properly, and that a conversion is not counted twice or missed entirely.
TrackLead automates exactly that configuration for server-side tracking, including consent, deduplication, and the connections to platforms like GA4, Meta, and Google Ads. That way you do not have to check every time whether everything is set up correctly, and you can just use this glossary to explain it to a client.