Digital Marketing Learning

What Is Google Analytics? GA4 Features, Reports and Uses

Learn what Google Analytics 4 does, how to set up and verify tracking, which reports matter, and how to use events and acquisition data for SEO and traffic analysis.

Bernard
BernardAuthor
Nov 18, 2026 14 min read
What Is Google Analytics? GA4 Features, Reports and Uses

Learn what Google Analytics 4 does, how to set up and verify tracking, which reports matter, and how to use events and acquisition data for SEO and traffic analysis.

Google Analytics is Google’s tool for measuring how people find and use a website or app. Its current version, Google Analytics 4 (GA4), records interactions as events and uses them to report on acquisition, engagement, and business outcomes.

Quick example: Suppose a service business wants to know how visitors found its site, which page they entered through, and whether they submitted an enquiry.

  • Traffic acquisition: Use Session source / medium to see what brought the visit, such as Google organic search or an email campaign.
  • Landing page: See which page visitors opened first in each session, such as the service page or a blog post.
  • Events and key events: Find generate_lead in the Events report after configuring it to fire on confirmed form submissions. Mark the verified event as a key event to track enquiries as a business outcome.
Read more: What Is Google Search Console?

How Does Google Analytics 4 Work?

GA4 uses a tracking tag installed directly on a website or through Google Tag Manager. When a visitor loads a page or performs a configured action, the tag sends an event and its associated parameters to the property. GA4 processes that data and makes it available in standard reports, explorations, audiences, and advertising tools.

Unlike the older Universal Analytics model, GA4 is built around events instead of treating pageviews, transactions, and other interactions as separate hit types. A page view is an event. A click can be an event. A form submission, purchase, scroll, file download, or video start can also be measured as an event.

Google describes GA4 as an event-based platform that can collect website and app data while supporting privacy controls and behavioral modeling. You can review Google’s GA4 overview for the platform’s current model and capabilities.

Conceptual GA4 event collection from a website interaction to an event record and reporting property.

 

The Four Measurements Beginners Should Understand

Users represent people who interacted with the website or app. Sessions group activity that happens during a visit. Events record specific interactions. Key events are the events you mark as especially important to the business, such as a purchase, qualified lead, registration, or completed contact form.

These measurements are connected but not interchangeable. A website may gain many users and sessions while producing very few meaningful events. That is why traffic volume alone is not a reliable measure of performance.

What Is Google Analytics Used For?

Google Analytics is used to connect marketing activity with on-site behavior. It provides evidence for decisions about SEO, paid campaigns, content, landing pages, user experience, and conversion optimization.

Measure Traffic Sources and Campaigns

The Acquisition reports show whether visits arrived through organic search, paid search, social media, referrals, direct traffic, email, or tagged campaigns. Source, medium, campaign, and channel data help marketers compare not only visitor counts but also engagement and key-event performance.

Separate conceptual measurement cards for users, sessions, events and selected key events in GA4.

 

Analyze Landing Pages and Content

GA4 can show which page started a session, which pages received views, how visitors moved through the site, and where important events occurred. This helps content teams identify pages that attract attention but fail to move users toward the next useful action.

Track Leads, Sales, and Other Outcomes

A useful GA4 property should measure business actions instead of relying only on pageviews. Ecommerce purchases, generated leads, account registrations, calls, downloads, trial starts, and other outcomes can be configured as events and selected as key events.

Understand Audience and Technology Patterns

Reports can group data by country, city, language, device category, browser, operating system, and other dimensions. These breakdowns help diagnose whether a campaign reaches the intended audience and whether a technical or usability issue affects a particular segment.

Buy Web Traffic
Buy Web Traffic

If you want to promote a recently published article, SEOVisitor’s website traffic service can help you bring additional visits directly to that piece of content.

Core Google Analytics 4 Reports and Features

GA4 includes many tools, but most websites do not need to use all of them at once. The most valuable features are the ones that answer a specific business question and rely on correctly collected data.

Realtime Report

The Realtime report shows activity from the last 30 minutes. It is useful for checking whether a new tag, campaign link, page, or event is sending data. Realtime is a diagnostic view, not a substitute for longer-term performance analysis.

Conceptual report folders representing acquisition, engagement, exploration and exported event data.

 

Acquisition Reports

User Acquisition focuses on how a user was first acquired, while Traffic Acquisition focuses on the source of individual sessions. Mixing these scopes can create confusing conclusions, so always confirm whether a report uses first-user or session-level dimensions.

Engagement Reports

Engagement reports cover events, pages and screens, landing pages, and key events. They help reveal whether visitors actually interact with content after arriving. Engaged sessions, average engagement time, and event completion are often more informative than a raw session count.

