Google Analytics Glossary – Beginner’s Guide to Google Analytics – Moz

Welcome to the wonderful world of Google Analytics 4 (GA4), where everything is an “event,” nothing is called what you think it’s called,
and the numbers are innocent until proven guilty. If you’ve ever stared at a GA report thinking, “Is a session a person… or a vibe?” you’re in
the right place.

This beginner-friendly Google Analytics glossary is organized like a real human would learn it: from the big building blocks (accounts and
properties) to the stuff you actually care about (traffic sources, engagement, and whether your marketing worked). It’s inspired by the “teach-me-like-I’m-new”
spirit you’d expect from a Moz-style beginner’s guide, but rewritten fresh with modern GA4 realities.

Why a Google Analytics Glossary Still Matters in GA4

GA4 is powerful, but it’s also a little like ordering coffee in a new city: the menu looks familiar, the words are the same, and yet somehow your “regular”
is now called a “double-shot oat flat white with event parameters.” A glossary helps you:

• Read reports correctly (so you don’t panic over “bounce rate” like it’s 2016).
• Communicate clearly with clients, bosses, or teammates who love dashboards more than sunlight.
• Build better tracking (because naming your event “button_click_2_FINAL_v7” is a cry for help).

The GA4 Glossary, Organized Like a Human Brain

1) Setup & Structure Terms (The “Where Does This Data Live?” Bucket)

Account The top-level container in Google Analytics. Think “company” or “organization.” One account can contain multiple properties.

Property The place where data gets collected and reported. Usually one website or app (or one brand’s digital ecosystem). Most of your GA4
work happens at the property level.

Data Stream A source of incoming data inside a GA4 property (e.g., Web, iOS app, Android app). Each stream has its own settings and identifiers.

Measurement ID The ID tied to a GA4 web data stream (looks like G-XXXXXXXXXX). It tells tags where to send data.

Tag A snippet of code (or configuration in a tag manager) that sends data to GA4. Commonly installed via gtag.js or Google Tag Manager.

gtag.js Google’s global site tag, a JavaScript tagging framework that can send events to GA4 (and other Google products).

Google Tag Manager (GTM) A tag management system that helps you deploy and manage tracking without constantly editing site code. It’s like
a remote control for your measurement setup (and, yes, you can still lose it in the couch).

Enhanced Measurement GA4’s built-in tracking for common behaviors (like page views, scrolls, outbound clicks, site search, file downloads)
that you can enable in the web data stream settings.

Consent Mode A Google framework that adjusts how tags behave based on user consent choices. Helpful for privacy compliance and measurement
continuity (especially when cookies aren’t guaranteed).

2) Users, Sessions, and Engagement (The “Who Came and What Happened?” Bucket)

User An individual visitor (as best as GA can determine). Users are identified via signals like device identifiers and cookies, so user
counts are “best effort,” not magic.

New User A user who visits for the first time (or appears as first-time based on identifiers). Great for measuring growth and awareness.

Active User In GA4, “Users” often means active users in many standard reports: people who engaged with your site/app in a meaningful way
during the selected date range.

Session A group of user interactions within a given time window. In plain English: one visit (even if it includes multiple events).

Engaged Session A session that meets at least one engagement condition (commonly: lasted at least 10 seconds, included a key event, or
had 2+ page/screen views). This is the core unit behind engagement metrics.

Engagement Rate The percentage of sessions that were engaged. If your engagement rate is 60%, that means 60% of sessions met GA4’s engaged-session criteria.

Bounce Rate (GA4) The opposite of engagement rate. In GA4, a “bounce” is basically a not-engaged session. This is different from
the old Universal Analytics definition, so don’t treat it like the same dinosaur.

Average Engagement Time How long your site/app was actively in the foreground (a more realistic “time” metric than older session-duration thinking).

Pageview / Screenview In GA4 these are events (e.g., page_view). They still matter, but they’re no longer the entire universe.

3) Events, Parameters, and “Everything Is an Event Now”

Event A recorded interaction in GA4. Page views, clicks, scrolls, purchases, sign-ups… events.

Event Name The label for an event (like page_view, purchase, generate_lead, or your custom book_demo).

Event Parameter Extra details sent with an event (like page_location, link_url, value, currency).
Parameters are how you add context without creating a million nearly-identical events.

