Detect Optimizely

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

• Cookies
• Script sources
• JavaScript globals

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

• optimizelyEndUserId
• optimizely.com.*.js
• optimizely
• optimizelyClient.clientVersion:
• optimizelySdk

Establishes

One or more public signals on the scanned page matched a known Optimizely signature (5 rules) at the time of the scan.

Does not establish

A sitewide install of Optimizely, an active vendor contract, exclusive use, or that Optimizely is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Optimizely signals.
2. 2. PluginView reads only public responses (cookies, script sources, javascript globals) and scores them against the Optimizely signature set (5 rules).
3. 3. Review the confidence score and text explanation for Optimizely on the results page.

Can PluginView detect Optimizely without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Optimizely — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Optimizely?

Optimizely is classified under A/B Testing, Personalisation in the PluginView directory.

How many fingerprint rules cover Optimizely?

This reference currently tracks 5 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Optimizely?

Illustrative public indicators for Optimizely include optimizelyEndUserId; optimizely.com.*.js; optimizely. A live scan may match additional proprietary rules beyond these examples.