An event appears in Google Analytics 4, but its extra field is missing from a report. Or the event count looks healthy, although nobody knows what the event actually represents. Both problems become easier to understand when you separate collection, processing and reporting.
GA4 collects events and uses their context to produce dimensions and metrics. The useful question is not only whether a number appears. It is which occurrence was recorded, what information accompanied it, and how the report turns those records into an answer.
Follow the event beyond the website
On a website, measurement code detects an occurrence or receives a signal from the application. A Google Analytics event includes a name and can include parameters. The collection request sends that information to an Analytics destination. GTM can manage this configuration, but GTM is not the reporting database.
Google’s event overview separates receiving an event from fully processing it. Received events can appear in Realtime before their data becomes available through the dimensions and metrics used in other reports.
Keep three observations separate: the website produced a signal, the measurement code sent it, and GA4 received it. A successful GTM tag execution proves neither that the application described the right action nor that the expected report is complete. Each observation answers a different question.
Use event names for occurrences and parameters for context
GA4 has four event categories. Automatically collected events come with the measurement setup. Enhanced measurement can collect common web interactions when enabled. Recommended events have prescribed names and parameters but require implementation. Custom events cover needs that the other categories do not meet.
