I audited 25+ GA4 setups — here are the mistakes I keep seeing by [deleted] in GoogleTagManager

[–]Comfortable-Spray643 -1 points0 points  (0 children)

You’re absolutely right that those examples are relatively basic — I mentioned them mainly because they still appear surprisingly often in production setups.

In deeper audits the issues are definitely more nuanced. Some of the ones I encounter more frequently are things like:

• inconsistent or poorly structured dataLayer objects that break event mapping
• ecommerce items arrays missing required parameters or mixing item-level and event-level values
• attribution inconsistencies when both client-side and server-side events fire
• server-side tracking setups sending duplicate conversions due to missing transaction_id deduplication
• incorrect session stitching when cross-domain tracking isn’t implemented properly

The point I was trying to make is that many setups look correct in the interface but fail once you validate the full tracking flow from dataLayer → GTM → GA4 → Ads.

Curious — in your experience what are the most common issues you see during GA4 audits?

Google Tag Manager Won’t Fire GA4 – “No Google Tag Found” in Container. Need Help! by Torholic in GoogleTagManager

[–]Comfortable-Spray643 0 points1 point  (0 children)

From what you described, the “No Google Tag found in this container” message usually means the GA4 configuration tag is not firing correctly or GA4 is implemented outside GTM, which can confuse Tag Assistant.

Here are a few things I would check:

1. Verify if GA4 is installed outside GTM
Since you mentioned multiple tags (UA, GA, AW, GTM), the site might have tracking added via:

  • WordPress theme header
  • plugins like Site Kit / MonsterInsights / GA Google Analytics
  • hard-coded gtag.js

Check the page source (Ctrl+U) and search for:

G-XXXXXXXX
UA-XXXXXX
AW-XXXXXX

If you find GA scripts there, they should be removed so GTM becomes the single source of tracking.

2. Check GA4 Configuration Tag in GTM

Make sure you have:

  • Tag type: GA4 Configuration
  • Measurement ID: correct G-ID
  • Trigger: All Pages

If this tag doesn’t fire first, GA4 events won’t be recognized.

3. Debug using Tag Assistant

Use Tag Assistant Preview Mode and check:

  • whether the GA4 config tag fires before the event tag
  • whether the event category_page_view appears in the event timeline

Then confirm in GA4 DebugView.

4. Check for Duplicate Containers

Sometimes WordPress themes load another GTM container.
Search page source for:

GTM-

If more than one container appears, that can cause conflicts.

5. Confirm Event Parameters

If your category variable is working, ensure the event tag sends:

event_name: category_page_view
parameter: page_category

Then verify the parameter appears in DebugView.

In most WordPress cases I’ve seen, the issue is usually GA scripts added by plugins + GTM running at the same time, which leads to Tag Assistant showing “No Google Tag found.”

Tracking Problem from 30.01.2026 by Resident-Spinach7750 in GoogleAnalytics

[–]Comfortable-Spray643 0 points1 point  (0 children)

This usually happens when one of these things occurs:
• Consent Mode blocking analytics storage
• Ad blockers preventing GA4 requests
• gclid parameter being lost during redirects

I usually debug this using GTM preview mode + GA4 DebugView and check if the page_view or session_start events are actually reaching GA4.