Detect Acquire Cobrowse

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

• Script sources
• JavaScript globals

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

• .acquire.io/cobrowse/
• acquireCobrowseRTC
• acquireCobrowseSettings
• acquireConfigNodeServer

Establishes

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

Does not establish

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

Can PluginView detect Acquire Cobrowse without logging in?

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

What category is Acquire Cobrowse?

Acquire Cobrowse is classified under Miscellaneous, Livestreaming in the PluginView directory.

How many fingerprint rules cover Acquire Cobrowse?

This reference currently tracks 4 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Acquire Cobrowse?

Illustrative public indicators for Acquire Cobrowse include .acquire.io/cobrowse/; acquireCobrowseRTC; acquireCobrowseSettings. A live scan may match additional proprietary rules beyond these examples.