Detect Crikle

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

• JavaScript globals

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

• crikle.contactId
• crikle.openConvertWidget

Establishes

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

Does not establish

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

Can PluginView detect Crikle without logging in?

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

What category is Crikle?

Crikle is classified under Live chat in the PluginView directory.

How many fingerprint rules cover Crikle?

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

What public signals suggest a site uses Crikle?

Illustrative public indicators for Crikle include crikle.contactId; crikle.openConvertWidget. A live scan may match additional proprietary rules beyond these examples.