GA4 Glossary: 186 Google Analytics 4 Terms Explained A–Z

A page-not-found HTTP error that can be tracked in GA4 as a custom event.

Example: Triggering a page_not_found event whenever a 404 occurs (via GTM) lets you report on broken links and missing pages — a quick win for UX improvement.

The top-level container in GA4 that holds all your analytics properties. Think of it like a company folder: one account might belong to "Acme Corp," and inside it you have separate properties for each website or app.

Permissions granted at the top-level Google Analytics account, automatically cascading down to every property within it.

Example: Granting a new marketing agency account-level Editor access means they can edit all your properties — including ones you may not want them touching. Always prefer property-level access for third parties.

The process and reports in GA4 that track how users first discover and arrive at your site. Covers both User Acquisition (first visit ever) and Session Acquisition (each visit's source).

Shows how new and returning users arrive at your site — split into User Acquisition (first visit) and Traffic Acquisition (per session).

Example: The User Acquisition report shows 60% of new users come from Organic Search, while the Traffic Acquisition report shows most sessions come from Direct — meaning returning users mostly come back directly.

The number of users who had at least one engaged session, triggered a key event, or had a session lasting more than 10 seconds. This is GA4's primary user metric (replacing "Users" from Universal Analytics).

Filters that isolate specific subsets of users, sessions, or events for deeper analysis.

Example: Creating an advanced segment of "users from Bengaluru who visited the pricing page more than twice in a week" to analyze high-intent local users.

GA4 settings that enable ad personalization, remarketing, and integration with Google Ads and other Google marketing products. Requires user consent under GDPR/privacy laws.

Notes you manually add to a GA4 property's timeline to document significant events.

Example: Adding an annotation on the day you launched a major site redesign helps you later explain a sudden spike or drop in traffic in reports.

GA4 automatically flags data points that deviate significantly from expected ranges.

Example: If your daily sessions suddenly drop by 80%, GA4 surfaces this as an anomaly so you can investigate quickly — no manual monitoring needed.

GA4 exposes a Data API and Admin API, letting developers pull report data programmatically or automate property configuration.

Example: A company builds an internal dashboard that queries the GA4 Data API every morning to display daily KPIs to the marketing team — without anyone manually exporting reports.

A developer API that lets you programmatically query GA4 report data and automate property configuration without using the GA4 interface.

Example: A marketing team builds an internal Slack bot that queries the GA4 Data API every morning and posts yesterday's key metrics — sessions, conversions, revenue — directly into their team channel.

The process of assigning credit to marketing touchpoints that led to a conversion.

Example: If a user first came via organic search, then returned via email, and then purchased — attribution models decide which channel gets credit.

A defined group of users based on shared behaviors, demographics, or events. Audiences can be used for remarketing in Google Ads.

Example: "Users who visited the pricing page but didn't purchase."

GA4's AI-driven alerts that proactively surface notable changes in your data without you needing to configure them.

Example: GA4 automatically flags "Organic traffic from mobile increased 45% this week" — surfacing opportunities or issues you might otherwise miss in daily reports.

The average total time users spent with the site or app in the foreground across all sessions. More meaningful than old "session duration" because it only counts time the tab is active.

The average active foreground time per individual session.

Example: If total engagement time is 5,000 seconds across 500 sessions, the average is 10 seconds/session.

Total revenue divided by the number of purchase events, showing the average transaction size. GA4 calculates this automatically if you implement the purchase event correctly with value and currency parameters.

Example: ₹5,00,000 in revenue from 250 purchases = ₹2,000 AOV.

A machine learning system GA4 uses to estimate the behavior of users who declined consent, based on patterns from consenting users.

Example: If 40 users declined cookies but 10 consented users showed similar behavior, GA4 may model that ~3 additional conversions occurred among the non-consenting group.

Comparing your property's performance metrics against anonymized aggregated data from similar industries.

Google's fully managed, serverless cloud data warehouse where GA4 raw data is exported for large-scale analysis.

Example: Instead of being limited to 14 months of data in GA4's UI, a company queries 3 years of event data in BigQuery using SQL to build a long-term user cohort retention model.

The GA4 feature that continuously streams or daily-batches all raw event data into a linked Google BigQuery project. Unlike standard GA4 reports (which can be sampled), BigQuery contains every single event row with all parameters.

Example: A data engineer writes a SQL query in BigQuery joining GA4 event data with CRM purchase data to calculate true customer lifetime value — something impossible within GA4's standard UI.

The percentage of sessions that were not engaged. In GA4, Bounce Rate = 1 − Engagement Rate. A user who lands on a page and immediately leaves without any interaction counts as a bounce.

A dimension in GA4's Tech reports that identifies which browser the user is using.

Example: Seeing that 25% of your users are on Safari helps you prioritize testing on that browser, especially for iOS-related issues.

Custom metrics you create in GA4 by applying mathematical formulas to existing metrics.

Example: Dividing Purchase Revenue by Active Users to create a "Revenue per User" metric that doesn't exist natively in GA4 — helping you compare monetization efficiency across campaigns.

The name you assign via UTM parameters to a specific marketing campaign.

Example: utm_campaign=diwali_sale_2025.

The collective set of UTM parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) attached to a URL.