Explorations

Explore provides flexible analysis methods such as free-form tables, funnels, path exploration, and segment overlap. It is especially useful when standard reports cannot answer a question, for example where users abandon a multi-step process or how organic visitors behave after entering through a particular page.

Audiences and Comparisons

Audiences group users based on conditions, while comparisons and segments isolate subsets of data for analysis. You might compare organic visitors with paid visitors, mobile users with desktop users, or visitors from one target country with all other locations.

Event planning notebook distinguishing routine interactions from a validated business outcome selected as a key event.

 

Advertising and Attribution

GA4 can analyze how channels contribute to key events. Attribution reports help prevent the last interaction from receiving all the credit when several touchpoints influenced a decision. Results still depend on consent, tracking continuity, attribution settings, and the available data.

BigQuery Export

The BigQuery Export feature sends raw GA4 event data to BigQuery for more detailed querying and modeling. It is valuable when analysts need data beyond the standard interface, want to join analytics with internal business data, or need custom quality checks.

Events and Key Events in GA4

Events are the foundation of Google Analytics 4. Some are collected automatically, some come from enhanced measurement, and others must be recommended or custom events. A good event plan uses clear names, avoids duplicate tracking, and records only parameters that are genuinely useful.

Mark only meaningful outcomes as key events. If every minor interaction becomes a key event, reports lose their ability to distinguish genuine progress from routine browsing. For an online store, purchases and checkout milestones may matter. For a service business, qualified form submissions, calls, or booked consultations may be more appropriate.

How to Set Up Google Analytics 4

A useful setup starts with an audit, not another tracking tag. Check whether a suitable GA4 property already exists, who owns it, and which website implementation sends data to it. An automatically created property still needs verification. Record the current setup and a rollback plan before changing tags.

1. Audit Access and Existing Tracking

Inventory Analytics properties, web streams, CMS integrations, hardcoded scripts, and Tag Manager containers. Test representative landing pages, forms, checkout pages, and relevant subdomains. A G- measurement ID identifies a GA4 web stream; GTM- identifies a Tag Manager container; an old UA- tracking ID does not collect GA4 data. Check the actual destination instead of relying on a plugin’s installed status.

Keep account control with the organization and give each person only the access they need. Confirm the permissions required to create or edit the property and stream. Analytics access and permission to publish a Tag Manager container are separate. Save the existing container version or configuration so an implementation error can be reversed.

2. Create or Repair the Property and Web Data Stream

If the existing property serves the correct business and website, repair it rather than splitting collection unnecessarily. Otherwise, create a GA4 property with the appropriate name, reporting time zone, and currency, then add a Web data stream for the site’s canonical domain. Review enhanced measurement deliberately. Automatic scroll or form events do not necessarily represent a completed reading session or a successful lead.

 

Conceptual tracking installation audit with one active implementation and other possible routes kept separate.

3. Choose One Maintained Installation Method

A supported CMS integration, Google Tag Manager, or direct Google tag can work. Choose the route your team can maintain and audit the existing implementation first. For WordPress, check whether a maintained integration already sends data to the intended stream. Adding another plugin or tag for the same destination can inflate page views and events.

For Tag Manager, follow Google’s current Analytics setup instructions. The recommended Google Analytics Destination workflow uses Tags → New → Tag Configuration → Google Analytics → Google Analytics. Enter the intended tag ID and configure the appropriate initialization trigger. The alternative Google tag workflow uses a Google tag with its tag ID and initialization trigger. Use Preview and Tag Assistant to test the intended pages; after validation, Submit a clearly named container version. Saving a tag alone does not publish it.

If installing directly, add Google’s supplied tag through a maintained deployment method at the documented location near the opening <head>. Avoid fragile edits to a parent theme that an update can overwrite. Make sure the intended pages have coverage and that overlapping CMS, direct-code, and Tag Manager installations do not independently send the same events.

4. Define Events Around Successful Business Actions

Write down each important action, its trigger, useful parameters, and the test that proves it works. Prefer suitable recommended events, such as generate_lead or purchase, and validate the required ecommerce values and transaction IDs where applicable. Register custom dimensions only when needed for reporting; avoid unnecessary high-cardinality identifiers and sensitive information.

For example, a form button click or a directly accessible thank-you page is not proof of a lead. Fire the lead event after the application confirms a successful submission. Test invalid submissions, double clicks, and page refreshes so they do not create false outcomes. Compare your own test with the backend record. Marking an event as a key event neither implements its tracking nor retroactively reclassifies past events; creating an advertising conversion is a separate decision. Record the definition and counting method.

5. Test Collection, Consent, and Duplicate Events

