What is the smallest GA4/GTM event plan that still drives real content decisions?

Conclusion

Track only what you will change:

• scroll completion (read depth)
• internal navigation clicks (session depth)
• outbound clicks (reference usefulness)

Keep the event set small, and implement with one generic GTM trigger + data attributes so tracking survives UI refactors.

Explanation

Pageviews alone don’t tell you what to change. Events exist to drive decisions.

Before adding an event, answer:

• If this metric moves, what will we do differently?

If you can’t answer, don’t track it yet.

Practical Guide

Step 1: define the decision loop (what you will change)

Examples:

• low 90% scroll rate → improve intro + headings
• low internal nav rate → improve related links / tag placement
• low outbound click rate → tighten references (only high-value links)

Step 2: ship the minimal event set

1. scroll_depth

• thresholds: 25 / 50 / 75 / 90
• read:
  • 90% completion rate (proxy for usefulness)
  • 25% drop-off (intro fails)

2. internal_nav

• clicks on related / tags / popular
• read:
  • internal nav click rate

3. outbound_click

• clicks to primary sources
• read:
  • outbound click rate (is it a useful research guide?)

4. optional: copy_code

• only for developer posts where copy intent matters

Step 3: implement so it won’t break

Approach: data attributes + one generic GTM click trigger.

Example attributes:

• data-gtm="internal_nav"
• data-gtm-location="sidebar_popular"
• data-gtm-label="<slug>"

GTM:

• trigger only when data-gtm exists
• map data-gtm to the GA4 event name

Pitfalls

• too many events to maintain
• tracking “nice metrics” that don’t change decisions
• fragile selectors that break every UI refactor

Checklist

• [ ] Each event has a clear decision tied to it
• [ ] Event set is limited to scroll + internal nav + outbound clicks
• [ ] Scroll thresholds are defined (25/50/75/90)
• [ ] Internal nav locations are defined (related/tags/popular)
• [ ] Outbound links are classified (primary sources)
• [ ] Tracking uses data attributes (not fragile selectors)
• [ ] GTM uses one generic click trigger based on data attributes
• [ ] GA4 event naming is consistent
• [ ] KPI definitions are documented (e.g., scroll_90_rate)
• [ ] A review cadence exists (weekly) to decide what to change

FAQ

Q1. Should I track everything GA4 offers?

No. Track what you can act on. Too many events becomes maintenance noise.

Q2. Is scroll tracking enough to measure quality?

It’s a proxy. Combine it with internal nav and outbound clicks to understand usefulness and intent match.

Q3. How do I keep GTM from breaking during UI changes?

Use data attributes and generic triggers. Avoid brittle CSS selectors.

Internal links

• Parent hub: Indexing: start here
• Related:
  • Google Search Console setup (Next.js + Vercel)
  • Discovered but not indexed checklist
  • Crawled, currently not indexed fixes

References

• Google Analytics Help: https://support.google.com/analytics/

Disclaimer

Adjust to your scale.