Works with your stack

Cookie consent for tawk.to live chat

the chat waits for a yes

The tawk.to plugin adds an inline script that loads the tawk.to chat on every page. It has no consent setting. Cookie Rocks holds the tawk.to script until consent, and the chat loads after Accept all.

By tawk.to · tawk.to · WordPress.org

Is this your product? Tell us if anything here is out of date. Write to us

Start your free trial

Get the free audit

tawk.to Live Chat

WordPress plugin

Tested

Tested version: 0.9.3
How: Tested automatically around each Cookie Rocks version
Last test: 7 November 2026
Latest version: 0.9.3 tested
Active installs: 100,000+

See it on WordPress.org

What tawk.to Live Chat adds to your visitors’ browser

Trackers it loads

tawk.to →Preferencestawk_uuid_* 6 months TawkConnectionTime Until the browser closes twk_idm_key Until the browser closes twk_uuid_* 6 months6 browser storage keys

What matters for consent with tawk.to Live Chat

Held until consent

Cookie Rocks holds the tawk.to chat script until the visitor agrees. After Accept all, the chat loads.

Who the visitor is

Visitor recognition is on by default: a logged-in user’s name and e-mail are written in the page and sent to tawk.to when the chat loads.

A session from the server

With visitor recognition and a Secure Mode key saved, the plugin opens a PHP session on every request, which sets a cookie no banner can hold. Turn one of them off if you do not need it.

Cookie Rocks with tawk.to Live Chat

Holds the scripts it adds to your pages, such as tags, pixels or a chat, until the visitor consents. In advanced Consent Mode, Google’s tags load with consent denied instead.

All the features

What our tests found on tawk.to Live Chat

Good to know · Crisp, Tidio, tawk.toCrisp, Tidio and tawk.to chat scripts are held until consent
The chat scripts added by the Crisp, Tidio (asynchronous loading) and tawk.to plugins (client.crisp.chat/l.js, code.tidio.co, embed.tawk.to) are held by Cookie Rocks until consent and load after Accept all.
Seen in our tests, 17 October 2026, Crisp, Tidio, tawk.to 0.48, 8.0.1, 0.9.3.
Set before the choice · tawk.to Live Chattawk.to loads its chat on every page and passes logged-in users' e-mail
With visitor recognition on (default), a logged-in user's name and e-mail address go to tawk.to when the chat loads. No consent setting, no filter and no WP Consent API support.
Read in its code, 16 October 2026, tawk.to Live Chat 0.9.3.
Full detail
The tawk.to plugin prints an inline footer script (id tawk-script) that creates the async embed.tawk.to script itself, on every page by default. With visitor recognition on, which is the default, Tawk_API.visitor carries a logged-in user's name and e-mail address in the HTML, sent to tawk.to when the widget loads. The plugin has no consent setting, no filter of its own and no WP Consent API support.
Depends on a setting · tawk.to Live Chattawk.to Secure Mode sets a PHP session cookie from the server
setting “Secure Mode JavaScript API key” · by default: empty
With visitor recognition on (default) and a Secure Mode key saved, the plugin starts a PHP session on every request. No consent banner can hold this cookie.
Read in its code, 16 October 2026, tawk.to Live Chat 0.9.3.
Full detail
When visitor recognition is on (the default) and a JavaScript API key is saved for Secure Mode, the tawk.to plugin calls session_start() on init for every request, closing it at once for visitors who are not logged in. This sets a PHP session cookie from the server, which no consent banner can hold.

How we test it

Around each version, with its latest release

Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.

tawk.to Live Chat 0.9.3, tested on 7 November 2026.
The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
Its own tags, set with a test ID, do not load before the choice and load after “Accept all”.
Settings of the test: tawk.to property and widget IDs (test values), default visibility.
Last run: tawk.to Live Chat 0.9.3 on 7 November 2026, with WordPress 7.1.3.

Chat and messaging

Other plugins of the same kind.

WhatsAppLinks wait for the click, hosted widgets wait for consent.CrispCrisp’s chat held until consent.tested 0.49 TidioTidio held until consent, started without a reload.tested 8.0.1 Live chatCrisp, tawk.to and Tidio held until consent.Click to ChatA WhatsApp button that contacts no one before the click.tested 4.46 JoinchatA WhatsApp button, plus click events for Google and Meta.tested 6.4.2 WP WhatsAppA WhatsApp button with a cookie only after its own box is ticked.tested 3.8.2 ChatyChat buttons that stay, and remember their state in the browser.tested 3.6.5

Every plugin and theme we test →

Questions

What happens after the 30-day trial?

The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.

For tawk.to users

Chat after a yes, contact for everyone.

chat after a yes

Every feature of the complete plugin for 30 days, no card. tawk.to keeps working as it does today.

During the trial: everything, including the full settings and the scans
After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
What waits for a key: most settings, updates and support

How the trial works, in detail

Get your trial key

Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.