Installing GA4 Doesn't Mean Your Tracking Is Working
Katalaga Hakim
6 min read
Setting up Google Analytics on a website looks easier than it actually is.
You create the property, create a web data stream, get a Measurement ID, paste the Google tag into the website, and expect the numbers to start appearing.
Then you open Analytics and see a message telling you that no data has been received.
That is where people usually start wondering whether they did something wrong.
Sometimes they did. Sometimes the tag is working perfectly and Google Analytics simply has not processed everything yet. The important part is knowing the difference.
Take a new ecommerce site such as PheromoneParfums.com. The first step is not installing some mysterious piece of tracking code. It is creating the right GA4 property and connecting the website to it properly.
Inside Google Analytics, you create a new property under the correct Analytics account. Give it a name that makes sense, choose the appropriate reporting time zone and currency, and complete the business information Google asks for.
For an ecommerce business, the property should be configured around what you actually need to measure. Page visits are useful, but eventually you will want to know which products people viewed, what they added to their cart, what they purchased, how much revenue those purchases generated, and where those customers came from.
After creating the property, you create a Web data stream. This is the connection between the website and the GA4 property.
Google gives that stream a Measurement ID beginning with G-. That ID is important, but it is not the tracking itself. It is the identifier that tells Google Analytics which property should receive the data.
This is where a common misunderstanding begins.
Copying the Measurement ID is not the same thing as installing Google Analytics.
The website has to actually load the Google tag when someone visits it.
If you are working with a website where you have access to the code, Google provides a Google tag that can be installed in the site's <head> section. If the website runs on a platform such as Shopify or WordPress, there may be a better platform-specific method through an integration, plugin, app, or tag management setup.
The method matters because putting the code in the wrong place can leave you with a perfectly configured GA4 property that receives nothing.
And that is why the next step should always be verification.
The Google Analytics screen can be misleading
One of the easiest mistakes to make is looking at the main Analytics dashboard immediately after installing the tag and assuming that the numbers should already be there.
GA4 has different reporting areas, and they do not necessarily update at exactly the same time.
Realtime reporting is particularly useful when testing a new installation. Open the website in a separate browser window and visit a few pages. Then open the Realtime report in GA4.
If your visit appears there, you have strong evidence that the tag is communicating with the property.
This is much more useful than simply staring at the main dashboard waiting for numbers to change.
A new installation can also produce a confusing situation where the Analytics interface still displays a message such as "No data received" while Realtime already shows an active user.
That does not automatically mean the installation has failed.
The first thing to check is whether the website is actually sending data.
Test the website, not just the Analytics dashboard
There is a simple way to approach this.
Open the website and then open GA4's Realtime report. Browse a few pages on the site. If the visit appears, the basic connection is working.
You can also inspect the website itself.
Open the page source and search for the Measurement ID. If the ID is present in the page's code, you know the tag has at least been added to the page. If it is completely absent, the problem is probably with the installation rather than GA4 itself.
Browser extensions and privacy settings can complicate testing as well. Ad blockers and other privacy tools can interfere with analytics requests, so a clean browser session can be useful when diagnosing a new setup.
The point is to test each part of the chain rather than assuming that one screen tells you everything.
Website → Google tag → GA4 property → Realtime data → standard reports.
If the chain breaks somewhere, you need to find the broken part.
Installing the tag is only the beginning for ecommerce
There is another important distinction for ecommerce websites.
Getting pageview data into GA4 does not mean you have finished your analytics setup.
A perfume store, for example, needs more than a record saying that somebody visited the homepage.
You eventually want to understand the commercial journey.
Someone views a product. They add it to the cart. They begin checkout. They purchase.
Those actions can be represented through ecommerce events such as view_item, add_to_cart, and purchase.
Once those events are implemented correctly, GA4 becomes much more useful because you can begin connecting website behaviour with actual commercial outcomes.
You can start asking better questions.
Which products are getting attention but not purchases?
Where are people abandoning the buying process?
Which traffic sources are bringing customers rather than just visitors?
Which products generate the most revenue?
Those are the questions that make analytics valuable.
Installing the basic Google tag only gives you the foundation.
Where Google Tag Manager fits
For a small website with basic requirements, directly installing the Google tag may be enough.
But once you start tracking more things, the setup can become messy.
You might want to track form submissions, important button clicks, ecommerce events, advertising platforms, remarketing tags, and other marketing tools. Adding each piece directly into the website's code can turn tracking into a maintenance problem.
That is where Google Tag Manager can become useful.
Instead of repeatedly changing the website whenever you want to add or modify a tracking tag, you can manage many of those tags through one central system.
That does not mean every website needs a complicated tag-management setup. It means the tracking architecture should match what the business actually needs.
A five-page brochure website does not need the same measurement system as a growing ecommerce store.
The real mistake is stopping after installation
The biggest problem with analytics setup is not usually creating the property.
It is assuming the job is finished once the code has been pasted.
A proper installation has several stages.
You create the correct property. You create the web stream. You install the tag using the appropriate method. You verify that the website is sending data. You check Realtime. Then you make sure the events and ecommerce tracking you actually care about are being recorded correctly.
Only then do you have something worth relying on.
And this matters because bad analytics can be worse than no analytics.
If you believe Google Ads generated 120 purchases when the tracking is actually recording something incorrectly, you may make budget decisions based on numbers that were never accurate in the first place.
The same applies to SEO, email, social traffic and every other channel you are trying to evaluate.
Analytics should not simply produce numbers. It should give you confidence that the numbers represent what is actually happening on the website.
So when you install GA4, don't stop when the tag is pasted.
Make sure the website is sending data, make sure GA4 is receiving it, and then make sure it is recording the events that matter to the business.
That is the difference between having Google Analytics installed and actually having useful analytics.
Keep reading
Your Developer Should Never Control Your Website
A few days ago, an auto shop contacted me because they wanted their WordPress website redesigned. That part...
Paid AdsHow to Use Claude to Run a Better Google Ads Account
Most people use AI for Google Ads like they use a slightly faster copywriter. They ask for headlines. They ask...