An admin-level log that records every configuration change made to a GA4 property, including who made it and when.

Example: If your bounce rate suddenly changes, Change History can reveal whether someone accidentally toggled off Enhanced Measurement.

A grouping of traffic sources into marketing categories. Examples: Organic Search, Paid Search, Direct, Email, Organic Social.

A more granular geographic dimension showing the city-level origin of users.

Example: A local restaurant chain can filter GA4 reports by City to see whether most online orders come from their delivery radius.

Fires when a user clicks a link that leads to an external domain.

Example: A click event fires when a user on your site clicks a link to an affiliate partner site, helping you measure outbound traffic.

An anonymous, randomly generated identifier stored in a browser cookie to track users across sessions on the same device. Unlike User ID, it's set by GA4, not by you.

A funnel type where users must enter at the first step to be counted.

Example: A strict closed funnel for a sign-up flow ensures you're only measuring users who started from the landing page, giving a cleaner conversion rate for that specific campaign.

A group of users who share a common characteristic in the same time period.

Example: All users who first visited in January — tracking their retention over the following weeks.

An Exploration report that groups users by a shared characteristic (like acquisition date) and tracks their behavior over time.

Example: Users acquired in a January campaign — did they return in Week 2? Week 4? This report answers that visually.

A GA4 feature to overlay two or more data segments side-by-side within standard reports.

Example: Comparing Mobile vs. Desktop traffic performance in the same chart.

A GA4 admin feature that lets one gtag or GTM container send data to multiple GA4 properties simultaneously, without changing website code.

Example: A digital agency managing a client site can use Connected Site Tags to send data to both their own QA property and the client's live property.

A Google framework that adjusts GA4's tracking behavior based on whether a user has consented to cookies. Instead of firing or not firing tags, it sends "consent signals" that allow modeling to fill gaps.

The data sent to Google indicating the user's consent status for analytics and advertising cookies. GA4 uses these to determine what data can be collected and what must be modeled.

A custom grouping applied to pages so you can analyze traffic/engagement by topic or section.

