HubSpot Conversations

Overview

HubSpot Conversations is HubSpot's live chat and chatbot platform that embeds a messaging widget on websites. The widget enables real-time communication between site visitors and sales or support teams, with conversations automatically linked to HubSpot CRM contact records. It combines functional chat capability with visitor identification and behavioral tracking through HubSpot's shared tracking infrastructure.

What This Script Does

The Conversations widget loads as part of the HubSpot tracking code or as a standalone embed:

• Chat widget script — loaded from js.usemessages.com or bundled with the main HubSpot tracking script from js.hs-scripts.com. The widget renders a chat interface (typically a floating button in the corner of the page) that expands into a messaging panel.
• messagesUtk — a dedicated cookie set for Conversations that stores the visitor's chat identity token. This links chat conversations to the visitor's CRM record and persists across sessions. Expires after 13 months.
• Standard HubSpot cookies — when loaded alongside the full HubSpot tracking code, the __hstc, hubspotutk, __hssc, and __hssrc cookies are also set, providing full visitor behavioral tracking alongside the chat functionality.
• Chatbot automation — bot flows can collect visitor information (name, email, company, inquiry type) before routing to a live agent. This data is submitted to HubSpot and creates or updates CRM contact records.
• Visitor identification — if the visitor is a known HubSpot contact (previously identified via form submission or email click-through), the chat widget displays their name and history to the agent, and the conversation is appended to their CRM timeline.

The widget contacts HubSpot messaging endpoints for real-time message delivery and may load additional resources for bot logic and conversation routing. Page context (current URL, referrer) is included with the chat initiation event to give agents context about what the visitor was browsing.

Consent & Compliance

HubSpot Conversations spans functional and analytics categories. The live chat function itself is a feature that visitors actively choose to use, which can be justified under GDPR Article 6(1)(b) when the visitor initiates a conversation. However, the messagesUtk cookie is set on page load before the visitor interacts with the chat, and the widget typically loads alongside the full HubSpot tracking infrastructure.

Under the ePrivacy Directive, the messagesUtk cookie set before any visitor interaction is not strictly necessary for a service the visitor has requested and requires consent. If the chat widget could defer setting this cookie until the visitor actually clicks the chat button, it would have a stronger case for the strictly necessary exemption — but the default HubSpot implementation sets it proactively.

Under CCPA/CPRA, the chat conversation data and visitor identification data constitute personal information. When this data is linked to CRM profiles and used for sales follow-up or marketing nurturing workflows, it must be disclosed in the privacy notice.

Should You Block This Without Consent?

Conditional. The live chat functionality serves a legitimate user-initiated purpose, but the default implementation sets tracking cookies before any interaction occurs. Ideally, configure the chat widget to load only after the visitor grants consent for functional cookies, or implement a lazy-loading approach where the widget initializes only when the visitor clicks a chat prompt. If the chat widget is loaded alongside the full HubSpot tracking code, the entire script must be gated on analytics/marketing consent.