Analytics Detection: a beginner's guide

Web analytics is the discipline of measuring who visits a website, what they do while they're there, and how they got there. It is one of the oldest forms of marketing measurement on the internet — Urchin (the predecessor of Google Analytics) launched in 1995 — and it has grown into a multi-billion-dollar industry. The major modern players include Google Analytics 4 (the dominant free option, used by an estimated 70%+ of all sites that have any analytics at all), Plausible (privacy-focused, hosted, paid), Matomo (open-source, self-hostable), Mixpanel and Amplitude (event-based, product-focused), Heap (auto-tracking), and Adobe Analytics (enterprise).

You should care because the analytics tool a website uses tells you a surprising amount about the team behind it. A site with Google Analytics 4 is using the default and probably hasn't thought hard about analytics. A site with Plausible has made a deliberate privacy-conscious choice. A site with Mixpanel or Amplitude is doing serious product analytics, which usually means an engineering and product team that takes data seriously. A site with no analytics at all is either philosophically opposed or hasn't bothered to set anything up. None of these are right or wrong, but they are signals.

The five things every analytics detection check looks at:

• Script sources. Analytics tools load JavaScript from distinctive origins: `googletagmanager.com`, `plausible.io`, `mixpanel.com`, `amplitude.com`.

• JavaScript globals. `window.dataLayer` (Google Tag Manager), `window.ga` (Google Analytics Universal), `window.gtag` (GA4), `window.mixpanel`, `window.amplitude`.

• Cookie patterns. GA sets `_ga`, `_gid`, `_gat_`; Mixpanel sets `mp__mixpanel`; Amplitude sets `amplitude_*`.

• Network requests. Outbound calls to known analytics endpoints during page load are unmistakable.

• Privacy banners and consent flows. A GDPR-style consent banner often hints at the analytics stack underneath.

Three questions an analytics detection check answers:

• Which analytics tool is this website actually using right now?

• For a sales pitch, does the choice tell me whether the team takes data seriously?

• For a competitive teardown, can I infer what metrics the company is probably watching?

The cost of guessing the analytics stack is misreading the data culture of the team. The fix is one detection pass and a list of known analytics fingerprints. The most useful public reference is the BuiltWith analytics overview and the W3Techs analytics market share, both of which publish regular surveys of which tools are most widely used.

In one sentence: Find tracking and analytics tools

Discovers analytics and tracking tools used on a website including Google Analytics, Mixpanel, Hotjar, Facebook Pixel, and many more marketing technologies.

Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.

Here's what's actually happening behind the scenes when you call this endpoint:

Scans HTML (HyperText Markup Language) source and network patterns for analytics scripts, tracking pixels, and marketing tags. Identifies tool IDs where possible (GA tracking ID, Facebook Pixel ID, etc.).

If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.

Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the Analytics Detection tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.

Understanding analytics implementations helps with competitive analysis, privacy compliance assessment, and identifying optimization opportunities in marketing technology stacks.

Picture this in real life. Imagine a marketing operations. Here's the situation they're walking into: Audit analytics implementations to ensure all tracking is properly deployed and no duplicates exist. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the Analytics Detection tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.

Three questions this tool answers in plain English. If any of these have ever crossed your mind, the Analytics Detection tool is built for you:

• What is this website actually built with, layer by layer?

• Who hosts it, who runs analytics on it, who delivers the assets?

• Is the company on a stack that fits my product, my pitch, or my integration?

You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.

Who gets the most out of this. Sales teams qualifying leads, marketers researching competitors, partnership managers scoping integrations, and security teams looking for known-vulnerable software in the wild. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.

What happens if you skip this entirely. Skip it and you're guessing at how a website is built — which kills sales calls, integration scoping, and competitive research. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.

If you're still on the fence about whether the Analytics Detection tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a marketing operations, a privacy officer, and a growth manager — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.

Story 1: MarTech Audit

Imagine you're a marketing operations. Audit analytics implementations to ensure all tracking is properly deployed and no duplicates exist.

Why it matters: Ensure data quality by identifying tracking gaps or duplicates.

Story 2: Privacy Compliance

Imagine you're a privacy officer. Identify all tracking technologies for privacy policy documentation and consent management.

Why it matters: Maintain GDPR/CCPA compliance with complete tracking inventory.

Story 3: Competitive Intelligence

Imagine you're a growth manager. Analyze competitor analytics stacks to understand their measurement approach.

Why it matters: Identify analytics tools to consider for your own stack.

Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the Analytics Detection tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:

• During sales prospecting, to qualify a lead by what they are running.

• During competitive research, to understand what a rival is built with.

• When scoping an integration or partnership.

• When you suspect a target is using a known-vulnerable version of something.

If you can see yourself in even one of those bullets, the Analytics Detection tool will pay for itself the first time you use it.

Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the Analytics Detection tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.

If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:

"Use the Analytics Detection tool to check example.com and explain anything that looks wrong in plain language."

The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.

If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.

There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.

When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.

These tools pair naturally with Analytics Detection. If you're already running this check, the related ones often answer the next question that comes up:

• Technology Detection — Detect frameworks, CMS, and libraries

• Meta Tags — Extract SEO and social meta tags

• Framework Detection — Detect frontend/backend frameworks

If you're using an AI assistant through MCP (Model Context Protocol), you can ask it to run several of these in one go: "Check Analytics Detection and the related tools for example.com and tell me what looks off."

If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.

GDPR (General Data Protection Regulation) — Europe's privacy law. Requires websites to be transparent about what personal data they collect and how they use it.

CCPA (California Consumer Privacy Act) — California's privacy law. Gives California residents the right to know what personal data a company has collected about them.

HTML (HyperText Markup Language) — The basic language web pages are written in. The tags you see in the source code (<h1>, <p>, <a>) are HTML.