Detect Loop Returns

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

• JavaScript globals
• DOM selectors

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

• Loop.config.variantParam
• LoopOnstore

Establishes

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

Does not establish

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

Can PluginView detect Loop Returns without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Loop Returns — typically javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is Loop Returns?

Loop Returns is classified under Returns in the PluginView directory.

How many fingerprint rules cover Loop Returns?

This reference currently tracks 3 fingerprint rules across javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Loop Returns?

Illustrative public indicators for Loop Returns include Loop.config.variantParam; LoopOnstore. A live scan may match additional proprietary rules beyond these examples.