Can PluginView detect Plausible Analytics without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Plausible Analytics — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Plausible Analytics?

Plausible Analytics is classified under Analytics, Product Intelligence & Monitoring in the PluginView directory.

How many fingerprint rules cover Plausible Analytics?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Plausible Analytics?

Illustrative public indicators for Plausible Analytics include plausible.io/js; plausible.io/api/event. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Plausible Analytics?

For Plausible Analytics, start with: All pages; observe pageview.

Detect Plausible Analytics

Analytics, Product Intelligence & Monitoring

PluginView detects Plausible Analytics, a Analytics, Product Intelligence & Monitoring, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Plausible Analytics include plausible.io/js, plausible.io/api/event. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Plausible Analytics

Loading website list…

Signal classes

PluginView evaluates public page signals in these classes when identifying Plausible Analytics. Individual fingerprint rule bodies are proprietary and are not published.

Vendor endpoints

Example public indicators for Plausible Analytics

Illustrative indicators derived from public catalog metadata for Plausible Analytics. A live scan may match additional proprietary rules beyond these examples.

plausible.io/js
plausible.io/api/event

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: All pages; observe pageview

How to check a site for Plausible Analytics

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Plausible Analytics signals (prefer: All pages; observe pageview).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Plausible Analytics signature set (2 rules).
3. Review the confidence score and text explanation for Plausible Analytics on the results page.

FAQ: detecting Plausible Analytics

Can PluginView detect Plausible Analytics without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Plausible Analytics — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Plausible Analytics?: Plausible Analytics is classified under Analytics, Product Intelligence & Monitoring in the PluginView directory.
How many fingerprint rules cover Plausible Analytics?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Plausible Analytics?: Illustrative public indicators for Plausible Analytics include plausible.io/js; plausible.io/api/event. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Plausible Analytics?: For Plausible Analytics, start with: All pages; observe pageview.