Last Updated: June 10, 2020
1. Cookies, Anonymous Identifiers, Web Beacons, and Other Internet Tracking Technology
We utilize Cookies, Anonymous Identifiers, Web Beacons, and other Internet tracking technology to collect information from your computer, mobile, or other device.
- Web Beacons and Other Internet Tracking Technology. A “Web Beacon” is an object embedded into a web page or an e-mail that collects various data. A Web Beacon is known by several common terms, such as a web bug, tag, page tag, tracking bug, tracking pixel, pixel tag, web pixel, targeting pixel, re-targeting pixel, and clear gif. Web Beacons are tiny graphics with a unique identifier that may be included on our Site for several purposes, including to deliver or communicate with Cookies, to track and measure the performance of our Site, and to monitor how many visitors view our Site. Unlike Cookies, which are stored on the device, Web Beacons are typically embedded invisibly on web pages or in e-mails. When used within e-mail, for example, a web beacon can track whether a User opens a message, clicks on a link within the e-mail, and similar actions. We also use other, similar Internet tracking technology to monitor a User’s actions coming to our Site, moving through our Site, and after leaving our Site.
- We use performance Cookies that allow us to track usage. This allows us to learn more about how users use the Site so that we make changes and improvements, as necessary.
- We use targeting Cookies that measure the effectiveness of our advertising campaigns and to track sites you’ve visited so that we can measure the effectiveness of our advertising campaigns.
3. Change Settings From Within Your Browser
The instructions for these vary from browser to browser and they may change from time to time as new versions are released. Here are some links to instructions for the most common browsers:
For other browsers, try searching for “managing Cookies in [browser name].”
4. List of Cookies We Use on Our Website
Hubspot essential/necessary cookies (which do not require consent)
- __hs_do_not_track - This cookie can be set to prevent the tracking code from sending any information to HubSpot.
- __hs_initial_opt_in - This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
- hs_ab_test - This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
- <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.
- hs-messages-is-open - This cookie is used to determine and save whether the chat widget is open for future visits.
- 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.
- __hsmem - This cookie is set when visitors log in to a HubSpot-hosted site.
- hs-membership-csrf - This cookie is used to ensure that content membership logins cannot be forged.
- hs_langswitcher_choice - This cookie is used to save the visitor’s selected language choice when viewing pages in multiple languages.
- __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.
- __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.
Hubspot consent banner cookies (non-essential cookies controlled by the consent banner)
- __hstc - The main cookie for tracking visitors.
- hubspotutk - This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
- __hssc - This cookie keeps track of sessions.
- __hssrc - Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
Google Analytics gtag.js and analytics.js - part of Universal Analytics and uses first-party cookies to: Distinguish unique users and Throttle the request rate
- _ga - Used to distinguish users.
- _gid - Used to distinguish users.
- _gat - Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.
- AMP_TOKEN - Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.
- _gac_<property-id> - Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out.
Google Analytics ga.js - uses first-party cookies to:Determine which domain to measure, Distinguish unique users, Throttle the request rate, Remember the number and time of previous visits, Remember traffic source information, Determine the start and end of a session, and Remember the value of visitor-level custom variables
- __utmt - Used to throttle request rate.
- __utmc - Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
- __utmv - Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.
Want to talk?