Use Tag Assistant to inspect tag behavior, Realtime to check incoming activity, and DebugView with a debug-enabled test device to inspect events and parameters in the intended property. Check both successful and unsuccessful actions before trusting the totals.

Test Expected evidence If the result is wrong
Page load and a client-side route change One intended page_view per page or route, with the correct URL Check overlapping tags and automatic plus manually sent page views
Successful lead or purchase One correctly defined event with the expected non-sensitive parameters Check the success trigger, event name, value, currency, and transaction handling
Invalid submission, double click, or refresh No false lead or duplicate purchase Check success validation and duplicate-event protection
Consent choices Collection follows the configured choice and implementation Check the consent platform, defaults, updates, and tag order
Campaign link and checkout domains Expected campaign attribution and tracking continuity Check UTM parameters, cross-domain settings, and unwanted payment referrals

Consent mode communicates consent signals; it does not obtain permission from visitors or bypass their choices. Basic and advanced implementations behave differently, and modeling has eligibility and feature limits. Never send ordinary form messages, email addresses, or other personally identifiable information as Analytics event parameters. Document the intended collection behavior and its gaps.

6. Protect Data Quality Before Setting a Baseline

Review internal-traffic and developer-traffic rules carefully. GA4 data filters have Testing, Active, and Inactive states. Test exclusions before activation: an active exclusion permanently discards affected incoming data, unlike a temporary report filter. When an event is missing, check the property, published tag version, page coverage, trigger, consent state, parameters, and filters in that order.

Allow standard report processing time—often 24–48 hours—rather than treating Realtime as the final report. Record the date reliable collection began, event definitions, time zone, and coverage. Compare complete periods with consistent definitions and reconcile important outcomes with the CRM or order system. Different scopes and privacy limits can produce legitimate differences between systems.

Review retention settings for the analyses you need: user-level and event-level exploration availability differs from aggregated reporting. Plan exports where necessary. Recheck tracking after theme, plugin, form, consent-platform, or checkout changes, and keep a small change log so a future jump or drop can be explained.

QA evidence cards for a confirmed form submission, a rejected invalid submission and duplicate-event checks.

 

How to Use Google Analytics for SEO

GA4 does not replace an SEO platform or Google Search Console. It becomes useful for SEO after the click: it shows what organic visitors do on the website, which landing pages engage them, and whether search traffic contributes to key events and revenue.

Connect Google Search Console

Link the Search Console property for your site to its GA4 web data stream. The Search Console integration adds two reports that answer different questions:

  • Google Organic Search Queries: Shows which Google searches generated impressions and clicks, along with click-through rate and average position. Its metrics come from Search Console.
  • Google Organic Search Traffic: Shows landing pages with Search Console metrics, such as clicks, alongside GA4 metrics, such as engagement and key events. Compare those measures at the landing-page level.

If the reports are missing from the menu after linking, go to Reports → Library and publish the Search Console collection. The collection is unpublished by default.

Evaluate Organic Landing Pages

Start with landing pages that receive organic sessions. Compare engagement, key-event rate, revenue, and device or country segments. A page with strong search visibility but weak engagement may have an intent mismatch, a slow experience, unclear content, or tracking problems.

Separate Traffic Quantity from Traffic Quality

A rise in organic users is valuable only when those visitors match the intended audience and complete useful actions. Analyze the source, landing page, location, device, engagement, additional pageviews, and key events together. Sudden growth with extremely short engagement and no downstream activity deserves investigation.

Read more: How to Track User Behavior from Different Traffic Sources in GA4

What Does “Not Provided” Mean in Google Analytics?

Google Analytics generally does not reveal the organic search query for each individual visit. Those keywords commonly appear as “(not provided)” because search queries are not passed to analytics at the user-session level.

To study keyword performance, use Google Search Console for aggregated query impressions and clicks, then connect that information with GA4 landing-page behavior. Do not try to assign a Search Console query to a specific individual user or session; the tools use different scopes and processing methods.

Small analyst comparing aggregated search evidence with organic landing-page engagement and confirmed outcomes.

 

Google Analytics Privacy and Data Limitations

Analytics data is not a perfect record of every visitor. Consent choices, browser protections, ad blockers, tag failures, cookie restrictions, cross-device behavior, reporting identity, thresholds, modeled data, and processing rules can all affect the numbers.

Configure consent and retention settings according to applicable laws and business requirements. Avoid sending personally identifiable information to Google Analytics. Access should also follow the principle of least privilege so users receive only the permissions they need.

When accuracy matters, compare GA4 with other evidence such as Search Console, advertising platforms, CRM records, ecommerce data, CDN or WAF analytics, and server logs. Differences between systems are normal because each platform defines and processes activity differently.

