Upgrading to Google Analytics 4: A Step-by-Step Guide
By Toy Wen Da, Co-Founder · Updated · 12 min read · scored 91/100
Upgrading to Google Analytics 4 means creating a GA4 property, connecting it to your website or app with a new data stream, and rebuilding your key events as conversions. Before you trust any report, check that data is actually flowing. Universal Analytics no longer processes new data, so GA4 is the only analytics setup available to you now.

What actually changed between Universal Analytics and GA4
Universal Analytics organized everything around sessions and pageviews. Open a site and that was a session; load a page and that was a pageview. Every report assumed this shape.
GA4 throws that model out and tracks events instead. A pageview is now just one kind of event, sitting alongside scrolls and clicks, video plays, form submissions and whatever else you define. That single change is why your reports look so different the moment you finish upgrading to Google Analytics 4: the underlying data model isn't the old one with a new skin.
Side-by-side: Universal Analytics vs. GA4
| Feature | Universal Analytics | GA4 |
|---|---|---|
| Core data unit | Sessions and pageviews | Events (pageview is one event type) |
| Platform coverage | Mostly desktop web | Unified web and app tracking in one property |
| Default metric for engagement | Bounce rate | Engagement rate and engaged sessions |
| Data processing | Stopped July 1, 2023 (July 1, 2024 for 360) | Live, ongoing |
| Custom insights | Custom reports and dashboards | Up to 50 custom insights per property, plus Explore reports |
| Data export | Limited | Native BigQuery export |
| Predictive data | None | Machine-learning-based predictive metrics (e.g., purchase probability) |
The event model is also why GA4 can tell you things UA never could, such as whether someone finished scrolling a blog post instead of just loading the page. If you want to know which specific reports to open first once your property is live, this guide to the GA4 reports worth checking covers them in order.

Why this upgrade stopped being optional

Google set a hard line on Universal Analytics, as confirmed in its own Analytics Help Center. Standard UA properties stopped processing new data on July 1, 2023, and Analytics 360 properties followed on July 1, 2024. After those dates, UA interfaces became read-only archives of old data rather than a working analytics tool.
A site owner who hasn't finished the GA4 migration therefore isn't "still on the old version"; they're simply not collecting current analytics data. Whatever traffic has arrived since the cutoff for their account type was never recorded anywhere.
The data-loss problem nobody can skip
Here's the part that catches people off guard: you cannot import your Universal Analytics history into GA4. The two platforms store and structure data too differently for Google to offer a migration path for historical numbers, as Google's own Analytics documentation explains. Every GA4 property starts from zero, however many years of UA data came before it.
This is why Google Analytics experts kept pushing people to finish the GA4 setup early. Every month without a working GA4 property is a month of historical data you'll never get back. If your account was already active before the cutoff, you likely have a head start, and if not, your GA4 history begins the day you finish setup, whenever that is.
For a broader look at how Google has reshaped Analytics beyond the UA shutdown, see this rundown of what's changed and what to act on now.
How to upgrade to Google Analytics 4, step by step
You need editor or administrator access to the Google Analytics account before starting, because without it none of the setup screens below will be available.
Step 1: Create your GA4 property
- Sign in to your Google account and open Google Analytics.
- Click Admin in the lower-left corner.
- In the Account column, confirm you're in the right account, then click Create property under Property.
- Name the property and set your reporting time zone and currency. Every visit gets timestamped against this zone, so pick the one your business actually operates from.
- Choose an industry category and business size, then select how you plan to use Analytics. These answers only shape which default reports GA4 shows you first, and you can change them later.
- Accept the Analytics Terms of Service and the Data Processing Amendment, then finish creating the property.
Step 2: Add a data stream
A property on its own collects nothing; it needs a data stream to tell it where the data comes from.
- In Admin, under Property, click Data Streams and then Add stream.
- Choose Web, iOS app or Android app, whichever matches what you're tracking.
- For a website, enter your URL and a name for the stream, then click Create stream.
- For an app, you'll be asked for the app name and store details and then walked through adding the Firebase SDK.
Step 3: Install the tracking code
For a website stream, GA4 gives you a Measurement ID that starts with "G-". You have two main ways to get it onto your pages.
- Google Tag: paste the tag snippet GA4 provides into the
<head>of every page, or into your site's global header template. - Google Tag Manager: if you already run GTM, create a GA4 Configuration tag using the Measurement ID instead of editing page code directly.
Most CMS platforms and page builders now have a dedicated field for the Measurement ID, which is simpler than editing templates by hand.
Step 4: Verify data is actually flowing
Open Reports, then Realtime, and browse your own site in another tab. Your visit should appear within a minute or two. If nothing shows up, the tag isn't firing, so check that it's on every page template and not just the homepage, and that no consent or tag-blocking tool is stripping it out.

