Detect LiveAgent

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

• JavaScript globals

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

• LiveAgent

Establishes

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

Does not establish

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

Can PluginView detect LiveAgent without logging in?

Yes. PluginView only reads publicly accessible responses when checking for LiveAgent — typically javascript globals. It does not bypass authentication or paywalls.

What category is LiveAgent?

LiveAgent is classified under Live chat in the PluginView directory.

How many fingerprint rules cover LiveAgent?

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

What public signals suggest a site uses LiveAgent?

Illustrative public indicators for LiveAgent include LiveAgent. A live scan may match additional proprietary rules beyond these examples.