GA4 Not Tracking After a Website Launch? Six Checks to Run Today
GA4 not tracking after a new website launch can look like your traffic disappeared overnight. Many El Paso businesses launch a new site, watch analytics drop to almost nothing, and assume the redesign failed. So they panic, or they blame the new site. In many cases, though, the visitors are still there; the tracking just broke. This guide walks through six checks you can run today to find out which one it is.
GA4 Not Tracking: Traffic Drop or Tracking Gap?
Why GA4 Not Tracking Is So Common After a Launch
First, a new site is new code. So everything the old site did quietly, such as loading the analytics tag, has to be set up again. The most common cause is simple: the GA4 tag was never added to the new site's templates. Changed form tools and missing key events are close behind.
In fact, it happens because launches are busy. The design, the content and the redirects take all the attention. As a result, analytics becomes a last-minute item, or nobody's item at all. Also, a site can look perfect to a visitor while sending no data at all, so nobody notices until the monthly report.
So the good news is that, in our experience, GA4 not tracking is usually fixable in an afternoon. Outcome: you find out whether you lost visitors or just lost the count, and you fix the right thing.
The Six Checks at a Glance
Here are the six checks in one view. Run them in order, because the first ones rule out the biggest causes.
| Trait | What it means | Where it comes from | What you notice |
|---|---|---|---|
| Tag on every template | The code loads on all pages | Your site templates | Every page sends data |
| Realtime test | Your own visit shows up | GA4 Realtime report | Proof the tag fires |
| ID and property | Data goes to the right place | GA4 admin settings | Numbers in the right account |
| Key events | Forms and calls are counted | GA4 events setup | Leads show in reports |
| Blockers | Nothing stops the tag | Consent, caching, staging | Data returns after fixes |
| Second opinion | An outside traffic count | Search Console | Real traffic confirmed |
Check 1: Is the GA4 Tag on Every Page Template?
Start with the tag itself. Most sites are built from a few templates: a home page, a service page, a blog post, a contact page. So the GA4 tag needs to be on every one of them, on the live site. A tag on the home page alone means every other page goes dark.
Then check with a tool. Google Tag Assistant shows whether a Google tag loads on a page. Also try a few different page types, not just the home page. Google's Google tag documentation explains how the tag should be installed.
Check 2: The Realtime Report Test
Basically, this is the fastest test there is. First, open the Realtime report in GA4. Next, visit your live site on your phone, using cell data instead of the office Wi-Fi. Then watch the report. If your visit doesn't show up within a minute or two, the tag is not firing.
If it does show up, good: the basic tag works. However, that doesn't mean everything is right. So keep going, because forms and calls are a separate check.
Check 3: The Right Measurement ID and the Right Property
Also, sometimes the tag fires, but it sends data to the wrong place. For example, the developer used a test property, or copied the measurement ID from another site. So check that the measurement ID on your site matches the one in your GA4 property. It starts with "G-" and appears in your GA4 admin settings.
Also check who owns the property. If an old agency set it up under their account, the history may not move with you. For more, read who owns your GA4 property. And if nobody can get in at all, see recovering GA4 admin access.
Check 4: Key Events for Forms and Calls
Page views are only half the story. In particular, the leads matter more. However, GA4 does not reliably track form submissions on its own. Form submissions and calls usually need key events set up, and those often need rebuilding after a redesign, especially if the new site uses a different form tool.
So submit each form yourself, then check whether the key event appears. Next, tap the phone link and check that, too. If the events are missing, they need to be rebuilt for the new site. Outcome: your reports show leads again, not just visits.
Conversion tracking from day one →Check 5: Consent Banners, Caching and Staging Settings
Next, some settings block tags without anyone noticing. First, consent banners. If your banner is set up so tags wait for permission, check that tags load correctly once a visitor agrees. Next, caching. A caching or speed tool can sometimes strip or delay scripts, including the analytics tag.
Then check for leftover staging settings. Sometimes a setting meant for the test site, such as a script block or a search engine block, gets carried over to the live site. In short, if the tag is installed but data still doesn't arrive, one of these is a likely suspect.
Check 6: Search Console as a Second Opinion
Finally, get a second opinion on your traffic. Google Search Console counts clicks from Google search, and it does not use your GA4 tag. So it is an independent check. Compare clicks in Search Console with sessions in GA4 for the weeks before and after the launch.
If Search Console clicks are steady while GA4 shows a drop, the problem is tracking, not traffic. By contrast, if both dropped, you may have a real traffic issue, such as missing redirects. Google's Analytics and Search Console help explains both reports. Also, for a simpler way to read the numbers, see a marketing report versus a dashboard.
Put Analytics on the Launch Checklist So GA4 Not Tracking Never Happens Again
The best fix is prevention. So add analytics to your launch checklist, right next to redirects and forms. Here is the analytics part of that list.
- Before launch: the tag. Confirm the GA4 tag is on every page template of the new site, not just the home page.
- Before launch: the ID. Check that the measurement ID matches your own GA4 property, not a test one.
- Before launch: key events. Rebuild key events for every form and phone link on the new site.
- Launch day: the Realtime test. Visit the live site from your phone and watch your visit appear.
- One week later: the second opinion. Then compare GA4 sessions with Search Console clicks, and look for a gap.
In our experience, the whole step takes less than an hour across launch week. As a result, a GA4 not tracking scare turns into a quick checklist item instead of a month of missing data.
Also decide who owns this step. After all, when analytics is everyone's job, it is nobody's job. For the full list of what to have ready before a build, read what to prepare before a website build.
Frequently Asked Questions
Q1 What should I check first if GA4 is not tracking?
Q2 Why is GA4 not tracking after my website redesign?
Q3 How do I check if GA4 is working?
Q4 Does GA4 track form submissions automatically?
Q5 How can I tell if my traffic really dropped?
Want a One-Time Tracking Check? DM SITE
If the numbers dropped after a launch, don't blame the new site yet. Instead, let us run the six checks, fix the tag and rebuild the key events. It is one job, not a retainer, and you get your reporting back. GA4 not tracking is usually a fixable problem, not a failed website.
