Detect Drift

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

• JavaScript globals

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

• drift
• driftt

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.

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: All public pages; open chat

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Drift signals (prefer: All public pages; open chat).
2. 2. PluginView reads only public responses (javascript globals) and scores them against the Drift signature set (2 rules).
3. 3. Review the confidence score and text explanation for Drift on the results page.

Can PluginView detect Drift without logging in?

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

What category is Drift?

Drift is classified under Live chat, Chat & Customer Support in the PluginView directory.

How many fingerprint rules cover Drift?

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

Illustrative public indicators for Drift include drift; driftt. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Drift?

For Drift, start with: All public pages; open chat.