Detect PersonaClick

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

• Script sources
• JavaScript globals

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

• cdn.personaclick.com/v.js
• personaclick
• personaclick_callback

Establishes

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

Does not establish

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

Can PluginView detect PersonaClick without logging in?

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

What category is PersonaClick?

PersonaClick is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover PersonaClick?

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

What public signals suggest a site uses PersonaClick?

Illustrative public indicators for PersonaClick include cdn.personaclick.com/v.js; personaclick; personaclick_callback. A live scan may match additional proprietary rules beyond these examples.