Detect Trackbee

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

• Script sources

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

• trackbee.min.js

Establishes

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

Does not establish

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

Can PluginView detect Trackbee without logging in?

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

What category is Trackbee?

Trackbee is classified under Analytics in the PluginView directory.

How many fingerprint rules cover Trackbee?

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

Illustrative public indicators for Trackbee include trackbee.min.js. A live scan may match additional proprietary rules beyond these examples.