What is the messagesUtk cookie?
messagesUtk (short for "user token" for the messaging tool) is an HTTP cookie set by the HubSpot platform when a visitor interacts with the live chat or Conversations widget (HubSpot Conversations) embedded on a website.
It's usually set once the visitor opens or uses the chat window, not simply on page load. It is set on the host site's own domain rather than a HubSpot domain.
What data it stores
The cookie stores a unique identifier (token) assigned to the visitor, used to recognize them on return visits and to link chat messages to their HubSpot profile.
The value is an alphanumeric string generated by HubSpot; the exact format is not publicly documented in detail and may vary. Collected data is sent to HubSpot's servers as part of the HubSpot CRM/Marketing Hub ecosystem.
What it is used for
For HubSpot, the cookie enables chat conversation continuity — a visitor can return to the site and resume a conversation without starting over, with messages linked to the same contact profile.
For the site owner, this means a coherent chat experience and the ability to correlate chat interactions with other marketing and sales data in HubSpot, such as visitor tracking and lead attribution.
Does it require consent?
In CookieFix's classification, messagesUtk falls under the marketing category (advertising/tracking), since it helps identify and track the visitor beyond the chat's basic technical function.
- Under GDPR and the ePrivacy Directive (as implemented locally, e.g. Romania's Law 506/2004), this cookie requires the visitor's prior consent before being set.
- Site owners must disclose it explicitly in their cookie policy and group it under the marketing category in the consent banner.
- The HubSpot Conversations script should only load after consent is obtained, not by default on page load.
How to block or delete messagesUtk
A visitor can delete or block this cookie via browser settings (Chrome, Firefox, Safari, Edge — per-site cookie management), or decline the marketing category in the site's consent banner if granular options are offered.
For site owners, the HubSpot chat widget script should be blocked until consent is given. A consent management platform like CookieFix can automatically block the HubSpot Conversations script from loading until the visitor accepts the marketing category, preventing the cookie from being set without consent.
Frequently asked questions
It is not strictly necessary for the site's core technical functioning; since it's used to track the visitor in the context of chat, it requires prior user consent under GDPR/ePrivacy.
It typically lasts around 6 months, after which it expires automatically unless renewed through a new chat interaction.
On the next interaction with the chat widget, HubSpot will generate a new identifier, and the conversation history tied to the old token will no longer be automatically recognized.
You can inspect cookies in your browser's developer tools (Application/Storage panel) after interacting with the HubSpot chat widget, or run a cookie scanner on your site's domain.