Does Drift require cookie consent?

Consent is normally required when the tracker stores or accesses non-essential device information, collects analytics identifiers, powers advertising, records sessions, or transmits personal data before a user has opted in.

How does ConsentLens detect Drift?

ConsentLens checks known network domains, JavaScript globals, script source patterns, and inline script snippets, then compares the matched tracker against the page load timing and consent banner state.

How often does Drift fire before consent?

ConsentLens has not yet collected enough public scan data to calculate a reliable pre-consent rate for Drift.

CRMMedium consent risk

Drift GDPR compliance and consent risk

Drift provides conversational marketing and sales. This page combines ConsentLens detection rules with live public scan data so you can see how often Drift appears, whether it fires before consent, and which compliance issues it tends to create.

Scan your website View global tracker stats

ConsentLens has not yet seen enough public scan data for Drift to publish prevalence percentages. The page still shows the exact detection signals and consent risk used by the scanner, and the data sections will populate automatically as public scans detect this tracker.

How ConsentLens detects Drift

Domains

js.driftt.com
event.drift.com

Globals

window.drift
window.driftt

Script patterns

drift.js

ConsentLens combines these signals with request timing. If Drift sends a data request during the first 500ms of page load, it is treated as a pre-consent tracking risk and connected to the relevant scan evidence.

Common compliance issues

No tracker-specific issue titles are available yet. When public scans produce issues naming Drift, this section will show the most frequent findings.

Pre-consent tracking guide Cookie consent requirements How scoring works

Example public scans detecting Drift

Public scan examples will appear here once ConsentLens detects Driftin indexable scan previews.