How to Find Out What Analytics a Website Uses

The analytics and tracking tools a website runs are some of the easiest technologies to detect, because they almost all work by loading a script from a recognisable domain. Whether you are doing competitive research, a privacy review, or just curious how a site measures itself, you can usually list its analytics stack in a minute. This guide shows how to find the analytics, tag managers and marketing pixels a site uses — and where detection's limits lie.

It is a focused companion to how to find out what a website is built with; analytics is one layer of that wider stack.

Why find a site's analytics?

Knowing how a site measures itself is informative in several ways. For competitive research, the analytics and ad pixels reveal how sophisticated a rival's marketing is and which channels they invest in. For privacy reviews, the tracking stack shows what data a site collects and shares — relevant to GDPR and to users who care about being tracked. For sales and partnerships, the tools a company runs are a qualification signal (a site running advanced analytics and several ad pixels is investing in growth). And for learning, seeing real-world setups teaches how analytics and tag management fit together. Because these tools are so visible, all of this is readable from the outside.

Method 1: Watch the Network tab

The most reliable method is to watch the requests a page makes. Open DevTools (F12), go to the Network tab, reload, and look at the domains being called — analytics tools phone home to their own servers, so their requests stand out. Interacting with the page (clicking, scrolling) often triggers additional tracking calls, revealing event-based tools. This live view is comprehensive because it shows what actually fires, not just what is declared in the source, including tags loaded indirectly through a tag manager.

Method 2: Search the page source

A quick source check also works. View the page source (Ctrl/Cmd + U) and search for the tell-tale domains and IDs: googletagmanager.com, google-analytics.com, connect.facebook.net and so on. The measurement and container IDs are especially useful because they identify the specific account format in use. The source view is fast for the major tools, though the Network tab is better for catching everything, since some tags are injected dynamically and may not appear in the raw source.

Identifying Google Analytics and Tag Manager

Google's tools are the most common, and their signatures are clear. Google Analytics 4 (GA4) loads gtag.js from googletagmanager.com and is tied to a measurement ID beginning G-. Older sites may still show the retired Universal Analytics, which used google-analytics.com and a UA- ID. Google Tag Manager (GTM) loads gtm.js with a container ID beginning GTM-, and crucially, GTM is a container that loads other tags — so a site often runs GTM, which in turn fires GA4 and several marketing pixels. Spotting GTM- tells you a tag manager is orchestrating things; you then look at what it loads to see the full stack.

Identifying marketing pixels

Advertising and remarketing pixels are just as visible, each calling its own domain:

Tool	Tell-tale domain / marker
Meta (Facebook) Pixel	connect.facebook.net, fbq( calls
Google Ads / conversion	googleadservices.com, googletagmanager.com
TikTok Pixel	analytics.tiktok.com, ttq object
LinkedIn Insight Tag	snap.licdn.com
Microsoft / Bing UET	bat.bing.com
Pinterest Tag	s.pinimg.com, pintrk(

Seeing several of these together tells you a site runs serious paid-acquisition measurement, which is a strong signal about its marketing maturity.

Beyond Google: other analytics platforms

Plenty of sites use alternatives to Google Analytics, and they are detectable the same way. Privacy-focused analytics like Plausible (plausible.io) and Fathom load lightweight scripts from their own domains. Product analytics like Mixpanel, Amplitude and Heap call their respective domains. Session-replay and heatmap tools like Hotjar (static.hotjar.com) and Microsoft Clarity (clarity.ms) are equally visible. The growing use of privacy-first analytics is itself an interesting signal — a site running Plausible instead of GA is often making a deliberate statement about user privacy.

A worked example

You want to map a competitor's measurement stack. You open the Network tab, reload, and immediately see a request to googletagmanager.com/gtm.js?id=GTM-XXXX — a tag manager is present. As the page loads, you spot gtag/js?id=G-XXXX (GA4 firing through GTM), a call to connect.facebook.net (Meta Pixel), and static.hotjar.com (Hotjar session recording). Interacting with the page triggers a bat.bing.com request (Bing UET). In a minute you have the picture: GA4 for analytics, managed through GTM, with Meta and Bing advertising pixels and Hotjar for behaviour analysis — a mature, multi-channel measurement setup. That tells you far more about how the competitor operates than their homepage copy does.

Consent and privacy considerations

One nuance worth noting: many sites now load a consent management platform (a cookie banner from tools like OneTrust or Cookiebot) that gates analytics and pixels until the user agrees. On such sites, some tracking may not fire — or may fire in a limited mode — until you accept cookies, so what you see before consenting can differ from what loads after. This is itself informative: a site with a robust consent flow is taking privacy compliance seriously, which is relevant to both a privacy review and an assessment of the site's professionalism.

The limits: client-side only

The important caveat is that detection sees client-side tracking — the scripts loaded in the browser. A growing number of sites use server-side tracking, where events are sent from the site's own server to analytics and ad platforms rather than from the visitor's browser. Server-side tracking leaves little or no front-end trace, so it is largely invisible to outside detection. This means a clean-looking front end does not guarantee a site is not tracking; it may simply be doing so server-side. Treat the detected list as a thorough client-side picture, complete for most sites but not a guarantee of everything happening behind the scenes.

What the analytics stack tells you about a business

The measurement stack is a window into how a company operates. A site running only basic, privacy-friendly analytics is often a small team or one that prioritises privacy; a site running GA4 through GTM with several ad pixels, session replay and a CDP is investing seriously in data-driven growth and paid acquisition. The specific pixels reveal the channels a business bets on — Meta and TikTok pixels point to social advertising, a heavy Google Ads footprint to search advertising, a LinkedIn tag to B2B. Session-replay and A/B-testing tools indicate a company optimising conversion rather than just measuring. For competitive research, sales qualification or partnership scoping, the analytics stack is one of the most revealing single things you can read about how mature and growth-focused an operation really is — often more revealing than its marketing copy.

A note on cookies, privacy and the law

Detecting trackers also surfaces a privacy dimension worth understanding. Many of these tools set cookies and send data to third parties, which is exactly what privacy laws like GDPR and the ePrivacy rules regulate — typically requiring consent before non-essential tracking fires. That is why you increasingly see consent banners gating analytics and pixels. From a research angle, this means two things: first, a site's tracking behaviour before and after consent can differ, so check both; and second, the presence (or absence) of a proper consent flow tells you how seriously a site takes compliance. If you run the tools yourself, the lesson is the mirror image: load non-essential tracking only after consent, and be transparent about what you collect, because the same detection methods anyone can run will reveal whether you actually do.

How accurate is analytics detection?

Highly accurate for client-side tools, which announce themselves through their script domains and IDs — GA4, GTM and the major pixels are reliably detected. The accuracy gap is server-side tracking, which is designed to be invisible, and tags gated behind consent, which may not fire until accepted. So "what client-side analytics does this site load?" is a question you can answer confidently; "is this site tracking me at all?" is harder, because some tracking may be happening where you cannot see it.

The workflow

1. Watch the Network tab on load and during interaction for analytics domains.
2. Search the source for IDs like G-, GTM-, UA- and pixel markers.
3. Identify the tag manager (GTM) and see what it loads.
4. List the pixels from their distinctive domains.
5. Remember the limits — client-side only, and consent may gate some tags.

Go deeper

• The full stack: how to find out what a website is built with.
• Estimate reach too: how to check a website's traffic.
• Privacy and security: is this website safe?

Want the analytics, pixels and full stack in one report? Analyse any site with StackOptic — free, no sign-up.