Skip to content

Works with your stack

Cookie consent for Tidio live chat

starts without a reload

← Cookie Rocks for your stack

The Tidio plugin loads its chat after the page has loaded. A script released by a banner after that moment would normally never run. Cookie Rocks holds Tidio until consent and starts the chat after Accept all, without a reload.

By Tidio · tidio.com · WordPress.org

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

Tidio Chat

WordPress plugin

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

What Tidio adds to your visitors’ browser

Trackers it loads

  • Tidio →PreferencesNo cookie of its own3 browser storage keys

What matters for consent with Tidio

Held until consent

Cookie Rocks holds the Tidio chat script until the visitor agrees.

A late start that still works

Tidio waits for the page load event before adding its chat. Cookie Rocks runs that wait at once when the page has already loaded, so the chat starts after Accept all, on the same page.

An early connection

Tidio adds a hint that opens a connection to its server in every page’s head, even while the chat waits. The plugin has no setting to remove it.

Kept in the browser

Once loaded, the chat keeps the visitor ID and its state in local storage.

What our tests found on Tidio

  • 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 · TidioTidio opens a connection to its server before any choice, even when held

    setting “tidio-async-load” · by default: on

    • A preconnect link to code.tidio.co is on every page, with no setting to remove it.
    • Its script waits for the page load event, so when released after consent it never ran.
    • Cookie Rocks 2.5.0 runs it at once; the chat starts after Accept all without a reload.
    • The chat keeps the visitor ID and its state in local storage (tidio_state_*).

    Read in its code, 16 October 2026, Tidio 8.0.1.

    Full detail

    The Tidio plugin adds a preconnect link to code.tidio.co in the head of every page once connected, with no setting or filter to remove it, so the browser opens a connection to Tidio before any choice even when the chat is held. In asynchronous mode (on by default) its inline footer script waits for the page load event to create code.tidio.co/<key>.js, so a script released after consent never ran. Cookie Rocks 2.5.0 runs such a wait at once when the page has loaded, and the chat starts after Accept all without a reload. The chat keeps the visitor ID and its state in local storage keys tidio_state_*.

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.

  • Tidio Chat 8.0.1, 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: Tidio public key (test value), asynchronous loading.
  • Last run: Tidio Chat 8.0.1 on 7 November 2026, with WordPress 7.1.3.

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 Tidio users

Chat after a yes, on the same page.

no reload needed

Every feature of the complete plugin for 30 days, no card. Tidio 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.

One trial per domain. Local and staging sites never use up your key.

We keep your e-mail address to send your key and help you with it, as explained in our privacy policy. No newsletter, nothing else.