Detect Perzonalization

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

• Script sources

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

• cdn.perzonalization.com

Establishes

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

Does not establish

A sitewide install of Perzonalization, an active vendor contract, exclusive use, or that Perzonalization 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 Perzonalization signals.
2. 2. PluginView reads only public responses (script sources) and scores them against the Perzonalization signature set (1 rules).
3. 3. Review the confidence score and text explanation for Perzonalization on the results page.

Can PluginView detect Perzonalization without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Perzonalization — typically script sources. It does not bypass authentication or paywalls.

What category is Perzonalization?

Perzonalization is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Perzonalization?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Perzonalization?

Illustrative public indicators for Perzonalization include cdn.perzonalization.com. A live scan may match additional proprietary rules beyond these examples.