A signature appears
Identify where it comes from.
Review the evidence and its context. A normal script, deferred attribute and noscript fallback do not all execute in the same way.
Marketing Tag Detector · Implementation clues
Find the tags. Then verify the tracking.
See which analytics and advertising signatures appear in a page’s HTML. Get a useful starting point for a tracking review, with a clear distinction between code being present and events actually firing.
Check your page
Marketing Tag Detector
What is visible in the source?
Enter a public page URL. This check reads the returned HTML; it does not run JavaScript or send tracking events.
02 / Review the evidence
Your tag report
Enter a public URL to inspect its marketing tags.
Plain-text report
After this source check, use the provider’s browser debugger or event-testing tools to verify firing and consent behaviour.
Put it to work
Presence is a clue, not a clean bill of health.
A source check answers one part of a bigger question. Use the evidence to decide what to inspect next.
A container appears
Look inside the container next.
Finding Google Tag Manager does not reveal its published tags. The checker does not download or execute container contents.
Nothing is detected
Check the implementation before adding code.
Consent controls, external scripts, first-party proxies or server-side tracking can hide an implementation from this check. Adding another tag could duplicate existing tracking.
Illustrative example
Turn a finding into a useful handoff.
Imagine the report finds a Google Tag Manager container but no direct Meta Pixel signature. Here is what that tells you—and what it leaves open.
What the report supports
A container reference is present.
Record the URL, container reference and evidence context. That is a reproducible observation about the returned HTML.
What remains unconfirmed
Meta may still load through the container.
Its absence in the source is not proof that it is missing. Nor does the container reference confirm a page view or conversion was sent.
The next verification step
Walk through the real journey in a debugger.
Use an authorised preview session to inspect fired tags and triggers. Check consent states, then verify the intended event and parameters at the destination.
A useful handoff separates observed code, unanswered questions and the next test. It avoids “tracking works” based on a script match alone.
Before you move on
Check the journey, not just the homepage.
Choose representative pages.
Include a landing page and the page where the important action happens. A template-specific tag may not appear everywhere.
Verify consent and event behaviour.
Use browser debugging to inspect actual execution and requests. This tool cannot certify consent compliance or detect duplicate events.
Record the outcome.
Save the source report alongside the debugger findings, tested URL and consent state so someone else can reproduce the review.
Your questions
A little more clarity.
Which platforms can it recognise?
Supported signatures include Google Tag Manager, Google tag, GA4, Google Ads, Meta Pixel, LinkedIn Insight, TikTok Pixel, Microsoft Clarity and Hotjar. It is not a complete inventory of every marketing platform.
Does a detected tag mean it works?
No. Detection identifies a supported signature in returned HTML. A tag can be present but blocked, deferred, misconfigured or never executed. Some inactive inline code can still match.
Why is a tag missing from the report?
It may be injected after JavaScript runs, loaded from a container or external script, gated by consent, or implemented server-side. Confirm its actual behaviour before changing the installation.
Make your tracking easier to trust.
Send us the page and the action you need to measure. We can help connect source evidence with a practical review of the enquiry or purchase journey.
Send an enquiry