Repository navigation
Sitewide GA4 sessions dropped 47% week-over-week (51 → 27) #74
Description
Numbers
| Metric | Prev week | This week | Change |
|---|---|---|---|
| GA4 Sessions | 51 | 27 | −47% |
| GA4 Users | 27 | 23 | −15% |
| GA4 Pageviews | 101 | 70 | −31% |
| GSC Clicks (sitewide) | 168 | 221 | +32% ✅ |
GA4 sessions and pageviews both dropped sharply while GSC clicks actually increased. This divergence is a notable signal: Google is reporting more clicks but GA4 is recording far fewer sessions.
Hypothesis
The discrepancy between rising GSC clicks (+32%) and falling GA4 sessions (−47%) strongly suggests a GA4 tracking gap rather than a true audience loss. Likely causes: a missing or broken GA4 snippet on recently deployed pages, consent/cookie-banner changes blocking the tag, or a referral exclusion misconfiguration. A real traffic drop would show both metrics declining together.
Suggested action
- Open GA4 Realtime and DebugView alongside GSC's Performance report for the same date range — confirm the click/session ratio is intact on key pages like
/tools/bpm-detector. - Use Tag Assistant or browser DevTools to verify the GA4 measurement ID fires on every page, especially any pages deployed or modified in the last 2–3 weeks.
- Check the GA4 Data Stream → Tag Settings for accidental referral exclusions or filter rules that may have been added recently.
Activity