|Universal Analytics (Google)
|Cookie used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in an anonymous form, including the number of visitors to the website and blog, where visitors have come to the website from and the pages they visited. Read Google’s data practices
||Cookie used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in an anonymous form, including the number of visitors to the website and blog, where visitors have come to the website from and the pages they visited.
|Cookie used by Google DoubleClick to register and report the Website user’s actions after viewing or clicking on an advertisement with the purpose of measuring its efficacy and presenting the user with targeted advertising. Read Doubleclick cookies
|Google Tag Manager
||Tag Manager is a tag management system that allows you to quickly and easily update tags on your website or mobile app from a web interface.
|Google Analytics Control
||Cookie used to remember a user’s preference about the permission for Google Analytics collecting information.
|HubSpot Opt Out
|HubSpot Do Not Track
||This cookie can be set to prevent the tracking code from sending any information to HubSpot. Setting this cookie is different from opting out of cookies, as it still allows anonymized information to be sent to HubSpot.
|HubSpot A/B Test
||This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
|HubSpot 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.
|HubSpot Messages Open
||This cookie is used to determine and save whether the chat widget is open for future visits. It resets to re-close the widget after 30 minutes of inactivity.
|HubSpot Welcome Message
||This cookie is used to prevent the welcome message from appearing again for one day after it is dismissed.
||This cookie is set when visitors log in to a HubSpot-hosted site.
|HubSpot Tracking Code
||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).
|HubSpot Visitor Identity
||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.
|HubSpot Session Count
||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.
|HubSpot Restart Browser
||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.
|HubSpot Chat Visitor
||This cookie is used to recognize visitors who chat with you via the messages 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 messages tool will load their conversation history.
||Collects information on user preferences and/or interaction with web-campaign content
||Collects data on visitor behavior from multiple websites, in order to present more relevant advertisement
||Keeps track of the current language on the website so it is served correctly for the user across all the website pages.
|Hubspot First Visit
||This cookie used to keep track of a user’s first visit.
|New Relic (nr-data.net)
||Used by HubSpot for metrics and analytics.
|SessionCam – 1st party session-expiry cookie
||Used to store the recording status through the visitor’s session. This cookie is set on the first load of SessionCam. It stores whether SessionCam is to record the session or not. This cookie also stores data for whether ServiceTick web surveys are configured to launch for given hostname.
|SessionCam – 1st party session-expiry cookie
||Used to identify the individual user session. This cookie provides the details needed to compile a recording showing multiple pages visited during a visitor’s unique visit to a website.
|SessionCam – 3rd party session cookie
||Only used when a visitor goes across multiple domain names belonging to the same client within a single visit
This cookie is always set but only used in the specific situation of SessionCam users who have websites where the content and functionality is distributed across multiple domain names. This cookie enables the SessionCam reporting console to maintain a view of a visitor’s session across multiple domain names.
|SessionCam – 1st party Test cookie
||Deleted after being set. This cookie is set when SessionCam initialises and is only ever used to ensure we can read and write cookies. Once this cookie has been set it is deleted immediately and if the cookie fails to set, SessionCam will not attempt to record.
|SessionCam – 1st party permanent cookie
|SessionCam 1st party permanent cookie
||Used to identify an individual unique visitor. The SessionCam reporting console can re-sort recorded sessions by a unique visitor. This means that multiple visits from the same unique visitor over a selected date/time range can be aggregated.
Set essential cookies to enable certain features and remember your preferences. For example, cookies keep you logged in, allow you to purchase items, and maintain your language and volume settings.
|TechTarget Inbound Converter
||TTGT sets an internal security cookie within the inbound converter system to enforce elements in the loadbalancer’s security policy. This cookie is referred to as the main cookie. The main cookie is inserted into HTTP responses to client requests. The main cookie serves the following functions:
- used to validate domain cookie and qualifying subdomain cookies
- detect session expiration
- validate the integrity of the frame or feature cookie if used
|When you press play Vimeo will drop third party cookies to enable the video to play and to collect analytics data such as how long a viewer has watched the video. These cookies do not track individuals.