Detect SweetHelp

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

• JavaScript globals

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

• sweetHelpBtnLoad

Establishes

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

Does not establish

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

Can PluginView detect SweetHelp without logging in?

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

What category is SweetHelp?

SweetHelp is classified under Cart abandonment in the PluginView directory.

How many fingerprint rules cover SweetHelp?

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

What public signals suggest a site uses SweetHelp?

Illustrative public indicators for SweetHelp include sweetHelpBtnLoad. A live scan may match additional proprietary rules beyond these examples.