methodology / Tech Fingerprint / #69
Analytics tools detected
#69 · Recommended · Web Quality · weighted · Tech Fingerprint · weight 0% · impl implemented · method v1.2.0
Web Quality factor
This factor is part of Web Quality — the weighted 0..100 score that sits above Web Standards. Its weight depends on what kind of site is being measured. Web Standards items take priority; this factor only enters the score once Web Standards passes.
- Base weight
- 0.0 applied to every site type unless overridden below
- Why this weight
- Analytics tools detected — pure tech-stack inventory. Whether a site uses GA4, Plausible, or no analytics at all isn't a web-quality signal. Surfaced as descriptive site_facts; not weighted.
What this means for your business
If nothing's measuring which pages people visit, where they drop off, or which ad sent them, you're flying blind. You can't improve what you can't see.
Plain title: Whether your site tracks customer behavior
What we measure
Which analytics tools your site loads. Common ones: Google Analytics 4, Plausible, Fathom, Mixpanel, Amplitude, Heap, PostHog.
How to improve your score
N/A — informational. Audit your loaded analytics for redundancy and remove anything you no longer use.
Implementation
stale · v1 · seeded — no connector publish yet · source: freshcoat-discovery/src/connectors/tech-stack.ts:scoreAnalyticsResult
Detection method
Scans ctx.html for known third-party analytics fingerprints (Google Analytics, Plausible, Fathom, Matomo, etc.). When count == 0, also probes for first-party telemetry signatures (sendBeacon calls, /_vercel/insights endpoints, /api/track-style POSTs, performance.mark). Returns null when neither third-party nor first-party telemetry is detected — many sites use server-side analytics that leaves no homepage signature.
Detection sources
- Third-party analytics script fingerprint match in ctx.html
- First-party telemetry heuristics (sendBeacon, known proprietary endpoints)
Scoring bands · n_a_only ladder
| Score | Condition |
|---|---|
| 100 | ≥1 third-party analytics tool detected |
| 100 | no third-party but first-party telemetry detected (Vercel Analytics-style) |
| n/a | neither detected — site may use server-side analytics or none at all |
Evidence-key dictionary
What every notes string the connector emits means.
Surfaces in the per-domain dossier evidence column.
tools=[<list>]- Recognised third-party analytics tools detected.
first_party_telemetry_detected- No third-party tool but first-party telemetry signature found (sendBeacon, /_vercel/insights, etc.).
no_third_party_match_first_party_may_exist- Neither signal present. Server-side analytics or no analytics — we don't know.
Applicability
Variable tier. Descriptive signal — having analytics is mildly positive (operator measures). Apr 29 fix: was confidently scoring 0 on every site without GA, now correctly nulls when uncertain.
Changelog
- 2026-04-29 · seed Initial seed from MethodologyRegistry bootstrap.
Facts
Implementation notes
Pattern-match script `src` URLs against a known-tool registry.
Scoring
Scoring formulas are versioned with the methodology. The current method (v1.2.0) maps raw measurements to pass, warn, fail. Factor weights determine how much each contributes to the composite — see the methodology index for the full table.
Version history
| Version | Change | Date |
|---|---|---|
| v1.2.0 | Factor introduced. Status: live. Scoring impl: implemented. | 2026-04-25 |