The 500-event limit does not apply to web — cleaning up zombie events

Symptom

Reports → Engagement → Events opens onto a list that keeps scrolling. Two hundred rows, and past the top ten every row reads 3, 1, 0 for the last 28 days. test_event_2, btn_click_old, promo_0428. Nobody left at the company knows who created them or why.

And usually someone asks: "shouldn't we clean these up before we hit the 500-event limit?"

First, that limit

Web data streams have no limit on the number of distinctly named events. Google's collection limits documentation says there is no limit for web data streams, and that the figure of 500 is per app user, for app data streams. The same page notes that automatically collected events and enhanced measurement events do not count toward the limits at all.

So if you are measuring a website, 200 events or 400 events will not be cut off by a limit. The "GA4 allows 500 events" line circulating online is an app stream limit that wandered over to web. If you do run an app stream, it is a real limit there.

With that corrected, the real question: why clean up if nothing is going to break?

What zombie events actually cost

The 200-row list is itself the symptom.

• The next person cannot tell what to trust. Twelve events that matter, hidden among 180 dead names, means every new analyst starts with an investigation.
• Every selection is a chance to pick wrong. Each time someone builds an audience, marks a key event or opens an exploration, purchase and purchase_old are both on the menu.
• It is a signal that nothing was designed. If 180 events accumulated and nobody ever removed one, that property usually has no naming convention and no parameter convention either.

Our EV-05 check draws the line like this. An event with fewer than 10 occurrences in 28 days counts as a zombie candidate; if those are more than 20% of all events the item is deducted, and above 40% it scores zero. A property with more than 300 distinct events fails regardless of the ratio — that is our line for what a human can manage, not a GA4 limit.

A zombie is not a dead event

Confuse the two and you will remove the wrong thing.

The second one is far more urgent. Our EV-04 check flags an event as stopped when the last 7 days are all zero while the period before them carried real volume, and warns on events swinging by 60% or more week over week. If you meet one of these while tidying the list, the job is not to delete it but to find out what shipped that day.

The cleanup order

1) Set the period to 28 days and sort by event count. In Reports → Engagement → Events, sorting ascending brings the candidates together at the bottom.

2) Take out what must not be removed. Rare is not the same as unused. Refunds, B2B enquiries, high-value purchases, cancellations — the events that matter most are often the rarest, and they live at the bottom of this list. The closer those are to zero, the more attention they deserve.

3) Sort the rest into three piles.

• Typos and tests (purchse, test_event_2) — remove.
• Finished campaigns (promo_0428) — remove, once you have checked nobody needs to re-read that period's report.
• Old names for a current action (addToCart) — remove, but settle the naming convention first or they will grow back.

4) Stop them at the source. You do not delete an event inside GA4; it disappears when you stop sending it. Remove the tag and trigger in GTM, or take the call out of the site code. Reports show the events collected within the selected period, so once it has stopped, it falls out of the list as the date range moves past it.

5) Write the list down before you remove anything. Event name, last count, and one line on why it went. That note is the only thing that will answer "didn't we used to track that?" six months from now.

In one line

There is no 500 limit on web. The reason to clean up is not the limit, it is the people. When names that fired fewer than ten times in 28 days make up more than a fifth of the list, that list has stopped being a map. But the rare-and-precious events and the ones that stopped yesterday are not cleanup targets — they are things to protect and things to investigate.