GA4 Ultimate Stack
Audit every GA4 event and key event across your properties
List events, key events and event create rules across every web stream of the brands you manage, filter by event name, and see where properties differ.
Why audit events across properties
In a portfolio, the same event rarely looks the same everywhere. One brand marks generate_lead as a key event and another doesn't. One site sends Generate_Lead with a capital letter. A third builds its lead event from a GA4 rule instead of a tag. Each difference is easy to miss when you look at one property at a time, and each one changes what the reports say.
Events Manager lists every event, its key-event status and any event create rules across the web streams of the brands you select, in one table.
A table of generate_lead across five properties: one is not a key event and one uses different capitalisation.
Pick brands and filter by event name
- Open Events Manager and tick the brands to include. Free selects one brand per run; Premium can select several, or all.
- Add one or more event name rules: contains, equals, starts with, ends with or regex. Rules combine with OR, so starts with generate_ or equals purchase returns both.
- Press Load events.
If a brand's property list looks out of date, use Refresh the brand list from GA4.
A form with four brands ticked, two event name rules typed in, and a summary of brands, streams and rules.
Read the event table
Each row is one event on one web data stream, with its property, its key-event status and, where there is one, the event create rule that builds it. Read it with three questions in mind:
- Is it there? An event missing from one brand is either not implemented or named differently.
- Is it a key event? The Key column shows the status on each property.
- Where does it come from? A rule-built event has no tag of its own, which matters when you check parity with GTM.
An events table with counts of properties, streams, events, key events and create rules above it.
Spot what differs between brands
Once the table is loaded, compare the events that should match. Typical findings:
- A key event that is set on most brands but not all.
- The same event under different names or capitalisation.
- An event that exists on the source property but isn't reaching the roll-up.
Treat each one as a question for the account owner before you change anything. A brand may differ on purpose.
A grid of four events against five brands showing where each is a key event, not a key event or missing.
Events GA4 builds from a rule
GA4's Create event rules make a new event from an existing one. For example, purchase_high_value might be built whenever purchase has a value above 500. No GTM tag sends it, yet it can be a key event. Events Manager shows these rules next to the events they produce, so a rule-built key event isn't mistaken for a missing tag.
To create or edit a rule, or change key-event status, see Event rules and key events.
A diagram: purchase sent by GTM passes through a GA4 create rule that builds purchase_high_value, a key event, while the original is still recorded.
Record what you found
Note the brands, the filters and each difference with the question it raises. On Premium, export the table as CSV or email it. On Free, record it in your own notes. Then decide, with the owner, which brands should change.
A five-step record strip followed by a CSV export card and an open-questions card.
ODDVX for Windows
Every property, one screen.
Start free on one GA4 brand per run. Premium adds every brand in one run, batch writes, exports and scheduled checks.