Tag Lens 360 - Tag Debugger & Inspector

Debug & validate marketing tags, pixels, cookies & data layers — plus record & replay tag journeys to test your funnel.

TagLens – Tag Debugger & Inspector Tag Lens 360 helps analysts, tag managers, developers, and QA teams verify that marketing tags, analytics pixels, cookies, and data layers are working correctly on their websites. Use it to see which tracking requests are firing on a page, read the exact values being sent, validate your implementation against your own rules, and inspect cookies and data layers without opening the browser console. Single purpose Debugging and validating web analytics and marketing tag implementations on the pages you visit. Tag capture Tag Lens 360 displays every tag request that fires on the current page, including the full request URL, decoded query and POST parameters, HTTP status, event type, and account identifiers. Any tag can be expanded to see all captured variables, and the details can be copied as JSON for sharing with your team. Data layer inspection Read values directly from the data layer objects on the page, so you don't need to open the browser console. Common structures are supported out of the box - including dataLayer (GTM), digitalData (W3C / CEDDL), adobeDataLayer, utag_data (Tealium), analytics (Segment-style), and Adobe AppMeasurement (s) - and you can register your own custom object names. Values are shown in a readable key-and-value format. Validation Create your own rule sets to check whether specific variables meet expected values. Rules support equals, contains, starts with, regex match, and existence checks. Results display clearly as pass or fail alongside the actual captured values, which is useful during QA and ongoing audits. Cookie inspection View every cookie available on the current page - name, value, domain, expiry, SameSite, Secure, and HttpOnly flags. Export the full list as CSV. Request filtering for testing Optionally filter specific URL patterns while you debug. This feature is intended for QA scenarios — for example, testing what a page looks like when a particular tag doesn't fire. Filtering is off by default, rules are user-defined, and everything can be toggled on or off at any time. It uses Chrome's built-in declarativeNetRequest. Session tracking Turn on "Preserve Log" to keep captured tags as you navigate between pages. Each page is separated by URL, timestamp, and tag count, and you can remove tags from a single page without clearing the rest of your session. Export Download all captured tags as a CSV, export details from a single tag, or export the cookie list as a CSV. Privacy Tag Lens 360 runs entirely in your browser. It does not use accounts, does not contact external servers, and does not send any data from the pages you visit to anyone. Captured tags, validation rules, and settings are kept in Chrome's local extension storage on your own machine. Permissions used Each permission this extension requests is used only for the feature described. * webRequest - capture outgoing tag requests on the active tab * declarativeNetRequest / declarativeNetRequestFeedback - apply user-defined request-filtering rules and report hits * storage - save your validation rules, filtering rules, and UI preferences locally * cookies - read, add, and edit cookies for the active tab * activeTab - inject the data-layer reader when the extension is open * tabs - detect page navigation for session tracking * host_permissions: <all_urls> - the extension must be able to read tag requests on whichever site the user is debugging