Analytics tool choice is a window into company culture. A startup running Amplitude and Segment is instrumenting every user action and making product decisions from behavioral data. A company running only basic Google Analytics 4 either doesn't have a data team or doesn't yet trust data enough to invest in it. A business with Hotjar on top of GA4 is actively trying to understand user behavior qualitatively. The tool itself matters less than what the combination reveals about how the company thinks.
For competitive intelligence, knowing what analytics platform a competitor uses tells you how well they can see their own funnel — and therefore how quickly they can iterate. It also tells you where they might be blind. And for sales and marketing professionals selling analytics-adjacent products, it's essential pre-call research.
The Analytics Stack Layers
Modern analytics isn't a single tool — it's a stack with distinct layers. Understanding the layers helps you interpret what you find:
- Web analytics — traffic, sessions, conversions (GA4, Adobe Analytics, Matomo, Plausible, Fathom)
- Product analytics — user behavior, feature adoption, retention cohorts (Mixpanel, Amplitude, Heap, FullStory, PostHog)
- Customer data platform — event collection and routing (Segment, Rudderstack, mParticle)
- Session recording and heatmaps — qualitative behavioral data (Hotjar, Microsoft Clarity, FullStory, Mouseflow)
- A/B testing — experimentation platforms (Optimizely, VWO, AB Tasty, Statsig, Growthbook)
- Attribution and media mix modeling — marketing performance (Northbeam, Triple Whale, Rockerbox, Wicked Reports)
When you detect what a competitor is running across these layers, you can form hypotheses about how sophisticated their growth operation is, what decisions they can make from data, and where they might have gaps.
How to Detect Analytics Tools on Any Website
The Manual Method: Network Tab
Open Chrome DevTools (F12), go to the Network tab, and filter by "analytics" or look for requests to known analytics domains. You'll see requests to www.google-analytics.com, api.mixpanel.com, api2.amplitude.com, or cdn.segment.com as events fire. This works but requires knowing what to look for and waiting for events to fire — clicking through the site, scrolling, and interacting to trigger event sends.
The Fast Method: SaaS Detective
For routine competitive research, SaaS Detective surfaces analytics tools automatically when you visit any page. Click the extension, and the Analytics category shows you every detectable analytics and tracking tool running on the current page — from GA4 to Segment to Hotjar to Northbeam — organized clearly without requiring you to dig through network requests.
Reading the Signals: What Analytics Stacks Tell You
Google Analytics 4 Only
Standard web analytics without any event-level product instrumentation. This company knows acquisition basics (where traffic comes from, what pages convert) but likely can't answer questions about feature adoption, user retention by cohort, or which behavioral patterns predict conversion. Data maturity: early.
GA4 + Hotjar or Clarity
They care about UX qualitatively. Probably running session recordings and heatmaps to understand friction in conversion flows. Slightly more mature than GA4-only — they're asking "why" questions, not just "how many." Data maturity: developing.
Segment + Amplitude or Mixpanel
Serious product analytics. Events are being tracked and routed through a CDP, then analyzed in a dedicated product analytics tool. This company can do cohort analysis, funnel analysis, and retention analysis. They have a data team or a technically strong product team. Data maturity: advanced.
Segment + Amplitude + Optimizely + Northbeam
Full-stack data operation. They're running A/B tests informed by product analytics and measuring marketing attribution with a sophisticated MMM tool. This company makes very few decisions without data backing. Data maturity: sophisticated.
Analytics tools often load conditionally. A/B testing tools like Optimizely may only load on specific experiment pages. Attribution tools like Northbeam often load on the checkout flow, not the homepage. Use SaaS Detective on the homepage, key product pages, and the pricing or checkout page to catch the full analytics stack, not just what's loaded on the landing page.
Specific Analytics Signatures to Know
Google Analytics 4
Loads from www.googletagmanager.com (if via GTM) or directly from www.google-analytics.com/g/collect. The GA4 measurement ID format is G-XXXXXXXXXX — visible in the GTM dataLayer or the GA4 script tag.
Segment
Loads from cdn.segment.com/analytics.js. When Segment is present, other analytics tools may route through it rather than loading directly — look for Segment first, then infer what downstream tools they're using.
Amplitude
JavaScript SDK loads from cdn.amplitude.com. API calls go to api2.amplitude.com. The presence of Amplitude without Segment suggests they're loading analytics SDKs directly rather than routing through a CDP.
Mixpanel
Loads from cdn.mxpnl.com. API calls to api.mixpanel.com. Very common in B2B SaaS companies. Seeing Mixpanel suggests they care about event tracking and funnels.
Hotjar
Loads from static.hotjar.com and script.hotjar.com. Common across e-commerce and SaaS. Sets a distinctive _hj* cookie pattern.
FullStory
Loads from edge.fullstory.com. More enterprise-oriented than Hotjar. Often seen alongside Amplitude in larger product organizations.
Triple Whale / Northbeam
DTC-specific attribution tools. Triple Whale uses triplewhale.com scripts; Northbeam uses nb.northbeam.io. Seeing either one on a Shopify store confirms they're serious about ad attribution and marketing efficiency.
What Missing Analytics Tells You
The absence of analytics is also a signal. A company with no detectable analytics beyond a consent management platform (which blocks analytics until consent is given) might be running server-side analytics that never touch the browser — common in privacy-forward European companies. A company with literally no analytics is either brand new, technically naive, or running everything through a mobile app you can't inspect from the web.
Neither of these absences is necessarily bad — but both have implications for how you'd approach a conversation with that company about data, measurement, or tools that depend on web instrumentation.
Bottom Line
Detecting what analytics platform a competitor uses requires knowing the script sources, cookie names, and network request patterns of major analytics vendors. For quick lookups, SaaS Detective surfaces analytics tools automatically, organized by category, across 30+ detectable analytics platforms. The real value comes from interpreting what you find: a sophisticated analytics stack signals a data-driven competitor who can iterate quickly; a thin stack signals potential blind spots you can exploit by building measurement infrastructure they don't have.