Rebuilding events, conversions and reports in GA4

Getting data to flow is the easy half of a GA4 migration. The harder half is making the reports mean something to your business again.
Mark your key events as conversions
GA4 captures several events automatically, such as page views, scrolls and outbound clicks, plus site search and video engagement. Your actual business goals (a purchase, say, or a form submit or demo request) usually need to be set up as their own events first.
- Go to Admin, then click Events under Property.
- Find or create the event that matches your goal, for example
form_submit. - Toggle Mark as conversion next to it.
Once marked, that event shows up in conversion reports and can feed into Google Ads bidding. Skipping this step is the most common reason a brand-new GA4 property looks "broken", when in fact it has just never been told what counts as success.
Rebuild your custom reports and explorations
None of your old UA custom reports carry over, and neither do segments or goals. You'll rebuild the ones that still matter in GA4's Explore section, which offers templates for funnel analysis and path exploration, plus cohort tracking, none of which existed in UA.
If you've gone looking for a specific GA4 report and come up confused by where things moved, this walkthrough on finding, reading and fixing a GA4 report covers the navigation changes directly.
Reconnect your other tools
Universal Analytics connected to a web of other platforms, and none of those links survive the migration automatically. Go through each one.
- Google Search Console: relink it under Admin > Property > Search Console Links so organic query data flows alongside your other traffic.
- Google Ads: relink the account to keep conversion data feeding your campaigns.
- CMS SEO plugins: if you run WordPress with Yoast, the Measurement ID needs re-entering, and this guide to connecting GA4 and Yoast shows where that field lives.
- CRM integrations: if marketing and sales both pull from Analytics, something like HubSpot needs its own reconnection, since the old link pointed at a UA property ID that no longer exists.
While you're reviewing traffic sources, check what GA4 is quietly bucketing as unattributed. Direct traffic that's really something else is a common side effect of incomplete tagging after a migration, and it inflates a channel that tells you almost nothing useful.
When GA4's own tools are enough, and when they aren't
GA4 is a genuinely capable free tool, but it wasn't built to answer every question you'll have about your site's SEO performance.
| Situation | Is GA4 alone enough? | Why |
|---|---|---|
| Checking traffic trend for your whole site | Yes | Standard acquisition reports cover this well out of the box |
| Diagnosing a traffic drop on one specific URL | Partially | GA4 shows the drop; Search Console shows if rankings also fell |
| A one-off question ("did last week's campaign work?") | Yes | Explore reports and date comparisons handle one-time questions fine |
| A recurring SEO problem across dozens of pages | No | GA4 has no built-in way to flag or track recurring page-level issues over time |
| Confirming a backlink is driving referral traffic | Partially | GA4 shows referral sessions; it can't confirm the link still exists or is followed |
| Tracking keyword rankings alongside traffic | No | GA4 has no ranking data at all; that lives only in Search Console or a rank tracker |
GA4 is strong on what happened on your site and weak on why, especially when the why involves Google's crawling and indexing behavior rather than visitor behavior. Search Console data and dedicated SEO monitoring fill that gap.
Backlinks show the same limit. GA4 can show you referral sessions from a domain, but it can't tell you whether a link is still live, nofollowed or passing any ranking value. This comparison of what GA4 can and can't tell you about backlinks lays out exactly where that line sits.
Google itself frames Search Console and Analytics as complementary tools rather than substitutes. Search Console reports how Google crawls and indexes your pages, which is data GA4 was never designed to hold, and you can read more on how Google frames crawling and indexing at Google Search Central.
Common mistakes when upgrading to Google Analytics 4
Most problems people run into after migrating to GA4 trace back to one of a handful of causes.
| Mistake | What it looks like | The fix |
|---|---|---|
| No events marked as conversions | Conversion reports show zero, even with real sign-ups happening | Go to Admin > Events and toggle "Mark as conversion" on your key events |
| Tag only on the homepage | Realtime shows traffic on one page, nothing deeper into the site | Add the Measurement ID to the global header template, not a single page |
| Search Console never relinked | Organic queries report is empty | Relink under Admin > Property > Search Console Links |
| Expecting UA history inside GA4 | "Where did my old data go?" after finishing setup | It never transfers; GA4 reporting starts the day the stream goes live |
| Treating GA4 like a ranking tool | No way to see keyword position trends | Keep Search Console or a rank tracker running alongside GA4 |
| Ignoring the data retention setting | Reports older than a few months stop returning user-level data | Set retention to the longest option under Admin > Data Settings > Data Retention |
The retention setting trips up more people than you'd expect. GA4's default retention window for user-level and event-level data is short unless you change it, per Google's Analytics Help Center guidance on data settings, so set it to the maximum during initial setup rather than after you've lost a few months of detail.
A less obvious mistake is assuming every niche needs the same GA4 setup. A site in a tightly regulated or heavily scrutinized space benefits from tracking engagement events more carefully than average, and crypto content is a good example of where Google plays it safe. Trust signals matter more when Google's own systems are cautious about the topic.
Access and permissions mistakes worth flagging separately
Three more issues show up around who can see what, and what looks like a tracking failure, after a migration.
- If you've just added or restructured a site alongside the GA4 switch, it's worth knowing how long Search Console typically takes to index a new page, so you don't mistake a normal delay for a tracking failure.
- Teams often give a contractor or agency full Analytics access during a migration and forget to scope it down afterward. This guide to sharing Search Console access the right way applies the same logic to Analytics permissions: grant the narrowest role that gets the job done.
- If your GA4 referral reports show odd spikes from directory sites, run a parallel check of how to find and fix Google My Business citation issues, because outdated listings can send oddly shaped traffic that muddies your referral data.
FAQs
Do I need to upgrade to Google Analytics 4 if my site is small?
Yes. Universal Analytics stopped collecting new data for every property, regardless of site size. A small site without GA4 set up has no current analytics data at all, not a simplified version of it.
Will I lose my old Universal Analytics data forever?
Your UA data isn't deleted immediately, but Google has said it won't remain accessible indefinitely, and it never transfers into your new GA4 property. Export anything you want to keep as a static record, since GA4 starts its own history from the day you finish setup.
How long does a GA4 migration actually take?
For a straightforward website, creating the property, adding a data stream and installing the tag can take under an hour. Rebuilding custom reports, conversions and integrations properly usually takes longer, often spread across a few sessions as you confirm each piece works.
Can I run GA4 and Universal Analytics at the same time?
In the past you could, and many sites ran both during the transition window. Now that UA no longer processes new data, there's nothing left to run in parallel, and GA4 is the only option collecting current information.
Why do my GA4 numbers not match my old UA numbers?
They aren't supposed to match, because GA4 counts events and defines sessions differently than UA did. Metrics like bounce rate, pageviews and even total users can shift from the platform change alone, with no actual change in your traffic.
Talk to the team about what your GA4 data is really telling you
Upgrading to Google Analytics 4 gets your tracking current, but a working property isn't the same as a property you're reading correctly. That takes watching the right reports over time, not just finishing setup once. If you want a second set of eyes on what your traffic and SEO data show once GA4 is live, talk to the team, who will build a sample report around your own site.
Resources / References
Sources
About the author
SearchBlueprint researched, wrote and scored this article with the content pipeline our customers run on their own sites. The score in the byline is what our content engine gave this page before it published. Nothing here is reviewed by hand, which is the point: it is the product's output, published where anyone can check it.