Example: Grouping all /blog/* pages into a "Blog" content group.

The original GA4 term for a key event; still widely used to describe a user completing a desired action. Note: Google officially renamed "Conversions" to "Key Events" in 2024 for GA4, though "Conversions" still appears in Google Ads.

The percentage of sessions or users that resulted in a key event. Formula: Key Events ÷ Sessions × 100. This is one of the most critical KPIs for any business — even a 0.5% improvement can mean significant revenue gains.

Example: If your site had 5,000 sessions and 150 purchases, your conversion rate is 3%.

A small text file stored in a user's browser that GA4 uses to identify returning users (via Client ID).

GA4's approach to tracking users without relying on third-party cookies, using Consent Mode, behavioral modeling, and User-Provided Data. As browsers like Chrome phase out third-party cookies, this becomes increasingly critical for accurate reporting.

Google's set of user experience metrics (LCP, FID/INP, CLS) measuring loading speed, interactivity, and visual stability. These can be sent to GA4 as custom events and are critical for SEO performance as Google uses them as a ranking signal.

The total cost of acquiring one converting customer through a paid campaign. Formula: Total Ad Spend ÷ Number of Conversions. This metric is imported from Google Ads into GA4 reports.

Example: Spending ₹10,000 to get 50 purchases = ₹200 CPA.

A GA4 dimension showing the country where the user's session originated based on IP address.

Example: Discovering that 40% of your users are from India despite your marketing being targeted only to the US suggests an untapped market worth localizing for.

A medium value (medium=cpc) indicating paid traffic where you're charged per click, typically from Google Ads.

GA4's ability to recognize and stitch together a single user's activity across multiple devices when User ID or Google Signals is active.

Example: A user browses your shoe catalog on their phone during commute, then completes the purchase on their laptop at home. Without cross-device tracking, GA4 would count this as two separate users with one abandoned session — with it, it's one user journey.

The section in GA4's Admin panel where you create and manage custom dimensions and metrics.

A user-defined dimension that captures data GA4 doesn't collect by default.

Example: Tracking a "Membership Plan" dimension (Free vs. Pro) for each user.

Funnels you build in GA4 using any combination of events (not just predefined steps), giving more flexibility than standard funnel reports.

Example: Building a funnel from video_play → scroll (90%) → contact_form_submit to track how video viewers convert.

A user-defined automated alert in GA4 that triggers when a specific metric crosses a threshold you set.

Example: Setting a custom insight to alert you when daily sessions drop more than 30% compared to the previous week — catching site outages or tracking failures early.

A user-defined numeric measurement beyond GA4's defaults.

Example: Tracking "Words Read" per article session.

A GA4 feature that lets you upload offline data (e.g., CRM data, cost data, product metadata) to enrich your GA4 reports.

Example: Uploading ad spend from non-Google platforms to see cost-per-acquisition across all channels.

The admin setting that controls how long GA4 stores user-level and event-level data before deleting it.

Example: The default is 2 months; extending to 14 months lets you run comparisons like "how did users acquired in January last year behave over a full quarter?"

The data pipeline that sends information from your website, iOS app, or Android app into a GA4 property. A property can have multiple data streams (e.g., one for web + one for the mobile app).

A real-time report in GA4 used during implementation to verify that events are firing correctly. Requires activating debug mode via GTM or the GA Debugger Chrome extension.

GA4's pre-built rules for automatically categorizing traffic into standard channels like Organic Search, Direct, Referral, etc.

Example: Traffic from Google with medium=organic is automatically bucketed into "Organic Search."

GA4's cascading method for identifying users across sessions: it first tries User ID, then Google Signals, then Device ID, and finally modeled data.

Example: A logged-in user will be identified by their User ID, while an anonymous guest is identified by their Device ID (client ID).

Dimension data about your users' age, gender, and interests (requires Google Signals or sufficient data).

A dimension that classifies users by the type of device they used: desktop, mobile, or tablet.

Example: Discovering that mobile users have a 20% lower engagement rate than desktop users signals a potential mobile UX problem worth investigating.

The identifier used on mobile apps to track users on a specific device. On iOS this is the IDFA; on Android it's the GAID.

A qualitative attribute that describes your data. In reports, dimensions appear as rows. Examples: Country, Device Category, Page Title, Session Source.

Traffic where no referrer information is passed — the user typed your URL directly, used a bookmark, or clicked an untracked link.

Google's enterprise programmatic advertising platform for buying display, video, and connected TV inventory across the web. GA4 audiences and conversions feed directly into DV360 campaigns.

Example: A GA4 audience of "users who viewed 3+ product pages but didn't purchase" can be exported to DV360 to serve them a targeted video ad on YouTube or premium publisher sites.

A specific built-in event (purchase) GA4 tracks for online transactions, capturing revenue, item details, and order info.

A session that lasts longer than 10 seconds, has at least one key event, or has two or more page/screen views. This is GA4's replacement for the old "non-bounce" session concept.

The percentage of sessions that were "engaged sessions". Formula: Engaged Sessions ÷ Total Sessions × 100.

Example: 700 engaged sessions out of 1,000 total = 70% engagement rate.

GA4's built-in report showing events, conversions, pages/screens, and landing page performance.

Example: The Engagement → Events sub-report shows that scroll fires 3× more often than click, meaning users read but don't click CTAs — a prompt to redesign your call-to-action buttons.

A feature that improves conversion measurement accuracy by securely sending hashed first-party data (email, name) to Google Ads.

A GA4 feature that automatically tracks common interactions (scrolls, outbound clicks, video plays, file downloads, site search) without needing custom code. Simply toggle it on in the Data Stream settings.

Any user interaction or action that GA4 tracks. GA4 is fully event-based, unlike Universal Analytics which used sessions and pageviews as its primary units. Examples: page_view, scroll, click, purchase, video_play.

The total number of times a specific event has been triggered.

Example: If 100 users each clicked a button twice, the event count is 200.

The average number of times each user triggered a specific event. Helps gauge how frequently users perform an action.

Additional data attached to an event to provide more context.

Example: A purchase event might have parameters like value: 999, currency: INR, item_name: "Running Shoes".

The average number of events fired per session. A useful signal for overall user engagement depth.

The percentage of sessions where a specific page was the last page viewed before the user left. Unlike Bounce Rate (which measures single-page sessions), Exit Rate applies to any page in any session.

Example: A high exit rate on your /checkout/confirm page could signal a broken confirmation flow.

Advanced, customizable reports in GA4 (under the "Explore" tab) that go beyond standard reports. Types include: Free Form, Funnel Exploration, Path Exploration, Cohort Exploration, and Segment Overlap.

An automatically tracked Enhanced Measurement event (file_download) that fires when a user clicks a link to a downloadable file (PDF, ZIP, DOCX, etc.).

Example: Tracking downloads of your product brochure PDF reveals which marketing pages are driving the most content engagement.

Google's mobile app development platform that shares the same event-based data infrastructure as GA4. When you add the Firebase SDK to your iOS or Android app, events automatically flow into the linked GA4 property.

Example: A first_open event fires the first time someone opens your app post-install, app_exception fires on crashes, and notification_open fires when a push notification is tapped — all available in GA4 reports out of the box.

The mobile analytics layer built into Firebase SDK, which shares the same underlying data infrastructure as GA4.

Example: When developers add the Firebase SDK to an iOS or Android app, all app events automatically flow into the linked GA4 property with no additional setup.

The source and medium that originally brought a user to your site for the very first time. These are lifetime attributes of a user that never change, even across future sessions.

Data you collect directly from your own users through your own channels (your website, app, CRM). This is the most reliable and privacy-safe data signal available in a cookieless world.

Example: Email addresses collected at checkout, stored in your CRM, and used to enrich GA4 via User-Provided Data.

Fires the first time a user opens your mobile app after installing it. Critical for measuring app install → first engagement drop-off in mobile analytics.

An Exploration report that visualizes each step of a user journey and shows where users drop off.

Example: A 4-step checkout funnel (Cart → Shipping → Payment → Confirmation) reveals that 60% of users abandon at the Payment step — a clear optimization target.

The enterprise, paid version of GA4, offering higher data limits, SLA guarantees, unsampled reports, and deeper BigQuery integrations for large organizations.

Example: A major e-commerce platform processing millions of daily sessions would use GA4 360 to avoid sampling and get faster reporting.

A visual representation of the steps users take to reach a defined goal, highlighting both progression and drop-off at each step.

Example: A goal flow from video_play → scroll (90%) → sign_up might reveal that users who watch your intro video are 3× more likely to sign up — justifying more prominent video placement on your homepage.

Google's advertising platform, which integrates with GA4 to import key events as conversions, share audiences for remarketing, and view campaign performance. See our Google Ads guide for full campaign setup and conversion tracking.

The current and latest version of Google's web and app analytics platform, launched in 2020, built on an event-based data model rather than the session/pageview model of Universal Analytics.

Example: Instead of tracking "a user visited 3 pages in a session," GA4 tracks individual events: page_view, scroll, click — giving far more granular behavioral insight.

Google's now-discontinued A/B testing tool that previously integrated with GA4. It was sunset in 2023; alternatives include VWO, Optimizely, or Firebase A/B Testing.

An optional GA4 feature that uses data from signed-in Google users who have opted into ad personalization, enabling cross-device reporting and richer demographics.

Google's unified tagging JavaScript library used to send data directly to GA4 (and other Google products) from your website without a tag manager.

A tag management system that lets you deploy and manage GA4 (and other tags) without editing website code. Recommended for most implementations as it's more flexible.

The domain or subdomain from which data is being sent.

Example: If you have both www.mysite.com and shop.mysite.com, GA4 shows hostname as a dimension so you can filter reports to just one subdomain.

A Google-defined segment of users who are actively researching or comparing products/services in a specific category, based on their recent browsing behavior across the web.

Example: A user who has been reading laptop reviews and comparing prices across multiple sites is placed in Google's "In-Market: Computers & Peripherals" segment, which you can target via Google Ads using GA4 audience integration.

Predefined Google audiences of users actively researching or comparing products/services in a specific category.

Example: Users browsing multiple car review sites are placed in Google's "In-Market: Automobiles" segment, which you can target in Google Ads via GA4.

GA4's AI-powered anomaly detection and automated insights feature. It surfaces unexpected changes in your data and lets you ask natural-language questions about your analytics.

Traffic originating from your own organization (employees, developers) that should typically be excluded from reports. GA4 lets you define internal traffic rules in Admin > Data Streams > Configure Tag Settings.

Example: Without filtering internal traffic, a developer testing your checkout 50 times a day would distort your purchase conversion data.

A GA4 admin rule that excludes visits from your own team by matching specific IP addresses or parameter values.

Example: Without this filter, a developer testing the checkout flow 50 times a day would inflate your session count and distort your conversion rate. You define internal traffic rules under Admin → Data Streams → Configure Tag Settings.

Dimensions in GA4's e-commerce model that describe individual products within a transaction.

Example: item_name, item_category, item_brand are item-scoped dimensions that let you analyze which specific products drive the most revenue.

A high-value event you designate as important to your business (previously called a "Conversion" in GA4).

Example: Marking purchase or sign_up as a key event so it's counted in reports as a business goal.

The first page a user sees when they arrive at your site in a given session. The Landing Pages report helps identify which entry points drive the best engagement.

The browser or device language setting of the user.

Example: If 15% of your users have language = hi (Hindi), adding a Hindi version of your site could significantly improve engagement and conversions for that segment.

The section in GA4 reports where you can customize which report collections appear in the left navigation and create custom report collections.

The total predicted or actual revenue a user generates over their entire relationship with your site or app. Key for e-commerce businesses to identify most valuable user segments.

An audience Google Ads creates by finding new users who statistically resemble an existing GA4 audience in terms of interests, behaviors, and demographics.

Example: Starting with a GA4 audience of your top 1,000 highest-value customers, Google builds a lookalike audience of millions of similar users across the web — dramatically expanding your reach without sacrificing targeting precision.

The number of days GA4 looks back to attribute a conversion to a prior touchpoint. Default is 30 days for key events (90 days for first-click).

Google's free BI and visualization tool that connects natively to GA4 for custom dashboards. Formerly called Google Data Studio.

Example: Building a Looker Studio dashboard that shows GA4's Engagement Rate, Revenue, and New Users side-by-side with Google Ads spend — auto-refreshing daily without manual exports.

A unique identifier (formatted as G-XXXXXXXX) assigned to each data stream in GA4. It's pasted into your website code to ensure data flows to the correct property.

An advanced API that lets you send event data directly to GA4 from any device or server, not just browsers.

Example: Sending a purchase event from your server when a payment is confirmed (bypassing the browser to avoid data loss from ad blockers).

The marketing channel or mechanism used. Examples: organic, cpc, email, referral, social.

A quantitative measurement that gives a number to a dimension. In reports, metrics appear as columns. Examples: Sessions (2,500), Engagement Rate (68%), Event Count (14,000).

GA4's built-in report for tracking revenue from e-commerce purchases, in-app purchases, and ad revenue. Gives a combined view of all revenue-generating events in one place.

Reports that show all marketing touchpoints a user interacted with on the path to a conversion, not just the last click.

Example: A user sees a Facebook ad → clicks an organic Google result two days later → receives a retargeting email and converts. MCF gives visibility into every step, helping you avoid under-crediting top-of-funnel channels like social.

A visitor whose device/browser has never been tracked by that GA4 property before.

Example: Someone visiting your site for the very first time from a new browser.

A value shown in GA4 when organic keyword data is withheld by Google for privacy reasons. Almost all organic search keywords are "not provided" in GA4's standard reports — Search Console integration is the only way to recover this data.

A placeholder value in GA4 reports meaning no value was collected for that dimension.

Example: If a landing page URL isn't captured, the Landing Page dimension shows "(not set)."

A funnel type in GA4's Funnel Exploration where users can enter at any step, not just the first.

Example: In a checkout funnel, an open funnel reveals users who skipped directly to the payment step without going through the cart — useful for understanding non-linear journeys.

The OS on the user's device (Windows, macOS, iOS, Android, etc.).

Example: A sudden drop in engagement on Android could indicate a bug introduced in your latest app update.

Traffic that came from unpaid search engine results.

Example: A user clicking your link in Google Search without an ad being involved.

Traffic from unpaid search engine results. GA4 classifies this as the "Organic Search" channel when medium=organic. Linking Google Search Console enriches this data with impressions, clicks, and average position.

The URL path (everything after the domain) of a viewed page. Used in reports to analyze performance of specific URL structures, unlike Page Title which can change without a URL change.

Example: /products/running-shoes

The HTML title tag value of the page viewed, used as a dimension in GA4 reports.

Example: "Product Page – Running Shoes | MyStore" appears as the page title in the Pages & Screens report, letting you identify which specific product pages get the most views.

A built-in GA4 event (page_view) that fires every time a user loads or reloads a page. The most fundamental tracking metric.

A built-in GA4 report showing which pages (web) or screens (app) receive the most views, along with engagement metrics per page.

Example: Discovering that your /about page has extremely high average engagement time signals it's resonating with users exploring your brand.

Any key-value pair of additional data sent with an event. Custom dimensions/metrics are created from parameters.

Example: {item_category: "footwear"}.

An Exploration report that displays the sequence of pages or events users navigate through in a tree-graph format.

Example: Starting from the Homepage node, you can see that 40% of users went to /pricing next, while 30% went to /blog.

Data that can identify a specific individual — e.g., names, email addresses, phone numbers. GA4 strictly prohibits sending PII in any event or parameter.

An audience GA4 automatically constructs using its predictive metrics (purchase probability, churn probability) — no manual rules needed.

Example: The built-in "Likely 7-day purchasers" audience is made of users GA4's ML model predicts will buy within a week — pushing this audience to Google Ads lets you bid more aggressively on your hottest prospects.

ML-powered metrics GA4 generates to forecast future user behavior. Examples: Purchase Probability (likelihood a user will buy in the next 7 days), Churn Probability, Predicted Revenue.

A single website or app being tracked within a GA4 account.

Example: If you run a blog and an e-commerce store, each gets its own property under one account.

Permissions scoped to a single GA4 property, with no visibility into other properties in the same account.

Example: An agency managing your e-commerce property can be given property-level Editor access without ever seeing data from your internal HR or intranet analytics property.

The total revenue generated from purchase events, net of refunds. The core monetization metric in GA4's e-commerce reports.

Example: If 10 purchases of ₹1,000 each occurred and one ₹1,000 refund was processed, Purchase Revenue = ₹9,000.

Traffic that came from another website linking to yours.

Example: A blog post on another site has your link; users clicking it show as referral traffic.

A GA4 e-commerce event (refund) that records when a transaction is reversed. It reduces revenue figures in reports.

Example: When a customer returns a product and you process the refund, firing a refund event with the original transaction_id ensures your GA4 revenue data stays accurate.

The state or province-level geographic breakdown of your users.

Example: An Indian e-commerce brand can see that Maharashtra and Karnataka drive the most revenue, helping prioritize regional promotions.

A pattern-matching syntax used in GA4 filters and audiences.

Example: The regex ^/blog/.* matches any URL starting with /blog/.

The practice of showing targeted ads to users who have previously visited your site or app, using GA4 audiences exported to Google Ads.

Example: Creating a GA4 audience of "users who added to cart but didn't purchase" and targeting them with a discount ad in Google Ads.

How GA4 identifies users across sessions: by User ID, Device ID, or modeled behavior.

Shows the percentage of users who return to your site on each subsequent day after their first visit.

Example: A Day 1 retention of 25% means 1 in 4 users who visited yesterday came back today — a benchmark that varies heavily by industry.

Revenue generated divided by the amount spent on ads. GA4 calculates this when Google Ads is linked.

Example: Spending ₹10,000 on Google Ads and generating ₹50,000 in tracked GA4 purchase revenue = 5x ROAS.

Total purchase revenue divided by the number of active users. A key metric for comparing how effectively different traffic sources monetize.

Example: ₹1,00,000 in revenue from 500 users = ₹200 revenue per user.

An analysis approach in GA4 Path Exploration that works backward from a completed event to see what steps preceded it.

Example: Starting from a purchase event and exploring backward reveals that 60% of buyers visited the /reviews page just before converting — a signal to promote that page more.

Total revenue generated divided by the amount spent on ads. GA4 calculates this automatically when Google Ads is linked and purchase events are properly configured.

Example: Spending ₹20,000 on Google Ads and generating ₹1,00,000 in GA4-tracked revenue = 5x ROAS.

When GA4 analyzes only a portion of your data instead of 100% due to large data volumes. Exploration reports can be affected by sampling; exporting to BigQuery avoids this.

The equivalent of Page Path for mobile apps — the name assigned to each screen in your app's code.

Example: HomeScreen, ProductDetailScreen, CheckoutScreen — letting you identify which app screens users spend the most time on.

The pixel dimensions of the user's device screen.

Example: If a large segment of your users is on 360×800 resolution (common mid-range Android phones), your design team should test at that resolution specifically.

Fires the first time a user scrolls to the bottom 90% of a page. Enabled automatically via Enhanced Measurement.

Example: If only 10% of users trigger a scroll event on your blog post, most readers aren't getting past the fold — time to restructure the content.

Google's enterprise-grade search campaign management platform for running paid search across Google, Bing, and Yahoo simultaneously. It integrates with GA4 to import key events as conversion signals and share audiences.

Example: A national retail brand running paid search at scale uses SA360 to manage millions of keywords, with GA4's purchase key events flowing in to optimize bids automatically.

The actual keyword or phrase a user typed into a search engine before landing on your site. When Google Search Console is linked to GA4, organic search queries appear in reports.

Example: Seeing that "best running shoes under 5000" is driving traffic to your product page tells you which organic keywords are performing.

Data shared between two trusted organizations through a direct partnership.

Example: A retailer sharing purchase data with a supplier to help the supplier understand sell-through rates — that supplier's use of the data is "second-party."

A temporary filter applied within Exploration reports to focus analysis on a subset of users, sessions, or events. Unlike Audiences, segments don't persist outside the report.

An Exploration that compares up to 3 audience segments and shows how they intersect.

Example: Overlapping "Mobile Users," "Users from India," and "Users who purchased" to find users who match all three criteria.

Moving GA4 tag firing from the user's browser to a server you control, improving data accuracy and privacy compliance.

Example: Instead of a browser GA4 tag (which ad blockers can block), a server receives the event first, then forwards it to GA4 — ensuring near-100% data collection.

A group of user interactions on your site within a given time frame. In GA4, a session begins with a session_start event and expires after 30 minutes of inactivity.

Example: One person browsing 5 pages in a row = 1 session.

The UTM campaign name associated with the traffic source of the current session.

Example: utm_campaign=feb_sale would appear as the Session Campaign in reports for all traffic tagged with that parameter.

The percentage of sessions in which at least one key event occurred.

Example: 300 sessions with a form submission out of 2,000 total sessions = 15% session conversion rate. Useful for comparing landing page effectiveness across campaigns.

A unique identifier automatically assigned to each session in GA4. Useful for joining GA4 data with other data sources (like BigQuery).

The medium (e.g., organic, cpc, referral) associated with how the current session began.

Example: A user clicking a Google Ad has session_medium = cpc, even if they first visited organically.

The source (e.g., google, facebook.com) that initiated the current session, as opposed to the first-ever session.

Example: A returning user who originally came from organic search but returned via an email campaign — their session source would be the email sender domain.

The event automatically fired by GA4 when a new session begins. It marks the beginning of a group of user interactions.

The event GA4 automatically fires at the beginning of every new session. Every session is anchored to this event, and it's what generates the Session ID.

How quickly your website's pages load for users, which GA4 can partially track via custom events or via integration with Core Web Vitals.

Example: Firing a custom event web_vitals with parameters for LCP (Largest Contentful Paint) and CLS (Cumulative Layout Shift) gives you performance data per page.

Where a user came from — typically the domain or platform that sent the traffic.

Example: google, facebook.com, newsletter.mycompany.com.

A custom rule or audience exclusion in GA4 designed to block bot traffic, known spam referrers, or irrelevant sources from polluting your reports.

Example: Creating an audience exclusion for sessions where page_referrer matches known spam domains keeps your traffic quality reports clean and your conversion rates accurate.

GA4's built-in report showing the technology (browser, OS, device model, screen resolution) your users are on.

Example: Finding that 30% of your users are on Safari Mobile helps you prioritize iOS-specific bug fixes.

A data privacy safeguard in GA4 that suppresses data in reports when user counts are too small, preventing identification of individuals. Commonly triggered when Google Signals is enabled.

A funnel metric showing how long users take to move through all steps of a funnel.

Example: If users take an average of 4 days to go from first product view to purchase, your retargeting email sequence should start within 24 hours to recapture them.

The total count of all users (both new and returning) who triggered any event during a given period. Active Users ≠ Total Users; Total Users is always ≥ Active Users.

The previous version of Google Analytics (also called GA3), which was sunset on July 1, 2023. It used a session-based model and tracked hits (pageviews, events, transactions) separately. GA4 fully replaces it with a unified event model.

A Google tool that helps you construct URLs with proper UTM parameters without manually typing them. Available at Campaign URL Builder.

Any individual who visits your site or app and is assigned a unique identifier by GA4. A user can visit multiple times across multiple sessions.

A built-in report showing demographic and geographic characteristics of your users.

Example: Discovering your top user cities are Bengaluru, Mumbai, and Delhi helps you tailor content and marketing for those regions.

An event automatically triggered by GA4 while the page/app is in focus; powers the "engagement time" metric.

A custom, persistent identifier you assign to known/logged-in users (e.g., your own database ID). This allows GA4 to track the same person across devices and browsers.

The percentage of total users who completed at least one key event during a given period. This is the user-level equivalent of session conversion rate and gives a truer picture of how many individuals are converting.

Example: If 200 out of 1,000 users triggered a purchase event, the User Key Event Rate is 20%.

A section of GA4's standard reports that organizes data around the stages of the customer journey: Acquisition, Engagement, Monetization, and Retention.

How well your site/app keeps users coming back over time. GA4 has a built-in Retention report showing returning users over days/weeks.

GA4 has five permission levels: Viewer (can view reports only), Analyst (can create and edit Explorations), Marketer (can create audiences and manage conversions), Editor (can modify all property settings), Administrator (full control including user management).

Example: A freelance data analyst gets "Analyst" access to build Exploration reports, while a developer configuring events needs "Editor" access. Giving everyone "Administrator" is a common security mistake.

First-party data you explicitly collect from users (e.g., email at checkout) and share with Google in a hashed/anonymized form to improve measurement.

Parameters added to a URL to track campaign performance in GA4. GA4 reads these automatically.

Example: ?utm_source=newsletter&utm_medium=email&utm_campaign=feb_sale.

A trio of Enhanced Measurement events automatically tracked for embedded YouTube videos. video_start fires when playback begins, video_progress fires at 10%, 25%, 50%, and 75% watched, and video_complete fires at 100%.

Example: If 80% of users trigger video_start but only 15% trigger video_complete, your video is losing attention early — consider a shorter, punchier edit or moving the key message to the first 30 seconds.

Fires when a user performs an internal site search and views results.

Example: Captures queries like "pricing" or "refund policy" — revealing what users can't easily find through your navigation.

In GA4, "Views" refers to the total number of times a specific page or screen has been seen by users. Unlike the old Universal Analytics, GA4 replaced the "View" configuration layer with data streams.

The average number of pages/screens each user viewed. A higher number can indicate either deep engagement or navigation confusion.