Works with your stack
Cookie consent for Crisp live chat
the chat waits for a yes
The Crisp plugin loads Crisp’s chat script on every page, after a small inline script with your site ID. It sets no cookie itself, but has no consent setting either. Cookie Rocks holds the Crisp script until consent, and the chat loads after Accept all.
By Crisp · crisp.chat · WordPress.org
Tested with Crisp 0.49: the chat script waits for Accept, then starts on the same page. Nothing goes to Crisp after a refusal. Cookie Rocks 2.10.0, 6 November 2026
Is this your product? Tell us if anything here is out of date. Write to us
Crisp
WordPress plugin
- Tested version
- 0.49
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 0.49 tested
- Active installs
- 10,000+
What Crisp adds to your visitors’ browser
Trackers it loads
- Crisp →Preferences7 browser storage keys
What matters for consent with Crisp
Held until consent
Cookie Rocks holds the Crisp script until the visitor agrees. After Accept all, the chat loads.
Who the visitor is
For logged-in users, the inline script passes their e-mail and name to Crisp. With WooCommerce, the customer’s phone and addresses too. That data should follow the visitor’s choice, like the chat.
No setting in the plugin
The plugin has no consent option and no filter. The banner does the waiting.
Cookie Rocks with Crisp
- 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.
What our tests found on Crisp
Set before the choice · Cookie RocksCookie Rocks holds Crisp until the visitor accepts, with no reload
The loader waits for Accept, then starts on the same page. Nothing is requested after Refuse.
Seen in our tests, 6 November 2026, Cookie Rocks.
Full detail
Cookie Rocks 2.10.0 holds the Crisp 0.49 loader client.crisp.chat/l.js and its inline script before any choice. After Accept, l.js loads and the Crisp API is ready without a page reload. After Refuse, nothing is requested from Crisp. Tested with a placeholder website ID, so the chat window itself was not opened.
Set before the choice · Crisp - Live Chat and ChatbotThe Crisp plugin loads its chat on every page and shares user details
For logged-in users it sends their e-mail and name to Crisp, and with WooCommerce the customer's phone, name and addresses. It has no consent setting and sets no cookie itself.
What to do: Hold both the inline script and l.js until consent.
Read in its code, 5 November 2026, Crisp - Live Chat and Chatbot 0.49.
Full detail
The Crisp plugin enqueues client.crisp.chat/l.js with the WordPress handle crisp (async, footer, version = the current date) on every page, after an inline script that sets CRISP_WEBSITE_ID. For logged-in users that inline script pushes their email and name to Crisp, and with WooCommerce the customer's phone, name and addresses from the session. The plugin has no consent setting, no filter, no WP Consent API and sets no cookie itself; the handle is crisp.
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.
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.
- Crisp 0.49, 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: Crisp website ID (test value).
- Last run: Crisp 0.49 on 7 November 2026, with WordPress 7.1.3.
Chat and messaging
Other plugins of the same kind.
Questions
What do visitors see before they choose?
No chat. A link to your contact page keeps a way to reach you for everyone.
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 Crisp users
Chat after a yes, contact for everyone.
chat after a yes
Every feature of the complete plugin for 30 days, no card. Crisp 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
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.