Cookie Table
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.
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 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).
Helps to browse device information. When a user clicks on an ad on Facebook, the link sometimes includes a fbclid query parameter. When the user lands on the target website, if the website has a Facebook pixel that uses first-party cookies, the pixel automatically saves the fbclid query parameter to an _fbc cookie for that website domain.
This cookie is set by Facebook and is used to deliver advertising products, such as retargeting, to users who have visited a website.
This cookie is set by Firebase and is used to remember the user's settings across different webpages.
This cookie is associated with Google Analytics and is used to distinguish unique users by assigning a randomly generated number as a client identifier.
This cookie is associated with Google Analytics and is used to distinguish unique users by assigning a randomly generated number as a client identifier.
This cookie is set by Google and is used by Google AdSense for experimenting with advertisement efficiency across websites using their services.
This cookie is associated with Google Analytics and is used to distinguish users.
This cookie is set by Hotjar and is used to detect the first pageview session of a user.
This cookie is set by Hotjar and indicates whether the user is included in the data sampling defined by the site's pageview limit.
This cookie is set by Hotjar and is used to maintain the user's session state across page requests.
This cookie is set by Hotjar and is used to recognize the user on subsequent visits for analysis purposes.
This cookie is set by Segment.io and is used for collecting anonymous data on user visits and preferences.
This cookie is set by FullStory and is used to recognize a visitor across different sessions.
This cookie is used to keep track of a visitor's identity. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.
This cookie is set by Intercom and is used to maintain the session state of a user's device.
This cookie is set by Intercom and is used to recognize the user on subsequent visits for support and messaging purposes.
This cookie is set by Intercom and is used to maintain the user's session state across page requests.
This cookie is set to identify Customers.
This cookie is set by LinkedIn and is used for tracking the use of embedded services.
This cookie is set by Rudderstack to tore the anonymous ID. By default, it would be the auto-generated unique ID by SDK for each visitor unless overridden via setAnonymousId API. All the subsequent event payloads will contain this data unless cleared from the storage.
This cookie is set by Rudderstack to store the user group ID set via the group API. All the subsequent group event payloads will contain this data unless cleared from the storage.
This cookie is set by Rudderstack to store the user group traits object set via the group API. All the subsequent group event payloads will contain this data unless cleared from the storage.
This cookie is set by Rudderstack to store the initial referrer of the page when a user visits a site for the first time. All the subsequent event payloads will contain this data.
This cookie is set by Rudderstack to store the initial referring domain of the page when a user visits a site for the first time. All the subsequent event payloads will contain this data.
This cookie is set by Rudderstack to store the session-related information including sessionId if session tracking is enabled.
This cookie is set by Rudderstack to store the user traits object set via the identify API. All the subsequent event payloads will contain this data unless cleared from the storage.
This cookie is set by Rudderstack to stores the user ID set via the identify API. All the subsequent event payloads will contain this data unless cleared from the storage.
This cookie is set by a Unbounce and is used to collect information about how visitors interact with our site and landing pages.
This cookie is associated with Google Analytics and is used to distinguish unique users by assigning a randomly generated number as a client identifier.
This cookie is set by LinkedIn and used to determine if Oribi analytics can be carried out on a specific domain