Marketing tracking glossary
Plain-English definitions of the tracking-infrastructure terms digital marketing agencies work with every day — and why each one matters when you run tracking across a book of clients.
Core concepts
Tracking infrastructure
The full set of analytics properties, tags, pixels, conversion actions, and the data flows between them that capture a marketing campaign’s performance.
Tag management
Deploying and governing marketing/analytics tags (snippets of tracking code) through a single container instead of hard-coding each one into the site.
Data layer(dataLayer)
A structured JavaScript object on the page that holds the values (price, order ID, user state) tags read from, decoupling tracking from the site’s HTML.
Tracking pixel
A snippet of code (historically a 1×1 image, now usually JavaScript) that an ad platform loads to record visits, events, and conversions in the browser.
Event tracking
Recording specific user interactions (clicks, form submits, video plays, purchases) as named events with parameters, rather than just page views.
Conversion & attribution
Conversion tracking
Recording the actions that matter to the business (purchase, lead, signup) and attributing them back to the marketing that drove them.
Attribution modeling
The rules that decide which touchpoints get credit for a conversion when a customer interacted with several channels before converting.
Enhanced Conversions
A Google Ads feature that sends hashed first-party data (email, phone) with conversions to recover attribution lost to cookie and consent gaps.
Offline conversion tracking
Importing conversions that happen off the website (a closed sale, a qualified lead in the CRM) back into ad platforms so bidding optimizes for revenue, not form fills.
Measurement Protocol
GA4’s server-to-server API for sending events directly to a property without a browser — used for server-side events and offline data.
Conversions API(CAPI)
A server-to-server channel (Meta CAPI, TikTok Events API) that sends conversion events directly to an ad platform, alongside or instead of the browser pixel.
Privacy & first-party
Server-side tracking
Moving tag execution from the browser to a server you control (e.g. server-side GTM) for more reliable, privacy-durable, and controllable data collection.
Google Consent Mode v2
Google’s framework for adjusting how its tags behave based on a user’s consent choices — required to use Google Ads/Analytics features for EEA users.
First-party data
Data a business collects directly from its own customers and audiences (with consent) — the durable foundation for tracking as third-party cookies disappear.
Identifiers & routing
UTM parameters
Tags appended to a URL (utm_source, utm_medium, utm_campaign…) that tell analytics where a visitor came from.
Cross-domain tracking
Stitching a user’s session across multiple domains (e.g. a site and a separate checkout/booking domain) so they’re counted as one journey, not two visitors.
Call tracking
Attributing inbound phone calls to the marketing that drove them, so calls are measured and optimized like clicks and form fills.
Dynamic number insertion(DNI)
Swapping the phone number displayed on a website per visitor or traffic source so inbound calls can be attributed to the marketing that drove them.