User Property Attributes associated with a user across sessions (e.g., membership status, customer type, plan tier). Useful for segmentation
and analysis when you need stable user-level context.

Recommended Events Google-suggested event names for common industries/use cases. Using recommended names can improve reporting consistency
and reduce “what-does-this-even-mean?” later.

Custom Event Any event you define yourself. Custom events are powerful, but naming discipline matters. If your event naming is chaos,
your reports become modern art.

DebugView A real-time-ish troubleshooting view to validate event firing while testing. Use it before you declare tracking “broken” in a Slack meltdown.

Custom Definitions The step where you register custom parameters/properties so they appear as reportable dimensions/metrics. If your parameter
exists but never shows up in reports, this is often why.

4) Key Events, Conversions, and Success Metrics (The “Did We Win?” Bucket)

Key Event An event you mark as especially important (think: lead, purchase, sign-up). In GA4, “key events” is the modern language that
replaces (or at least overlaps with) the older term “conversions” in many contexts.

Key Event Count How many times key events occurred. Great for volume tracking, but pair it with quality metrics so you don’t celebrate junk leads.

Key Event Rate The share of sessions (or users) that produced a key event. It helps answer: “Are we attracting people who actually do the thing?”

Example: If you flag generate_lead as a key event, then your “key event rate” can become a practical north-star metric for SEO landing pages.

5) Dimensions, Metrics, and Scope (The “Numbers vs Labels” Bucket)

Dimension A descriptive attribute (text/category) like City, Device category, Page title, or Session source/medium.

Metric A quantitative measurement (number) like Users, Sessions, Engagement rate, Key events, or Revenue.

Scope The level at which a dimension/metric applies. Common scopes include:

• Event-scoped: tied to a specific event (e.g., link_url).
• Session-scoped: tied to a visit (e.g., session source/medium).
• User-scoped: tied to the person (e.g., user property “plan_tier”).

Pro tip: Many “GA4 is wrong” moments are actually “scope mismatch” moments. If you mix session-scoped dimensions with user-scoped metrics, your totals can look weird.

6) Reports & Analysis Tools (The “Where Do I Click?” Bucket)

Report GA4’s standard, prebuilt reporting views (Acquisition, Engagement, Monetization, Retention). Great for quick reads and repeatable dashboards.

Exploration GA4’s advanced analysis workspace for deeper questions: funnels, pathing, segment overlap, cohorts, and ad hoc slicing. This is where you go when standard reports say, “That’s cute. Now what?”

Comparison A quick filter overlay on reports (e.g., compare “Organic Search” vs “Paid Search”). Lightweight and fast.

Segment A defined subset of users or sessions (e.g., “Users who viewed pricing and then booked a demo”). Often used in explorations.

Audience A reusable group definition you can build for analysis and (in some setups) remarketing. Audiences can be based on behaviors,
user properties, or sequences.

7) Acquisition, Campaign Tracking, and Channel Definitions (The “Where Did They Come From?” Bucket)

Source The origin of traffic (e.g., google, newsletter, facebook).

Medium The marketing method/category (e.g., organic, cpc, email, referral).

Campaign The specific initiative (e.g., spring_launch, black_friday).

Default Channel Group GA4’s rules-based grouping of traffic into channels (Organic Search, Paid Search, Email, Social, etc.). Helpful, but
not omniscientUTM consistency matters.

UTM Parameters Tags added to URLs so GA can attribute visits correctly. The most common are:

• utm_source (who sent the traffic)
• utm_medium (how it arrived)
• utm_campaign (which initiative)
• utm_term (often for paid keywords)
• utm_content (creative variation, link placement)

Example URL:
https://example.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=q1_launch&utm_content=cta_button

User Acquisition vs Traffic Acquisition Two GA4 report families that sound identical until they ruin your afternoon:
User acquisition focuses on first-touch acquisition for new users, while traffic acquisition is session-scoped and reflects
how sessions are being sourced.

8) Attribution & Advertising (The “Who Gets Credit?” Bucket)

Attribution How GA assigns credit for key events across touchpoints in the user journey (channels, ads, clicks, etc.).

Attribution Model The rule set (or data-driven logic) used to distribute that credit. GA4 supports multiple models depending on reporting context and settings.

