These are essential cookies that do not require consent.
__hs_opt_out
This cookie is used by theopt-in privacy policyto remember not to ask the visitor to accept cookies again.
This cookie is set when you give visitors the choice to opt out of cookies.
It contains the string "yes" or "no".
It expires in 13 months.
__hs_do_not_track
This cookie can be set to prevent the tracking code from sending any information to HubSpot.
It contains the string "yes".
It expires in 13 months.
__hs_initial_opt_in
This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
It contains the string "yes" or "no".
It expires in seven days.
__hs_cookie_cat_pref
This cookie is used to record the categories a visitor consented to.
It contains data on the consented categories.
It expires in 13 months.
hs_ab_test
This cookie is used to consistently serve visitors the same version of anA/B test page they’ve seen before.
It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.
It expires at the end of the session.
<id>_key
When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.
The cookie name is unique for each password-protected page.
It contains an encrypted version of the password so future visits to the page will not require the password again.
It expires in 14 days.
hs-messages-is-open
This cookie is used to determine and save whether the chat widget is open for future visits.
It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.
If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.
It contains a boolean value of True if present.
It expires in 30 minutes.
hs-messages-hide-welcome-message
This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
It contains a boolean value of True or False.
It expires in one day.
__hsmem
This cookie is set when visitors log in to a HubSpot-hosted site.
It contains encrypted data that identifies the membership user when they are currently logged in.
It contains a random string of letters and numbers used to verify that a membership login is authentic.
It expires at the end of the session.
hs_langswitcher_choice
This cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages.
It gets set when an end user selects a language from the language switcher and is used as a language preference to redirect them to sites in their chosen language in the future, if they are available.
It contains a colon delimited string with the ISO639 language code choice on the left and the top level private domain it applies to on the right. An example will be "EN-US:hubspot.com".
It expires in two years.
__cfduid
This cookie is set by HubSpot’s CDN provider, Cloudflare. It helps Cloudflare detect malicious visitors to your website and minimizes blocking legitimate users.
It may be placed on your visitors' devices to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It is necessary for supporting Cloudflare's security features.
It is a session cookie that lasts a maximum of 30 days.
__cfruid
This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. Learn more about Cloudflare cookies. It expires at the end of the session.
Analytics cookies
These are non-essential cookies controlled by the cookie banner. If you're a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.
__hstc
The main cookie for tracking visitors.
It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
It expires in 13 months.
hubspotutk
This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
It contains an opaque GUID to represent the current visitor.
It expires in 13 months.
__hssc
This cookie keeps track of sessions.
This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
It expires in 30 minutes.
__hssrc
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
This is the cookie used forthe chatflows tool. If you're a visitor, this allows you to chat with a representative on the site.
messagesUtk
This cookie is used to recognize visitors who chat with you via thechatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser.
If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history. The cookie is controlled by theConsent to collect chat cookiessettingin your chatflow.
If this setting is disabled, the cookie is controlled by theConsent to processsettingin your chatflow.
HubSpot will not drop themessagesUtk cookiefor visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted.
This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped forinfo.example.comwill not apply to the visitor when they visitwww.example.com, and vice versa.
It contains an opaque GUID to represent the current chat user.
If you have the Facebook pixel code installed on your website, Facebook may set a cookie in a visitor's browser.
If you use the HubSpot ads tool to select and install your Facebook pixel on pages with the HubSpot tracking code, HubSpot will link the placing of that pixel code to the cookie notification banner. If you require opt-in consent via this banner, the Facebook pixel willnotbe able to set any cookies until the visitor has have opted in.
If you manually placed the pixel code on pages (e.g., by editing your site header HTML), HubSpot willnotbe able to control the visitors Facebook is able to set cookies on.
