Google Analytics UTILS

Debug GA4, replace IDs, block analytics and tag scripts, inject GTM/GTAG, and bypass CSP/CORS for measurement testing.

Google Analytics UTILS Developed by the Luratic Team for digital analysts, Google Analytics UTILS brings together practical tools for testing and debugging GA4, Google Tag Manager and the Google tag (gtag.js), with a distinctive interface designed by Jesús Núñez (https://www.jne.design/). Extension highlights: - GA4 Debug Mode. Activate debug mode to inspect events in GA4 DebugView and send them individually instead of in batches. Goodbye batches, hello easier debugging! - Request blocking. Block GA4 collection requests before they leave your browser, or prevent GTM and GTAG scripts from loading. Each option can be enabled independently. - GA4 and GTAG ID replacement. Replace the Measurement ID on matching GA4 requests with a test property's ID or a placeholder such as G-XXXXXX. You can also replace the ID used to load the GTAG library. Useful for validating events in a property you can access without sending those requests to the original property. IMPORTANT: Chrome displays the original request as an internal redirect. That request is redirected before transmission, not sent to the original Analytics property first. Changing the ID redirects requests; use request blocking to stop them from leaving your browser altogether. - GTM and GTAG injection. Load a GTM container or the GTAG library simply by entering its ID, without editing the website's code or pasting a complete snippet. Combine GTM blocking and injection to test your chosen container instead of the website's existing containers. - Domain filtering. Apply the enabled options only on the websites you choose, using a comma-separated list of domains. - Path-based detection. Recognise GA4 requests and GTM/GTAG scripts by their URL paths and identifying parameters, rather than relying only on Google's usual hostnames. This also covers custom domains when the expected paths and parameters are preserved. - CSP Bypass. Remove Content Security Policy response headers while testing script loading and analytics requests, without waiting for changes to the website's configuration. CSP policies defined in HTML meta tags are not removed. - CORS Bypass. Adjust CORS response headers to help test cross-origin requests when missing or incorrect permissions get in the way. This does not fix rejected preflight requests or other server-side errors. Before using injection, enable "Allow User Scripts" in the extension's details in Chrome. CSP and CORS bypasses affect your browser only; they do not fix the website's configuration for other visitors. Enable them only while testing and disable them afterwards. Requires Chrome 145 or later. Found a bug or have an idea to make the extension better? We'd love to hear from you at info@luratic.com. Feito a man dende Galicia con moito amor e sentidiño 💙