Can PluginView detect Visitor Queue without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Visitor Queue — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Visitor Queue?

Visitor Queue is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.

How many fingerprint rules cover Visitor Queue?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Visitor Queue?

Illustrative public indicators for Visitor Queue include cdn.visitorqueue.com/vq.js; visitorqueue.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Visitor Queue?

For Visitor Queue, start with: B2B pages; observe visit.

Detect Visitor Queue

Advertising, Attribution & Visitor Identification

PluginView detects Visitor Queue, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Visitor Queue include cdn.visitorqueue.com/vq.js, visitorqueue.com. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Visitor Queue

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Visitor Queue

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

cdn.visitorqueue.com/vq.js
visitorqueue.com

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: B2B pages; observe visit

How to check a site for Visitor Queue

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Visitor Queue signals (prefer: B2B pages; observe visit).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Visitor Queue signature set (2 rules).
3. Review the confidence score and text explanation for Visitor Queue on the results page.

FAQ: detecting Visitor Queue

Can PluginView detect Visitor Queue without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Visitor Queue — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Visitor Queue?: Visitor Queue is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Visitor Queue?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Visitor Queue?: Illustrative public indicators for Visitor Queue include cdn.visitorqueue.com/vq.js; visitorqueue.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Visitor Queue?: For Visitor Queue, start with: B2B pages; observe visit.