Can PluginView detect HubSpot Tracking without logging in?

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

What category is HubSpot Tracking?

HubSpot Tracking is classified under Marketing, CDP, Email & Push in the PluginView directory.

How many fingerprint rules cover HubSpot Tracking?

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 HubSpot Tracking?

Illustrative public indicators for HubSpot Tracking include js.hs-scripts.com; js.hs-analytics.net. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting HubSpot Tracking?

For HubSpot Tracking, start with: All pages; observe pageview.

Detect HubSpot Tracking

Marketing, CDP, Email & Push

PluginView detects HubSpot Tracking, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with HubSpot Tracking include js.hs-scripts.com, js.hs-analytics.net. 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 HubSpot Tracking

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for HubSpot Tracking

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

js.hs-scripts.com
js.hs-analytics.net

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 HubSpot Tracking

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

FAQ: detecting HubSpot Tracking

Can PluginView detect HubSpot Tracking without logging in?: Yes. PluginView only reads publicly accessible responses when checking for HubSpot Tracking — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is HubSpot Tracking?: HubSpot Tracking is classified under Marketing, CDP, Email & Push in the PluginView directory.
How many fingerprint rules cover HubSpot Tracking?: 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 HubSpot Tracking?: Illustrative public indicators for HubSpot Tracking include js.hs-scripts.com; js.hs-analytics.net. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting HubSpot Tracking?: For HubSpot Tracking, start with: All pages; observe pageview.