Universal Analytics vs Google Analytics 4

Universal Analytics was session-oriented and used categories, actions, and labels for many interactions. GA4 uses an event-based model and supports combined web and app measurement, explorations, audiences, modeled insights, and BigQuery export.

Standard Universal Analytics properties stopped processing new data on July 1, 2023, and the Universal Analytics 360 processing extension ended on July 1, 2024. Access to Universal Analytics properties was removed starting in July 2024. These are historical shutdown dates, not a migration deadline that is still ahead.

Google’s migration guidance confirms that Universal Analytics history cannot be imported as GA4 history. Keep any previously exported UA reports in a separate archive and document changes in measurement definitions. GA4 only contains data collected through its own implementation; it cannot reconstruct visits that were never collected. Historical comparisons must account for the platforms’ different definitions and collection models.

Separate analytics and order records with a consent-related measurement gap and a reconciliation notebook.

Which GA4 Reports Should a Beginner Check?

Begin with a small, repeatable review instead of scanning every screen:

  • Realtime: confirm that current tracking and campaign links work.
  • Traffic Acquisition: compare session sources, mediums, and campaigns.
  • Landing Page: identify the first pages visitors see and how they perform.
  • Pages and Screens: evaluate content consumption and event activity.
  • Events and Key Events: confirm that important actions are measured correctly.
  • Tech and Demographics: investigate device, browser, country, or city patterns.

Use a consistent date range and compare it with the previous period or the same period last year when seasonality matters. Use GA4 annotations to mark tag changes, campaign launches, and site outages. In a report with a line chart, right-click the relevant point, choose Add annotation, and record what happened and when.

Read more: Content Marketing: Strategy, Types and Metrics

Final Takeaway

Google Analytics 4 is a measurement system, not an automatic answer generator. It can show how users arrive, what they do, and whether important outcomes occur, but the reports are only as trustworthy as the implementation and the questions behind them.

Start with a clean property, validated tracking, a short list of meaningful events, and clear business goals. Combine GA4 with Search Console and independent operational data, then judge every traffic source by relevance, engagement, and outcomes—not visitor count alone.

Frequently Asked Questions

Quick answers to common questions about Google Analytics

Google Analytics 4, commonly called GA4, is Google's analytics platform for measuring website and app activity. It uses an event-based data model to report how users arrive, interact with content, and complete important actions.

Google Analytics is used to measure traffic sources, landing pages, user activity, content performance, leads, sales, audiences, devices, campaigns, and other business outcomes. Its value comes from connecting visits to meaningful actions.

GA4 records interactions as events. Events can describe page views, clicks, searches, form activity, purchases, and other actions. Important events can be marked as key events so teams can evaluate performance against business goals.

Key events are collected events marked as important business outcomes, such as a successful lead submission, registration, or purchase. Marking an event does not create its tracking or retroactively reclassify historical events. Validate the success trigger and counting method; advertising conversions are configured separately.

Start with Realtime to verify collection, Acquisition to understand traffic sources, Engagement to review pages and events, and key-event or ecommerce reports to measure outcomes. Use Explorations when you need deeper custom analysis.

Connect Search Console, segment organic traffic, evaluate landing pages, track key events and revenue, compare devices and countries, and investigate whether organic visitors complete useful actions. Search Console measures search visibility, while GA4 measures behavior after the click.

Users represent people or devices that interact with the site, while sessions represent groups of interactions during visits. One user can generate multiple sessions, so both metrics should be interpreted with events, engagement, and conversion outcomes.

No. Historical Universal Analytics data cannot be imported into GA4 as GA4 history. Keep any reports or data exported before UA shutdown in a separate archive. A new GA4 implementation cannot reconstruct visits that were never collected.

Not necessarily. First identify its owner, destination tags, streams and actual incoming events. Repairing a suitable existing property may be preferable to splitting collection across another property, but verify that it serves the correct business and website.

Check the intended property with Realtime and debug-mode tests in DebugView, supported by Tag Assistant. Test representative pages, successful actions, failed actions, repeated navigation and consent choices. Then allow report processing time before evaluating the baseline.

Choose a maintained route that fits your website and team. A CMS integration, Tag Manager or direct Google tag can work. Audit existing tracking first and avoid independently installing duplicate measurement through several routes.

No. Consent choices, technical limitations and privacy controls affect observability. Behavioral modeling has eligibility requirements and does not support every feature. Document the intended consent behavior and limitations rather than treating modeled reports as a complete visitor log.

Bernard
Written by

Bernard

Sharing practical insights to help websites attract better traffic and grow with confidence.

Join the conversation

Comments

Leave a Comment