Pixel & Tag Audit
Enter any public page URL. The audit fetches the page via a Cloudflare Worker and reports every analytics or advertising pixel installed. Catches 25 of the most-common vendors plus their IDs.
Measurement Intelligence
Marketing teams usually install 8 to 12 pixels across a site: half of them stop being used but keep firing.
Every running pixel adds page weight, consent complexity, and vendor exposure. This audit shows what is firing on a given page so you can match it against the list of pixels you still use. Anything on the page that isn't on your list is a candidate for removal.
URL to audit
Frequently asked questions
What does this audit?
Any public URL. Fetches the HTML and detects which analytics and advertising pixels are installed, with their IDs.
How many pixels does it detect?
30 of the most-common vendors: GA4, GTM, Meta Pixel, LinkedIn Insight, TikTok, Pinterest, Snapchat, Reddit, X, Bing UET, Hotjar, Clarity, FullStory, Mouseflow, Amplitude, Mixpanel, HubSpot, Intercom, Drift, Optimizely, VWO, Criteo, Yandex, Baidu, Taboola, Outbrain, and more.
Does it detect pixels loaded via GTM?
If the pixel is dropped into the HTML before page load it is detected. GTM-dropped pixels show up because GTM injects them into the DOM.
What about pixels loaded via JavaScript later?
The audit reads static HTML. Pixels injected after initial load won't be detected. Combine with a browser-level audit (Chrome DevTools and Network).
Why audit pixels?
Vendor sprawl. Marketing teams install pixels over years. Half are no longer used but still fire, slowing pages and leaking data.
What should I do with the audit output?
Match against your approved pixel list. Remove anything no longer in use. File each active pixel in your ROPA.
What is a pixel ID?
A tenant identifier that routes data to the right account. GA4 uses G-, Google Ads uses AW-, Meta uses a numeric ID.
Can the tool detect pixels fired server-side?
No. Server-side pixels (sent via Measurement Protocol) have no client-side footprint. Audit server logs for those.
Does it work on authenticated pages?
No. Only public URLs. For gated content, use Chrome DevTools and Network with the page open after login.
Can I audit many pages at once?
One URL per run. For sitewide audits, run on representative pages (home, product, blog, checkout).
How often should I audit pixels?
Quarterly. More often during active campaign changes.
Free · no account
SEORCE for Chrome, Edge and Firefox
Audits the page you are on: headings, meta tags, schema, indexability, and whether AI crawlers can read it. Export the result as a PDF. Free, with no account.
It audits one page at a time and does not track AI answers. About the extension
Traffic from search and AI
See which visits came from search and AI.
SEORCE Web Analytics runs from one script tag, with Google Search Console connected. It shows visits from every AI source, from search and from campaigns, and it is free on every plan.
3,000+ users · Free forever plan, no card needed