Can PluginView detect Klaviyo Onsite without logging in?

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

What category is Klaviyo Onsite?

Klaviyo Onsite is classified under Marketing, CDP, Email & Push in the PluginView directory.

How many fingerprint rules cover Klaviyo Onsite?

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 Klaviyo Onsite?

Illustrative public indicators for Klaviyo Onsite include static.klaviyo.com/onsite; a.klaviyo.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Klaviyo Onsite?

For Klaviyo Onsite, start with: Storefront and landing pages.

Detect Klaviyo Onsite

Marketing, CDP, Email & Push

PluginView detects Klaviyo Onsite, a Marketing, CDP, Email & Push, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Klaviyo Onsite include static.klaviyo.com/onsite, a.klaviyo.com. 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 Klaviyo Onsite

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Klaviyo Onsite

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

static.klaviyo.com/onsite
a.klaviyo.com

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: Storefront and landing pages

How to check a site for Klaviyo Onsite

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

FAQ: detecting Klaviyo Onsite

Can PluginView detect Klaviyo Onsite without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Klaviyo Onsite — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Klaviyo Onsite?: Klaviyo Onsite is classified under Marketing, CDP, Email & Push in the PluginView directory.
How many fingerprint rules cover Klaviyo Onsite?: 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 Klaviyo Onsite?: Illustrative public indicators for Klaviyo Onsite include static.klaviyo.com/onsite; a.klaviyo.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Klaviyo Onsite?: For Klaviyo Onsite, start with: Storefront and landing pages.