Google Tag Manager gtm.js request
The script download that loads a Google Tag Manager container or a Google tag. Its URL shows which container or tag ID a site uses.
The request at a glance
- Request
GEThttps://www.googletagmanager.com/gtm.js?id=GTM-XXXXXXhttps://www.googletagmanager.com/gtag/js?id=G-XXXXXXX- Sent by
- Google Tag Manager
- Typically triggered by
- The page loading the GTM or Google tag snippet
What this request is
gtm.js is the Google Tag Manager container script, and gtag/js is the Google tag library. Both are script downloads rather than data hits: they load the code that later sends analytics and advertising requests.
The id parameter identifies what is being loaded: a GTM- container, or a Google tag ID starting with G- (GA4), AW- (Google Ads) or DC- (Floodlight).
What typically triggers it
- Page load, when the container or Google tag snippet in the page runs.
- A container can also be loaded by another container or by a plugin.
Important parameters
| Parameter | What it means | Source |
|---|---|---|
id | Container ID (GTM-) or Google tag ID (G-, AW-, DC-). | Vendor-documented |
l | A custom data layer name, when the site does not use the default dataLayer. | Commonly observed, not documented by the vendor |
gtm_auth, gtm_preview | Environment parameters, present when a GTM environment or preview is being loaded. | Commonly observed, not documented by the vendor |
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
googletagmanager.cominto the filter box. - Click a matching request and open Payload to read its parameters.
- A site can load more than one container or Google tag. Each distinct id is a separate configuration to check.
Sources
- Google for Developers: The data layer
- Google for Developers: Install the Google tag
- Campaign Manager 360 Help: Floodlight tags
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.