Detect Target2Sell

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

• Script sources

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

• static.target2sell.com

Establishes

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

Does not establish

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

Can PluginView detect Target2Sell without logging in?

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

What category is Target2Sell?

Target2Sell is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Target2Sell?

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 Target2Sell?

Illustrative public indicators for Target2Sell include static.target2sell.com. A live scan may match additional proprietary rules beyond these examples.