What is the twk_idm_key cookie?
twk_idm_key is an HTTP cookie set by Tawk.to, a live chat widget provider commonly used on e-commerce sites and support pages. The cookie appears when a visitor interacts with the chat window embedded on the site (in some configurations the widget loads automatically when the page is visited, depending on how the site owner set it up).
It is set by the Tawk.to JavaScript widget, so technically it behaves as a first-party cookie from the site's domain perspective, but it is managed by Tawk.to's infrastructure.
What data it stores
The cookie stores an identifier tied to the visitor's chat session, used by Tawk.to to maintain conversation context (for example, so the visitor doesn't lose the chat history on page reload). The exact value format is not publicly documented by Tawk.to and may vary.
The associated data is sent to Tawk.to's infrastructure to process and display the chat widget.
What it is used for
The main purpose is functional: it allows the chat widget to identify the visitor's current session and maintain conversation continuity while they browse the site or reload the page. For the site owner, this means a smoother chat experience for users and the ability for support agents to respond within the same session without losing context.
Does it require consent?
In CookieFix's classification, twk_idm_key falls under the preferences (functional) category. Since it is not strictly necessary for the site's basic functioning (the site works without chat as well), setting it generally requires the visitor's prior consent, under the EU ePrivacy Directive (as transposed locally, e.g. Romania's Law 506/2004) and GDPR.
- The site owner should list this cookie in the cookie policy.
- The Tawk.to widget should not load, or should not set cookies, before the visitor gives consent for the preferences/functional category.
How to block or delete twk_idm_key
Visitors can delete or block this cookie from their browser settings (Chrome, Firefox, Edge, Safari) via the cookies and site data section, or use private/incognito browsing.
For site owners, the recommended approach is using a CMP such as CookieFix, which automatically blocks the Tawk.to script (and therefore the cookie) until the visitor accepts the relevant category, preventing the chat widget from loading before consent.
Frequently asked questions
It's a session cookie set by the Tawk.to live chat widget, used to maintain the visitor's conversation context on the site.
No. It's classified as a functional/preferences cookie since the site can operate without it, so it requires visitor consent.
It's a session cookie, meaning it typically expires when the visitor closes their browser.
It can be deleted via browser settings or proactively blocked using a CMP that stops the Tawk.to widget until consent is given.