Detect Piggy

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

• Script sources
• JavaScript globals

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

• .piggy.eu/
• PiggyWidget

Establishes

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

Does not establish

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

Can PluginView detect Piggy without logging in?

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

What category is Piggy?

Piggy is classified under Loyalty & rewards in the PluginView directory.

How many fingerprint rules cover Piggy?

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

Illustrative public indicators for Piggy include .piggy.eu/; PiggyWidget. A live scan may match additional proprietary rules beyond these examples.