Can PluginView detect Criteo OneTag without logging in?

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

What category is Criteo OneTag?

Criteo OneTag is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.

How many fingerprint rules cover Criteo OneTag?

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 Criteo OneTag?

Illustrative public indicators for Criteo OneTag include static.criteo.net/js/ld/ld.js; sslwidget.criteo.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Criteo OneTag?

For Criteo OneTag, start with: Storefront; product/cart actions.

Detect Criteo OneTag

Advertising, Attribution & Visitor Identification

PluginView detects Criteo OneTag, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Criteo OneTag include static.criteo.net/js/ld/ld.js, sslwidget.criteo.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 Criteo OneTag

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Criteo OneTag

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

static.criteo.net/js/ld/ld.js
sslwidget.criteo.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; product/cart actions

How to check a site for Criteo OneTag

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

FAQ: detecting Criteo OneTag

Can PluginView detect Criteo OneTag without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Criteo OneTag — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Criteo OneTag?: Criteo OneTag is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Criteo OneTag?: 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 Criteo OneTag?: Illustrative public indicators for Criteo OneTag include static.criteo.net/js/ld/ld.js; sslwidget.criteo.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Criteo OneTag?: For Criteo OneTag, start with: Storefront; product/cart actions.