Lookback Window How far back GA will consider touchpoints eligible for credit (e.g., 30 days). Longer windows capture more influence but can blur what actually moved the needle.

9) Data Quality, Privacy, and “Why Is This Report Missing Stuff?”

Data Retention How long GA4 keeps user-level data available for certain features. Standard properties often allow limited retention settings,
and some demographic data retains shorter regardless of your choice.

Data Thresholds (Thresholding) Privacy protections that can withhold data in reports/explorations when there’s risk of identifying individuals,
especially with sensitive dimensions. If you see numbers disappear or get “(not available),” this may be why.

(not set) GA’s way of saying, “I expected data here, but I didn’t get it.” Often caused by missing UTMs, missing parameters, or incompatible scope.

BigQuery Export An optional connection that exports GA4 event data to BigQuery for deeper querying, longer-term storage patterns, and advanced modeling.
Useful when you want SQL-level control beyond the GA4 interface.

Beginner Mistakes This Glossary Helps You Avoid

• Confusing users with sessions (a person can have multiple sessions; sessions are not people).
• Reading GA4 bounce rate like Universal Analytics (different definition; different implications).
• Making every click a key event (your “success” metric becomes meaningless noise).
• UTM chaos (e.g., Email vs email vs e-mail = three different mediums = three headaches).
• Forgetting Custom Definitions (the parameter exists, but it’s invisible in reports).
• Blaming GA4 for privacy thresholding instead of adjusting reporting choices and expectations.

Conclusion

If GA4 ever makes you feel like you need a translator, you’re not alone. But once you understand the core vocabularyusers vs sessions, events and parameters,
dimensions and metrics, and how key events and attribution workGoogle Analytics becomes a decision tool instead of a confusion machine.

Use this glossary as your cheat sheet while you build reports, set up tracking, or explain performance to stakeholders who just want one number and a thumbs-up.
(And if they demand one number, make it a good onelike key event rate for your primary business action.)

Extra: of Real-World “Glossary in Action” Experience

Here’s what usually happens when teams “know GA4” but don’t speak GA4. First, someone pulls up a report and triumphantly announces, “Traffic is up!”
Then someone else says, “Greatare leads up?” And suddenly we’re all staring at the screen like it just asked us to solve a riddle in ancient Greek.
That moment is exactly why a practical Google Analytics glossary matters: it turns vague excitement into measurable truth.

The most common real-world mix-up is users vs sessions. A marketing manager sees 10,000 sessions and assumes 10,000 people showed up.
But a “session” is a visit, not a human being. One person can return multiple timesespecially if your site is slow, your checkout is clunky, or your content is
genuinely helpful (yes, even clunky sites can have helpful content). When you report outcomes, align your story with the right unit: use users
for reach, sessions for activity, and engaged sessions for quality.

Next comes the emotional support animal of GA4 confusion: bounce rate. In GA4, bounce rate is basically the flip side of engagement rate.
That means a user can “not bounce” without clicking a thingif they stay long enough or view multiple pages/screens. So if your content is meant to answer a
question quickly (think: “store hours,” “pricing,” or “how to reset your password”), a higher bounce rate might not be a disaster. The fix is not “panic.”
The fix is to decide what “success” means, then track it as a key eventlike click_call, generate_lead, or
purchase.

Another classic scenario: a team creates 47 custom events for tiny interactions, then wonders why reporting feels messy. GA4 is event-based, yesbut that doesn’t
mean “track everything with a brand-new event name.” A cleaner approach is to use a small set of well-named events and store details in
event parameters. For example, track click (or a recommended click event) and send link_text and link_url
as parameters. You get flexibility without turning your Events report into a junk drawer.

Campaign tracking is where businesses quietly lose money. One person uses utm_medium=email, another uses utm_medium=Email, and the
CEO asks why there are “two email channels.” This is where a glossary becomes a governance tool: define your UTM standards, document them, and enforce them.
Consistent naming makes your default channel group and acquisition reports far more trustworthy.

Finally, the “Why are my numbers missing?” moment. GA4 can apply data thresholds to protect privacy, and your data retention settings can
limit how far back certain user-level analysis can go. Teams that plan ahead often connect BigQuery export early, not because they love SQL
(some do), but because it gives them options when the interface gets restrictive. The lesson: definitions aren’t triviathey’re the difference between
confident decisions and expensive guessing.