Update time: December 18, 2025
Google Analytics 4 (GA4) has recently introduced two new event parameters: batch_ordering_id and batch_page_id.
batch_ordering_id
batch_ordering_id is a monotonically increasing number that increments each time GA4 sends a network request（aka: batch） from the same page.
GA4 has a feature called event grouping, which bundles multiple events into a single request (batch) to optimize network performance. The batch_ordering_id parameter shows the order in which these batches are sent from the same page.
For example, when a page is opened, it sends Event 1, Event 2, Event 3, Event 4, and Event 5. GA4 automatically optimizes:
- Event 1 is sent in the first batch, so its value is 1.
- Event 2 is sent in the second batch, so its value is 2.
- Event 3, Event 4, and Event 5 are sent in the third batch, so their values are 3.
Event 3, Event 4, and Event 5 are combined into a single Request (batch) for sending. In fact, when you open this page, only three Requests (batches) are sent to GA4.
This parameter helps GA4 (and downstream systems like BigQuery) preserve the original sequence of event batches when multiple requests are sent from a single page view.
batch_page_id
batch_page_id is a sequential number assigned to a page that increases for each subsequent page within an engagement.
In practice, batch_page_id is derived from the event timestamp and is closely related to the value stored in the GA4 cookie _ga_<container-id>.
Specifically:
-
batch_page_id is a 13-digit timestamp (milliseconds)
-
It corresponds to the current event timestamp
-
It is effectively the millisecond-level version of the timestamp stored in the GA4 cookie _ga_<container-id>
Example: Assume an event is triggered on bbccss.com.
Current timestamp in _ga_<container-id> : 1700107169 (10-digit, in seconds)；batch_page_id : 1700107168937 (13-digit, in milliseconds)
The relationship between them can be expressed as:
current timestamp=batch_page_id/1000
This confirms that batch_page_id is essentially the millisecond-level timestamp associated with the page context of the event.
When should you care about these parameters?
You will most commonly encounter batch_ordering_id and batch_page_id when:
- Analyzing raw GA4 event data in BigQuery
- Debugging event order issues
- Working with batched Measurement Protocol or gtag.js requests
- Reconstructing page-level event sequences
These parameters are automatically generated by GA4 and cannot be configured or modified.
Read More：
