Every term you need to navigate the marketing analytics landscape — clearly defined with practical context for practitioners.
A rule or set of rules that determines how credit for conversions is assigned to touchpoints in conversion paths. Common models include last-click, first-click, linear, time-decay, and data-driven attribution.
The time period after a user interacts with an ad during which a conversion is credited to that interaction. Also known as a lookback window. Common windows include 7-day click, 1-day view, and 30-day click.
A set of protocols that allows different software applications to communicate. In marketing measurement, APIs enable direct server-to-server data transfer — the backbone of server-side tracking and Conversions APIs.
In server-side Google Tag Manager, a client is the component that receives incoming HTTP requests. Clients parse the request data and make it available to tags. Examples include the GA4 client, which receives pings from gtag.js, and the Universal Analytics client.
The traditional method where tracking code runs directly in the user's browser (JavaScript). Data is sent from the user's device to third-party endpoints. This approach is increasingly limited by browser restrictions, ad blockers, and privacy regulations.
Google's framework that adjusts how Google tags behave based on user consent choices. Consent Mode v2 (required by the EU Digital Markets Act) introduces two new parameters — ad_user_data and ad_personalization — that must be signaled to Google.
Facebook/Meta's server-side API that allows advertisers to send web events directly from their server to Meta. It bypasses browser restrictions and improves data reliability, match rates, and attribution accuracy compared to the Meta Pixel alone.
A small piece of data stored on the user's browser by a website. First-party cookies are set by the domain the user visits; third-party cookies are set by other domains (like ad platforms). Third-party cookies are being phased out across major browsers.
A secure environment where multiple parties can combine and analyze first-party data without exposing raw user-level data to each other. Used for privacy-safe audience matching and measurement across platforms.
A JavaScript object that stores structured data about the page, user actions, and ecommerce events in a standardized format. It acts as the bridge between your website and your tag management system, ensuring consistent, reliable data.
The path data takes from source to destination. In server-side tracking, the data stream flows: browser → your server container → marketing/analytics endpoints, rather than browser → dozens of third-party endpoints directly.
Data collected directly from your audience through owned channels (website, app, CRM) with explicit consent. Considered the gold standard for privacy-compliant marketing as it doesn't rely on third-party intermediaries.
When your server-side container runs on a subdomain of your main website (e.g., sgtm.yoursite.com), cookies set by the container are treated as first-party. This is critical for bypassing ITP and other browser tracking restrictions.
Google's latest analytics platform built on an event-based data model. Unlike Universal Analytics, GA4 is designed for a cookieless future and supports both client-side and server-side data collection natively.
A tag management system that allows marketers to deploy and manage tracking tags without modifying website code. Available in two flavors: client-side (web container) and server-side (server container).
Google's protocol that allows developers to send data directly to Google Analytics via HTTP requests. The foundation of server-side GA4, enabling events to be sent from any internet-connected device or backend system.
Google's initiative to create privacy-preserving alternatives to third-party cookies and cross-site tracking. Includes proposals like the Topics API, Protected Audiences, and Attribution Reporting API.
Processing marketing tags on a server you control rather than in the user's browser. Data flows from your website to your server container, which then distributes it to marketing and analytics endpoints. This improves data quality, site performance, and privacy compliance.
The cloud-hosted environment (typically on Google Cloud Platform or a custom hosting provider) that runs your server-side GTM instance. It receives incoming requests, processes them via clients, and routes data to configured tags.
Configuring your server-side container to run on a subdomain of your main site (e.g., sgtm.yoursite.com). This ensures cookies are treated as first-party, preserving tracking capabilities that would otherwise be blocked.
In server-side GTM, a tag is the component that sends processed data to a destination — like GA4, Facebook CAPI, Google Ads, or a custom endpoint. Tags run on your server, not in the user's browser.
A condition that determines when a tag should fire. In server-side GTM, triggers can be based on incoming request data, event names, or custom conditions defined in the server container.
Data that a customer intentionally and proactively shares with a brand — such as preferences, purchase intentions, or personal context. Unlike first-party data (inferred from behavior), zero-party data is explicitly volunteered by the user.