Detect Revenue Roll

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

• Script sources

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

• .revenueroll.com

Establishes

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

Does not establish

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

Can PluginView detect Revenue Roll without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Revenue Roll — typically script sources. It does not bypass authentication or paywalls.

What category is Revenue Roll?

Revenue Roll is classified under Retargeting in the PluginView directory.

How many fingerprint rules cover Revenue Roll?

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

What public signals suggest a site uses Revenue Roll?

Illustrative public indicators for Revenue Roll include .revenueroll.com. A live scan may match additional proprietary rules beyond these examples.