Hopkin Tag Inspector

Tracking audits are the kind of work nobody gets around to: someone has to click through the funnel, read a network tab, and know what each vendor's payload is supposed to look like. Hopkin Tag Inspector makes that job something an AI agent can do instead. Built for AI agents The whole recorded session is readable from the page itself as structured JSON — every event, every finding, and the conversions that were expected and never fired. Any agent that can drive a browser can read it directly, with no server, no API key and no export step: const audit = await window.__hopkinTagInspector.getAudit() Point an assistant at your checkout and get back a real audit — which pixel is missing its lead event, which conversion fired three times, which tool is receiving an unhashed email address — without a human ever opening DevTools. The agent can start a recording, drive the flow, and read the result, all from the page. It works just as well by hand. Press record, use your site normally, and every beacon is captured from the first request, correlated back to the JavaScript call that made it, and judged against rules that know how each tool actually behaves. What it covers Seventeen advertising, analytics and customer-data platforms are decoded into real event names and parameters rather than raw request URLs — the pixels and tag managers behind most paid media, the product analytics tools behind most funnels, and the event pipelines that sit between them. Each one is decoded by rules written for that platform's own payload format, so a purchase event is reported as a purchase, with its value, currency and identifiers named. See what did not fire A conversion that never fired looks exactly like a page you forgot to test. Tag Inspector marks the events that should have been there and were not, anchored to the page where they were expected. This is the part no network tab can do for you. Findings, not just traffic It flags the problems that cost money or create risk: an email address sent as readable text, a conversion with no value or currency, the same conversion counted three times on one page, an event fired while consent was denied, a library loaded twice. Both halves of every event Most tools show you either the JavaScript call or the network request. This shows both, paired — so a call that was made but never reached the network is visible as exactly that, rather than as silence. Consent-aware Events are recorded together with the consent state at the moment they fired, so "fired before consent" and "fired while denied" are separate, provable facts. Where your data goes Nowhere. There is no server, no account and no network egress of any kind. Sessions are stored locally in your browser and can be exported by you, on purpose. Personal data in captured payloads is redacted by default; showing it is a deliberate, per-session choice you make in the panel. Surfaces A side panel for watching a session live, a DevTools panel for reading full payloads with findings annotated in place, and the page API above for everything driven by an agent.