Detect Divide

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

• JavaScript globals

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

• divide.cookies
• setDivideCookiePreferences

Establishes

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

Does not establish

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

Can PluginView detect Divide without logging in?

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

What category is Divide?

Divide is classified under Ecommerce in the PluginView directory.

How many fingerprint rules cover Divide?

This reference currently tracks 2 fingerprint rules across javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Divide?

Illustrative public indicators for Divide include divide.cookies; setDivideCookiePreferences. A live scan may match additional proprietary rules beyond these examples.