Network request reference · Google Analytics 4

GA4 /g/collect request

The request the Google tag sends to Google Analytics 4 for page views and other events.

The request at a glance

Request: POST or GET https://www.google-analytics.com/g/collect https://region1.google-analytics.com/g/collect
Sent by: Google Analytics 4
Typically triggered by: A page view or any other GA4 event
Related cookies: _ga, _ga_<container-id>

What this request is

/g/collect is where the Google tag (gtag.js), or a GA4 tag in Google Tag Manager, sends event data from the visitor's browser to Google Analytics 4. Each request carries one or more events.

Google documents the hosts and the consent fields on this request, and fully documents the separate server-side Measurement Protocol. It does not publish a reference for the browser request's query parameters, so most of the names below are how practitioners widely read them.

What typically triggers it

A page view when the Google tag or GA4 configuration tag loads.
Automatic and enhanced measurement events such as scroll, outbound click or file download.
Custom events sent with gtag('event') or fired by Google Tag Manager triggers. Several events can be batched into one request.

Important parameters

Parameter	What it means	Source
`gcs`	Consent state for ad_storage and analytics_storage, as set by consent mode.	Vendor-documented
`gcd`	Detailed consent state for each consent type.	Vendor-documented
`v`	Protocol version, 2 for GA4.	Commonly observed, not documented by the vendor
`tid`	Measurement ID (G-XXXXXXX) of the GA4 property.	Commonly observed, not documented by the vendor
`cid`	Client ID, read from the _ga cookie.	Commonly observed, not documented by the vendor
`en`	Event name, for example page_view or purchase.	Commonly observed, not documented by the vendor
`ep.<name>`	An event parameter with a text value.	Commonly observed, not documented by the vendor
`epn.<name>`	An event parameter with a numeric value.	Commonly observed, not documented by the vendor
`sid`	Session ID, the session start time in Unix seconds.	Commonly observed, not documented by the vendor
`sct`	Session count for this client.	Commonly observed, not documented by the vendor
`seg`	Whether the session is engaged, 1 or 0.	Commonly observed, not documented by the vendor
`dl`	Document location: the page URL.	Commonly observed, not documented by the vendor
`dr`	Document referrer.	Commonly observed, not documented by the vendor
`dt`	Document title.	Commonly observed, not documented by the vendor
`_et`	Engagement time in milliseconds.	Commonly observed, not documented by the vendor

When several events share a request, the shared parameters are in the URL and each event's own parameters are on separate lines of the request body.

In TagPipes: TagPipes Pulse reads the gcs consent-state parameter on Google requests like this one when it checks how tags behave against a site's consent banner.

How to find it on a site

Open the site in Chrome, open DevTools (F12, or Cmd+Option+I on a Mac) and go to the Network tab.
Reload the page and type /g/collect into the filter box.
Click a matching request and open Payload to read its parameters. Some may be in the request body rather than the URL.
Check tid to see which GA4 property received the event, and en for the event name.

Sources

The endpoint, the sender and the parameters marked vendor-documented were checked against the sources above on September 27, 2026. Parameters marked commonly observed reflect how the request is widely read by practitioners; the vendor does not document them and can change them without notice. Browse all network requests.

Know when a tag stops firing

TagPipes Auditor checks with real browsers that your marketing pixels fire with the right parameters, and alerts you when tracking breaks. Pulse checks how marketing tags behave against your consent banner.

See Auditor See Pulse

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.