THE DIRECT ANSWER
A tag on the page is not proof that analytics works. Check the ID, consent path, command queue, live hit, and Realtime report before you trust the numbers.
The short answer
When Google Analytics says it has no data, check more than whether the tag is installed. The tag can be present, use the right ID, and still fail to send a page view.
Use five checks: the exact ID, the consent path, the command queue, a sent hit, and the GA4 Realtime report. The last check matters most because it proves the result reached the property.
Our tag was there, but the result was not
On July 31, 2026, my GA4 page said it had received no website data. The measurement ID was on the live site. The Google tag script loaded. There were no page errors. That looked close to done, but it was not done.
Tag Assistant found the correct Google tag and destination. It also showed the real problem: no hit had been sent. That one line separated an installed tag from working analytics.
Check the property and consent path first
Start with the exact measurement ID. Make sure the live site and the GA4 property show the same letters and numbers. This catches a common mistake: a good tag pointed at the wrong property.
Then test the privacy choice. On my site, analytics loads only after a visitor allows it. That rule stayed in place. A repair is not complete if it gets data by ignoring the visitor’s choice.
Compare the loader with the official pattern
Google’s setup guide uses a small command queue. Our loader put the commands into a normal JavaScript array. Google’s example uses the function’s native arguments object. The two looked similar in code, but the result was different.
We changed that one part to match Google’s documented pattern. We did not add ads, weaken consent, or send form details. Small setup code should be copied carefully because one quiet mismatch can stop every report that follows.
Use Realtime as the finish line
After the repair went live, the GA4 Home page still showed its older setup warning. The Realtime report told the current story. It showed one active user, three page views, and the page_view, first_visit, session_start, and user_engagement events.
Google says Realtime is the place to validate current Analytics data. A setup card may take time to refresh. Use the live report for the first proof, then check the normal processed reports the next day.
Leave a record someone else can check
Write down the property, measurement ID, page tested, consent choice, event seen, time checked, and person who owns the next review. Do not save passwords, cookies, or private visitor details.
This record turns a one-time fix into a repeatable test. If data stops later, the next person knows what working looked like and where to start.
ORIGINAL WORKSHEET
The five-check analytics test
Run these checks in order. Do not call analytics ready just because a tag appears in the page code.
- 01 · IDDoes the site use the exact measurement ID from the right GA4 property?Copy the ID from GA4 and compare every letter and number.
- 02 · ConsentDoes the tag load after the visitor allows analytics?Test both choices. Accepted visits may measure; declined visits must stay private.
- 03 · QueueDo the tag commands match Google’s current setup pattern?Compare the loader line by line with Google’s official example.
- 04 · HitDoes Tag Assistant or the browser show a Google Analytics request?A loaded script is not enough. Look for a sent page-view hit.
- 05 · RealtimeDoes GA4 show the visit, page, and event?Use Realtime as the final proof, then check processed reports the next day.
SOURCE RECORD
Check the original sources
Four takeaways
- A tag on the page is not proof that data reached GA4.
- Check the exact ID and privacy choice before changing code.
- Compare the loader with Google’s current official example.
- Use Realtime as proof, then check processed reports the next day.
THE LEADERSHIP RECORD
Technology leadership requires judgment
The country needs leaders who can understand powerful technology without becoming distracted by hype. My standard is to make new tools useful, keep people responsible for important decisions, protect the truth, and measure whether the work actually improves.
This article is one part of a larger public record: learning in public, taking responsibility, and preparing for leadership at the highest level.
STAY IN TOUCH
Follow the record as it is built.
Tim shares plain-English lessons from building companies, serving communities, improving institutions, and preparing for leadership at the highest level.