Detect Klaviyo Onsite

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.

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

1. 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. 2. PluginView reads only public responses and scores them against proprietary Klaviyo Onsite fingerprints. Rule bodies and identifiers are not published.
3. 3. Review the confidence score and text explanation for Klaviyo Onsite on the results page.

Can PluginView detect Klaviyo Onsite without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Klaviyo Onsite. 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.

Does PluginView publish Klaviyo Onsite fingerprint rules?

No. Detection uses proprietary fingerprint rules that are not published. Scan results explain matches in plain language without disclosing rule bodies or identifiers.

Which pages are best for detecting Klaviyo Onsite?

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