Detect Fresh Relevance

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

• DOM selectors

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

• link

Establishes

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

Does not establish

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

Can PluginView detect Fresh Relevance without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Fresh Relevance — typically dom selectors. It does not bypass authentication or paywalls.

What category is Fresh Relevance?

Fresh Relevance is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Fresh Relevance?

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

What public signals suggest a site uses Fresh Relevance?

Illustrative public indicators for Fresh Relevance include link. A live scan may match additional proprietary rules beyond these examples.