Universal Analytics /collect request
The hit sent by legacy Universal Analytics tags. Universal Analytics no longer processes data, so it usually means an old tag is still on the page.
The request at a glance
- Request
GET or POSThttps://www.google-analytics.com/collect- Sent by
- Google Analytics 4
- Typically triggered by
- Page views and events on pages that still carry Universal Analytics code
What this request is
/collect, without the /g/, is the endpoint used by Universal Analytics: analytics.js and gtag.js configured with a UA- property. Google stopped processing Universal Analytics data in July 2023, or July 2024 for Analytics 360.
Seeing it on a page today means a legacy tag is still loading. It sends requests that no longer appear in any report, and it can set the _gid cookie.
What typically triggers it
- A page view when legacy analytics.js or a UA- gtag configuration loads.
- Events, ecommerce hits or timing hits sent by the legacy code.
Important parameters
| Parameter | What it means | Source |
|---|---|---|
v | Protocol version, 1. | Commonly observed, not documented by the vendor |
tid | Property ID (UA-XXXXX-Y). | Commonly observed, not documented by the vendor |
cid | Client ID. | Commonly observed, not documented by the vendor |
t | Hit type, for example pageview, event or transaction. | Commonly observed, not documented by the vendor |
These parameters were documented in Google's Measurement Protocol v1 reference, which Google has retired; the page now shows only a sunset notice.
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
google-analytics.com/collectinto 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.
- The UA- ID in tid tells you which old property the tag still points at.
Sources
- Google Analytics Help: Universal Analytics is going away
- Google: Cookies used by Google advertising and measurement products
The endpoint, the sender and the parameters marked vendor-documented were checked against the sources above on . 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.
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.