SEO tracking has its own dense vocabulary, and half the confusion beginners run into isn’t the concepts themselves — it’s that GA4, Google Tag Manager, and Search Console each use overlapping words to mean subtly different things. This glossary organizes the essential terms by category so you can look up a word in context rather than hunting through an alphabetical list, followed by answers to the questions we hear most often when clients are getting oriented.
Use this as a working reference rather than something to memorize in one sitting — even experienced practitioners look up the precise definition of terms like “engaged session” or “default channel group” when auditing an unfamiliar account, because platforms redefine these terms more often than most people realize.
These are the core systems most SEO tracking setups are built on. Understanding what each one is actually for prevents a common beginner mistake: trying to make one tool do a job that belongs to another.
Google’s current analytics platform, built around an event-based data model rather than the older session-and-pageview model of Universal Analytics. GA4 tracks user behavior across web and app properties and is the primary tool for measuring what happens after a visitor arrives from organic search.
A tag management system that lets you add and manage tracking code — including GA4, conversion pixels, and custom event tracking — without editing site code directly. GTM uses tags, triggers, and variables to decide what to track and when.
A free Google tool that reports how a site performs specifically in Google Search: which queries surface it, click-through rates, average position, indexing status, and technical issues like Core Web Vitals or mobile usability problems. GSC shows search-side data that GA4 cannot see on its own.
A free reporting and dashboard tool that connects to GA4, Search Console, and other data sources to build visual reports without requiring the viewer to log into each underlying platform separately.
An approach where tracking data is sent from a server (often via a server-side GTM container) rather than directly from the visitor’s browser, improving data accuracy against ad blockers and browser privacy restrictions, at the cost of more complex setup and maintenance.
These are the numbers that show up on nearly every dashboard, and they’re also the terms most often misread because their definitions changed between Universal Analytics and GA4.
A group of user interactions with a site that take place within a given time frame, typically ending after 30 minutes of inactivity. A single visitor can generate multiple sessions across a day if they leave and return.
A GA4-specific metric counting sessions that lasted longer than ten seconds, included a conversion event, or included at least two pageviews — GA4’s replacement for the old, less reliable bounce rate calculation.
The percentage of sessions that were “engaged” sessions, effectively the inverse of bounce rate. A higher engagement rate generally signals content that’s matching visitor intent.
A specific event marked as representing a meaningful business outcome — a form submission, phone click, or purchase. GA4 requires you to explicitly mark events as conversions (referred to in newer interface versions as “key events”); it does not decide this automatically.
GA4’s automatic categorization of traffic sources into buckets like Organic Search, Direct, Referral, and Paid Search, based on the URL parameters and referrer data available at the time of the visit.
The rule set determining which touchpoint gets credit for a conversion when a user interacted with multiple channels before converting. GA4 defaults to a data-driven attribution model that distributes credit across touchpoints rather than crediting only the last click.
Search Console reports on the search-side of the funnel — what happens before a click, and how Google’s crawlers see the site — using its own distinct vocabulary.
The number of times a site’s link appeared in Google search results for a query, regardless of whether it was clicked. High impressions with low clicks often signals a title or meta description problem, not a ranking problem.
The percentage of impressions that resulted in a click, calculated as clicks divided by impressions. CTR benchmarks vary enormously by average position and query intent, so it’s most useful compared against a page’s own history rather than an industry average.
The average ranking position a page held across all the impressions it received for a given query or page, blended across every recorded search where the page appeared, including positions far down the results.
Search Console’s report on which URLs have been crawled and indexed, and which have been excluded, along with the reason for exclusion — critical for diagnosing why a page isn’t appearing in search at all.
These terms describe how tracking is technically wired together, and they’re the concepts that trip up beginners moving beyond basic installation.
In Google Tag Manager, a snippet of tracking code — a GA4 configuration tag, a conversion pixel, a custom HTML tag — that fires when its associated trigger condition is met.
The condition that tells a tag when to fire, such as a specific page loading, a button being clicked, or a form being submitted.
A structured JavaScript object on a webpage that passes information — like a transaction value or a form type — from the site itself to Google Tag Manager, allowing tags to fire based on data the site provides rather than guessing from page structure alone.
Tags appended to a URL (utm_source, utm_medium, utm_campaign, and related parameters) that let you manually label traffic sources, most often used for tracking non-organic channels like email or paid social where automatic detection isn’t reliable.
A GA4 configuration that stitches together a user’s session when they move between two different domains — for example, a main website and a separate booking platform — so the journey isn’t incorrectly split into two disconnected sessions.
A user-defined data point — like a membership tier, a location identifier, or a content category — that GA4 doesn’t track by default but that you configure to capture and report on for more granular analysis.
A newer set of terms has entered the tracking vocabulary as AI answer engines and generative search features have become sources of referral traffic, and they’re not yet standardized the way older analytics terms are.
Google’s AI-generated summary that appears above traditional search results for many queries, sometimes citing sources with a link. Clicks originating from an AI Overview citation typically appear in GA4’s organic search channel, though Google does not currently break this out as a separate, labeled channel.
Sessions arriving from AI chat tools like ChatGPT or Perplexity that cited a site as a source. This traffic usually shows up under Referral or a specific source name in GA4’s channel reports and is worth isolating in a custom segment since its volume and behavior differ from traditional referral traffic.
An emerging, informal term for how often a brand or site is mentioned or cited by AI answer engines for relevant queries — a concept analogous to search visibility or share of voice, but measured through AI platforms rather than traditional SERPs, and not yet something GA4 or Search Console report on natively.
Search Console shows how a site performs within Google Search itself — impressions, clicks, and rankings before a visit happens — while GA4 shows what visitors do after they arrive on the site, so the two tools answer different halves of the same question and work best used together.
Only for reading historical reports or older documentation, since Universal Analytics was fully retired in favor of GA4; new setups should be built entirely on GA4's event-based model and its own vocabulary of events, engaged sessions, and key events.
GA4's entire data model is event-based rather than pageview-based — a pageview, a scroll, a click, and a purchase are all logged as events with different names and parameters, which is a deliberate architectural shift from Universal Analytics and explains why so many GA4-specific terms reference events.
Each platform defines conversion-adjacent terms based on what it can measure: GA4's conversions are user actions on your site, Search Console has no conversion concept at all since it only sees search behavior, and ad platforms define conversions based on their own pixel or tag data — so cross-platform reporting requires knowing which definition each number is using.
Not for simple tracking like page views or button clicks, which GTM can typically capture without a custom data layer, but a data layer becomes necessary for accurately tracking more complex events like ecommerce transactions or multi-step form submissions.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
This guide is one lesson from the SEO Tracking & Analytics Setup course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.