Detect Webgains

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

• Script sources
• JavaScript globals

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

• analytics.webgains.io
• ITCLKQ

Establishes

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

Does not establish

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

Can PluginView detect Webgains without logging in?

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

What category is Webgains?

Webgains is classified under Affiliate programs in the PluginView directory.

How many fingerprint rules cover Webgains?

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

What public signals suggest a site uses Webgains?

Illustrative public indicators for Webgains include analytics.webgains.io; ITCLKQ. A live scan may match additional proprietary rules beyond these examples.