GA4 Pipeline -Episode 3: Collect | What GA4 Does With Events
- Arif Khan
- Jan 6
- 2 min read
--author Arif Khan | founder zinzu.io
In the previous episode, we looked at how events are sent.
Now we move to the next step in the pipeline: Collect
This is where GA4 receives events and processes them before you ever see them.
What “collect” means in GA4
When events reach GA4, they are no longer under your control.
GA4 is responsible for:
Receiving events at scale
Applying server-side processing
Preparing data for reporting and export
At this stage, GA4 is not visualizing data yet. It is processing it.
Events are inputs, not final data
Google Analytics 4 (GA4) doesn’t store or expose data exactly as received.
Events via tags, Measurement Protocol, or uploads are raw inputs to a server-side pipeline that groups, models, and filters them into the insights you see in reports or BigQuery.
What GA4 Receives
Event name: e.g., page_view.
Parameters: Up to 25 key-values (e.g., value=49.99).
Timestamps: Event time and engagement.
Identifiers: User pseudo-ID, anonymized signals.
Queued for processing: real-time in ~30s, full derivations in 24 hours
Examples of processing during collection
Before data is exposed in reports or BigQuery, GA4 applies processing such as (these are only few of large processing):
Session grouping: Events are grouped into visits based on timing and signals.
Attribution processing: Traffic source and campaign information is evaluated.
Privacy enforcement: Consent and privacy rules affect what data is processed and exposed.
Thresholding and aggregation rules: Limits may be applied to protect privacy and support scale.
These steps happen after events are sent, but before you see the data.
Why GA4 feels like a black box
You do not see:
The raw processing steps.
All internal rules
Every decision made during collection
This is intentional.
GA4 is designed to balance: Scale, Privacy & Simplicity for most users
Understanding this prevents false assumptions about “missing” or “incorrect” data.
What’s Next?
Once events are collected and processed, the only thing left is interpretation.
This is where most people interact with GA4 through reports, explorations, and conversions.
In the next episode, we’ll look at interpretation, and why GA4 often struggles to explain behavior even when the data is technically correct.
Comments