Event names are interfaces
Analytics is only useful when event names are stable and payloads are minimal, typed, and privacy-safe.
The real cost of messy events
If you rename events casually, you’re not “iterating”—you’re breaking an interface.
That breaks:
- dashboards,
- funnels,
- downstream jobs,
- and your ability to compare time ranges.
Durable events
A durable event is:
- stable: the name is a long-lived identifier
- typed: payload shape is explicit
- minimal: no article body, no emails, no unnecessary PII
- non-blocking: the page renders even if analytics fails
The blog-specific set
For blog surfaces, a small set usually covers the product needs:
- article viewed
- category viewed
- tag viewed
- CTA clicked
- outbound link clicked
The goal is clarity: measure the business intent, not the noise.