See what a site sends to Google, request by request.
Inspect Signals is a Chrome extension that lists the Google Analytics 4 and Google Ads requests a website sends, in Chrome's side panel. Each request sits under the page and the frame that sent it, so you can check a tracking setup while you browse the site, without opening DevTools.
Add to Chrome Version 0.2.26, Chrome 120 or later.
What it shows
Built for checking client sites, and for screen recordings where someone needs to follow along. It reads requests; it never blocks or changes them.
-
Requests by page and source
Every GA4 and Google Ads request appears under the page that sent it, with the property or account id, the event, consent state and the GA4 session. A shared request number shows capture order across GA4 and Ads; GA4 also shows the actual
_scounter for each event. -
Filters
Narrow the list by source (the storefront, an app pixel, a custom pixel by name and id, other frames), GA4 measurement id and session, Ads conversion id and label, and the consent state of one purpose. Warnings combines with every filter. Settings lets you show or hide consent, status, warnings and info, timestamps, and request URLs in rows. Preferences are saved locally across panels.
-
Which script sent it
Each request shows what loaded it: a Google Tag Manager container, a gtag.js snippet on the page, or another tag it was configured inside. When a number cannot be tied to one script, it stays unnamed instead of guessed.
-
Order checks for e-commerce
Signals for the same order are grouped in one card with their source and value. A rule flags the group when values or consent disagree, or when a purchase has no transaction id.
-
Shopify web pixels
Requests sent from custom pixel and app pixel sandboxes are attributed to the pixel that sent them; a custom pixel shows the name set in Customer events, so it is easy to find in the Shopify admin. Each request shows Shopify's consent, the cart, checkout and order ids at that moment, and a rule flags a request sent against Shopify consent or a completed checkout with no purchase signal.
-
Click id and session checks
A gclid, wbraid or gbraid that never reaches a later Ads conversion, a GA4 session that restarts after an ad or utm landing, and self-referrals are flagged on the requests involved.
-
Decoded, Params and Raw
Click a row to read the request three ways: decoded into named fields, as a parameter list, or exactly as it was sent.
-
Key event and conversion hints
Micro steps or GTM events marked as GA4 key events, repeated key events in one session, and funnel steps with no matching Ads conversion get explanatory notes. Ads imports of GA4 key events are not visible, so those suggestions can be ignored when the account uses imports.
-
Landing page checks
A captured session without a page_view may have a Landing page of (not set). Checks also highlight possibly repeated page views, missing landing campaign parameters and SPA routes without a captured page view. Info explains each observation and its limits.
-
Flow view
A Sankey of pages in visit order and a timeline with one lane per property or account, showing session segments and the moments consent changed.
-
Export and reopen
Save a tab's recording as a JSON file and open it again later in the flow view, for a report or a second look.
In the panel
Screens from a demo store with made-up ids.
How it works
The extension reads nothing until you grant a site. Access is asked for one site at a time and Chrome keeps the grant for that site.
- Open the site and click the toolbar icon. The side panel opens for that tab.
- Press Grant access and accept Chrome's prompt for that site.
- Press Reload page. Capture starts from that load.
- Optional, once for all sites: press Grant on the second notice to add www.googletagmanager.com and pagead2.googlesyndication.com. This names the GTM container or gtag snippet behind each request and captures Ads requests sent to pagead2.
- Browse as usual. Requests appear as they are sent; Clear empties the tab's requests and Export saves them.
Understand the checks
Info keeps the legend, check conditions and next steps available in the extension. The guide adds examples and troubleshooting for every check, including when BigQuery export could help investigate an observation.
Limits
What the extension cannot see, so you know what a clean panel does and does not prove.
- Server-side GTM and other first-party collection endpoints are not captured.
- It shows what the browser sent, not what Google accepted.
- Checks see only this tab: Ads account settings (primary, secondary, custom goals), GA4 key events imported into Ads and server-side events are not visible.
- Each tab keeps its newest 1,500 requests. Older ones are dropped and counted in the panel header.
- Order checks and warnings see only captured requests. They state what was sent, not why.
- Loaded by reads Google's gtm parameter, whose format is not documented. Without the two optional Google hosts it uses the request alone.
- The recording lives in session storage and is gone when the tab or the browser closes, unless you export it.
Privacy
The extension has no server. Nothing it reads leaves your browser.
- It reads requests only on sites you grant one by one with Grant access.
- Captured requests are deleted when you close the tab, press Clear or close the browser. Google tag script addresses stay until the tab or the browser closes.
- The extension has no analytics, no advertising, no tracking of you and no remote code.
- It does not read page content, form fields, passwords or cookies.