GA4 (Google Analytics 4) is Google\u2019s current analytics platform, which replaced Universal Analytics on July 1, 2023. It uses an event-based data model instead of sessions and pageviews, tracks web and app in a single property, and reduces cookie dependence — putting it in position for a privacy-first, multi-platform web.
GA4 is not "the new version of UA". It is a completely different measurement system with a different data model, different metrics, and different reports. Teams that treat it as a UA re-skin spend six months confused about why nothing matches.
What is GA4?
Google Analytics 4 is Google\u2019s current-generation analytics platform. Every user interaction — a page view, scroll, click, purchase — is captured as an event with parameters, rather than as a session that contains a page view. That single architectural change is what unlocks cross-platform tracking, granular custom measurement, and predictive metrics.
GA4 was made mandatory when Google shut down Universal Analytics on July 1, 2023 for standard properties and July 1, 2024 for GA 360. Historical UA data has since been deprecated.
Universal Analytics was built for a desktop, cookie-friendly web. GA4 was built for a mobile, cross-device, privacy-restricted web. The move is less about features and more about surviving the death of third-party cookies.
Why GA4 matters for SEO
If you rely on organic traffic, GA4 is now the only Google-native analytics option. Four reasons SEOs need to get comfortable with it fast:
- Organic traffic attribution. The Traffic Acquisition report is your primary view of organic vs paid vs direct vs referral. If it is not set up correctly, every SEO report you build is wrong.
- Content performance. The Pages and Screens report shows engagement time per page — a far better signal of content quality than the legacy bounce rate.
- Cross-platform view. A single property tracks your website and your app. UA needed separate properties and painful stitching.
- Predictive metrics. Built-in ML surfaces purchase probability, churn probability, and predicted revenue — actionable audiences that ship straight to Google Ads.
How GA4 works
Every interaction in GA4 is an event. Events have a name and up to 25 parameters, which is what allows you to slice performance any way you want.
event_name: "page_view"
page_title: "Home"
page_location: "https://example.com/"
session_id: 1729384756
# A purchase event carries the transaction context
event_name: "purchase"
value: 129.00
currency: "USD"
items: [ ... ]
Events
Everything is an event. Google groups them into four buckets: automatically collected (page_view, session_start, first_visit), enhanced measurement (scroll, outbound_click, file_download, video_start), recommended (sign_up, login, purchase), and custom (whatever you define).
Conversions
You mark any event as a conversion. Unlike UA\u2019s hard-coded goal system, GA4 conversions are flexible — a form submit, a scroll past 75%, or a signup click can all be conversions.
Audiences
Real-time user groupings you can build from any event or property. Audiences ship directly to Google Ads for remarketing without a second tag.
Exploration reports
The Exploration hub is where the analysis lives — funnel exploration, path exploration, cohort exploration, segment overlap. Pre-built reports in GA4 are intentionally sparse to push you to Explorations.
GA4 vs Universal Analytics — what actually changed
| Feature | Universal Analytics | GA4 |
|---|---|---|
| Data model | Session + pageview | Event + parameter |
| Platforms | Web only | Web + app in one property |
| User ID | Client ID + User ID | Client ID + User ID + Google signals |
| Reporting | Pre-built reports | Explorations + light reports |
| Machine learning | Limited | Predictive audiences + insights |
| Data retention | Up to 50 months | 2 or 14 months user data |
| Cookie dependency | High | Designed to be cookieless-friendly |
Real GA4 reports SEOs actually use
Four reports that answer real questions.
1. Traffic Acquisition
Filter: Session default channel group = Organic Search
# Your live organic traffic view, replaces UA "Organic Search" segment
2. Landing page report
Metrics: sessions, engaged sessions, conversions, engagement rate
# Which pages actually earn revenue from organic
3. Search Console integration
# Adds "Queries" + "Google organic search traffic" reports
# Only Google-native way to see keyword-level performance
4. Funnel exploration
Steps: page_view / scroll / form_submit / purchase
# Diagnoses the exact stage where users drop off
GA4 vs a data warehouse — where does GA4 stop being enough
GA4 solves the "what happened last week" problem. For deeper analysis, most teams stitch GA4 to a warehouse.
GA4 is enough when
- You need channel-level attribution
- You have a single product and site
- You care about last-30-days performance
- Your data volume is under GA4\u2019s free limits
- You want built-in Google Ads audience sync
Move to warehouse when
- You need multi-year trend analysis
- You need to join analytics with CRM
- Your data volume exceeds free-tier caps
- You need row-level, unsampled data
- You want to blend paid, product, and finance data
7 GA4 best practices
- Define your event and conversion strategy before you implement. A GA4 property with 200 auto-events and no conversions is noise. Pick the 5–10 events that map to revenue.
- Link GA4 to Google Search Console. This is the only Google-native path to keyword-level performance data.
- Extend data retention to 14 months. The default is 2 months. If you never change it, year-over-year reporting is impossible.
- Turn on BigQuery export. Free for standard GA4. Gives you raw event data for warehouse analysis and long-term storage.
- Build Explorations for the questions you ask every week. Pre-built reports are intentionally shallow. Real analysis happens in the Explore hub.
- Audit events quarterly. Dead events, duplicate events, and mismatched parameters accumulate silently. A quarterly audit stops the drift.
- Train stakeholders on the new model. The team that still thinks in sessions will misread every GA4 report. A 30-minute walkthrough on events + engagement rate pays for itself weekly.
Most GA4 problems come from copying UA workflows into GA4. Bounce rate is not the inverse of engagement rate. Sessions in GA4 count differently. UA "goals" are not GA4 "conversions". If a metric name looks familiar, double-check the definition before trusting it.
Common GA4 mistakes to avoid
- Not defining conversions — a GA4 property without conversions cannot power Google Ads or measure business impact.
- Ignoring event tracking setup — leaving enhanced measurement on default without custom events misses 80% of the value.
- Keeping default 2-month data retention — makes any year-over-year analysis impossible.
- Not linking Search Console — leaves organic search performance blind to the rest of GA4.
- Duplicate events from GTM and gtag.js — silently doubles conversion counts.
- Ignoring BigQuery export — the raw event stream is free and the only path to unsampled, long-term data.
Frequently asked questions
No. Google sunset Universal Analytics on July 1, 2023 for standard accounts and July 1, 2024 for 360 accounts. All historical UA data has since been deprecated.
Yes. Standard GA4 is free for all users. GA4 360 is the paid enterprise version with higher data limits, longer retention, and BigQuery export at scale.
Not directly, because most organic keyword data is hidden by Google\u2019s privacy protections. Link GA4 to Google Search Console to see impressions, clicks, and CTR by query alongside your GA4 traffic data.
Engagement rate is the percentage of sessions that qualify as engaged. A session is engaged if it lasts at least 10 seconds, includes 2 or more page views, or triggers at least 1 conversion event.
GA4 shifted from a session-based to an event-based data model, unified web and app data into a single property, added predictive metrics, and reduced cookie dependence. Most legacy UA reports do not have direct equivalents in GA4 — you have to build them in Explorations.
How theStacc helps
theStacc wires GA4 into the SEO workflow. We link Search Console, define your conversion events, and build the Explorations that answer the questions marketing teams ask every week — which content earns organic traffic, which pages convert, and where the funnel leaks. No more "GA4 is confusing, so we\u2019ll figure it out next quarter".