If you are trying to migrate Universal Analytics to GA4, the first thing to know is that the move is no longer optional and the old reports are not coming back. Universal Analytics stopped processing new data in July 2023, and Google began deleting historical UA data in mid-2024. There is nothing left to wait for. This checklist walks through the UA to GA4 migration in plain language — create the property, set up the data stream, find the measurement ID, turn on enhanced measurement, rebuild your goals as key events, and verify the whole thing is working.
None of this requires you to be an analyst. It requires about an hour and a willingness to click through a setup flow that Google did not make especially friendly. Work through the steps in order and you will come out the other side with a GA4 property that actually records what matters to your business.
Why Universal Analytics is gone (and not coming back)
Universal Analytics was the version of Google Analytics most small businesses installed any time between roughly 2012 and 2020. It is the one with the bounce rate everyone watched and the goals you set up once and forgot about. Google retired it. The dates matter, so here they are honestly: standard UA properties stopped processing new hits on 1 July 2023, the paid Analytics 360 version followed in 2024, and Google then began permanently deleting historical UA data. If you never exported your old reports, that history is most likely gone.
This is why “switch to GA4” is not a project you can keep postponing. If your site is still firing the old UA tag, it is collecting nothing — the receiving end was switched off years ago. Any month you spend without a working GA4 property is a month of data you will never get back. The good news is that the GA4 setup itself is a one-time job, and once it is done the data starts accumulating immediately.
Step 1: Create the GA4 property and data stream
Everything in GA4 lives inside a property — the container that holds all the data for one website or app. If someone set up a GA4 property for you during the transition, you may already have one; check under Admin before you create a duplicate. If not, you will create one now.
In Google Analytics, go to Admin (the gear icon), and under the Account column make sure you are in the right account. Then in the Property column choose Create property. Give it a clear name — your business or site name is fine — set your reporting time zone and currency, and answer the few business questions Google asks. Time zone matters more than it looks: it decides where your “day” starts, which affects every daily and weekly number you will ever read.
Once the property exists, GA4 needs to know where the data is coming from. That is a data stream — the connection between your website and the property. For a website, choose Web, enter your full site URL, and give the stream a name. GA4 will create the stream and, by default, switch on a set of automatic tracking we will cover in Step 4.
One property, one stream — to start. A common mistake is creating several properties or streams in a burst of enthusiasm. For a single website, one property with one web data stream is correct. You can always add more later; you cannot easily merge messy duplicates.
Step 2: Get the measurement ID and put it on your site
When the data stream is created, GA4 shows you a measurement ID — a code that starts with G- followed by a string of characters. This is the GA4 equivalent of the old UA tracking ID that started with UA-. It is how Google knows which property a given page belongs to. You will find it again any time under Admin → Data streams, so there is no need to memorise it.
That ID has to be installed on every page of your site. How you do that depends on your platform. If you use Google Tag Manager, you add a Google tag configured with the measurement ID. If your website builder — WordPress, Squarespace, Shopify, Wix and others — has a Google Analytics field in its settings, paste the measurement ID there. If you are editing the site code directly, GA4 gives you a small snippet to place in the <head> of every page.
Whatever the route, the principle is the same: the measurement ID must load on every page you want measured, including your thank-you and checkout pages. A measurement ID that only loads on the homepage will quietly under-report everything else.
Step 3: Turn on enhanced measurement
Here is one of the genuine improvements in GA4. In the old days, tracking things like outbound clicks, file downloads, or how far someone scrolled meant custom configuration most small business owners never attempted. GA4 does a lot of it automatically through a feature called enhanced measurement.
When you created the data stream, enhanced measurement was almost certainly switched on by default. It is worth confirming. Open the data stream under Admin → Data streams and look for the Enhanced measurement toggle. With it on, GA4 automatically records page views, scrolls, outbound clicks, site searches, video engagement, and file downloads — no extra setup. For most small content-driven sites, leaving all of these on is the right call. You can always switch off an individual event later if it adds noise.
The practical upshot: a chunk of what used to be manual tracking work now happens the moment your measurement ID is installed. That is real progress, even if the rest of the migration feels like a chore.
Step 4: Rebuild your goals as key events
This is the step people most often skip, and it is the one that determines whether GA4 tells you anything useful about your business. In Universal Analytics, the outcomes you cared about — a contact form submitted, a newsletter sign-up, a booking made — were called goals. GA4 does not have goals. It has events, and the important ones you mark as key events (Google previously called these “conversions”).
Your old UA goals did not carry over. You have to recreate them. The model is different: in GA4, everything is an event first. A form submission is an event; once you mark that event as a key event, GA4 starts treating it as a meaningful outcome and reports on it accordingly. The path is roughly: make sure the action you care about is being recorded as an event, then go to Admin → Events, find that event, and toggle Mark as key event.
Take the time to list, on paper, the three to five outcomes that actually matter for your business before you touch the interface. For most small professional service sites that is something like: contact form submitted, phone-number clicked, newsletter sign-up, and booking or quote requested. Set those up as key events and you will have a GA4 property that reports on what you care about — not just raw traffic.
What won’t carry over from Universal Analytics
Be clear-eyed about this so the migration does not surprise you later. Several things do not transfer:
- Your historical data. GA4 starts counting from the day you set it up. It does not import your UA history, and that history is being deleted by Google regardless. Your year-over-year comparisons will be thin until GA4 has been running for a full year.
- Your goals. As covered above, goals must be rebuilt from scratch as key events.
- Bounce rate, in the form you knew it. GA4 leads with engagement rate instead, and the two are not the same number measured differently — they measure different things. It is worth understanding why before you panic about a metric that looks “worse.”
- Some old reports and views. The familiar UA report layout is gone. GA4’s interface is organised differently, and a few reports you relied on may not have a direct equivalent.
That bounce-rate change trips up a lot of people. A site can look like it is failing simply because a metric was redefined — we wrote up exactly that scenario in our case study, The Bounce Rate Panic. Read it before you draw conclusions from your first few weeks of GA4 numbers.
Step 5: Verify the migration is actually working
Do not assume the setup worked because you finished the steps. Verify it, because a silent failure here means weeks of missing data. Two quick checks cover most problems.
First, open the Realtime report in GA4, then visit your own site in another browser tab. Within a few seconds you should see yourself appear as an active user. If you do, the measurement ID is installed and firing. If Realtime stays empty after a minute, the tag is not loading — recheck Step 2.
Second, test your key events. Submit your own contact form, click your phone number, or complete whichever outcome you marked as a key event. Then check the Realtime report or the Events report to confirm the action was recorded. It can take a little time for an event to show as a key event in the standard reports, so give it up to a day before concluding something is wrong.
Once both checks pass, your GA4 setup is genuinely complete. Data will accumulate from here, and the longer it runs the more useful those year-over-year comparisons become.
The honest catch: a correctly configured GA4 property is not the same as a property you will actually read. GA4 is built for analysts, and most small business owners set it up, look at it twice, and never open it again. The setup is the easy part. Getting something useful out of it, week after week, is where the real gap is.
Where WebSignalytics fits
WebSignalytics was built for exactly the moment after your GA4 migration is done. It connects to your Google Analytics in the background — read-only, through Google’s own secure sign-in — and emails you a plain-language report every Monday: what changed last week, why it likely matters, and what is worth your attention. No dashboards, no logging in, no learning the GA4 interface.
So you do the one-time work of setting GA4 up properly, and from then on you never have to open it. The data you just spent an hour wiring up gets read for you, every week, and translated into something you can act on in the time it takes to drink a coffee.
The whole point of migrating to GA4 is to have working data about your website. WebSignalytics makes sure that data actually tells you something — in a paragraph, not a spreadsheet.
You migrated to GA4. Now make it useful.
Connect your Google Analytics in two minutes. Your first plain-language report — what changed, why it matters, and what to do next — arrives the following Monday.
Start your 14‑day free trial