Chat widget

Is your Drift chatbot EU AI Act ready?

Article 50 asks that visitors know they are talking to an AI. Scan your site free, and read below exactly where that notice goes in Drift.

Free · No account · Result in ~30s

Drift and Article 50, briefly

Drift is built around playbooks: small scenarios that fire on a specific page, audience or visitor history. There is no central place where the greeting lives, because every playbook has its own opening line. That makes Drift the vendor where a notice most easily ends up incomplete.

What our scans found on Drift sites

We have not yet scanned enough sites where Drift was the first widget we detected to say anything meaningful here. As soon as the sample is large enough it will appear, counts included. We would rather publish nothing than a percentage based on two sites.

How we detect Drift

Our scanner looks for these signals on your public page. Two independent signals are required for a match, so a blog post that merely names the vendor does not count.

Script hosts
js.driftt.comjs.drift.comcustomer.driftt.com
JS globals
window.driftwindow.driftt
DOM selectors
#drift-widget#drift-frame-controller.drift-frame-controller

Where the AI notice goes in Drift

Playbooks, your active playbook, first message. In Drift the greeting almost always lives in a playbook, not in widget settings.

  1. 1

    Open Drift and go to Playbooks.

  2. 2

    Filter on status Live to see what actually runs.

  3. 3

    Open each live playbook and find the first message.

  4. 4

    Put the AI notice at the front of that message.

  5. 5

    Publish per playbook; Drift keeps drafts without making them live.

The sentence you paste

You are chatting with an AI assistant, not a person.

The welcome message only appears after opening. The banner snippet from the Compliance Kit covers the moment before that with a single script tag, and your AI transparency statement covers the question that comes after.

Watch out with Drift: Several playbooks per page means several places. The banner covers them all at once.

Drift documentation: gethelp.drift.com

What goes wrong most often with Drift

Three mistakes we run into on sites that did set the notice. Each one costs points in the scan, and each one takes minutes to fix.

Checking that it works in Drift

Filter your playbooks on status Live and count them. Then walk each of those playbooks on the page and in the situation it is configured for: an exit-intent playbook only shows when you move the mouse towards the address bar, and a returning-visitor playbook only on a second visit. Use a fresh incognito window each time, because Drift stores conversation history per visitor. Read the first bubble of each playbook and check that the notice sits in that same bubble, not in the second.

After that you can scan again. Our scan looks at the same public page a visitor does, so what you see in an incognito window is roughly what we see.

Two dates

  • 2 August 2026: the transparency duty on interaction (Article 50) applies.
  • 2 December 2026: marking AI-generated content becomes relevant.

Frequently asked questions

I have ten playbooks.

Set the notice in every playbook that starts a conversation. Begin with the ones on your busiest pages and use the banner as a safety net for the rest.

Does this apply to Drift Video?

No, a recorded video is not an AI interaction. It does matter if you publish AI-generated video, which comes into play from 2 December 2026.

We only use Drift to book meetings.

A scheduler walking fixed steps is arguable as an AI system. The moment the playbook produces freely worded answers, the argument is over. The notice is cheap either way.

Running another widget as well?

Fix this for Drift in about 15 minutes

The Compliance Kit contains a copy-paste disclosure banner (NL/EN/DE), an AI transparency statement, an AI system inventory and a step-by-step guide per widget.

See the Compliance Kit (€149)

Technical compliance tooling and templates. Not legal advice.