Cookies in this hub
12
Functional cookies improve the user experience by remembering settings, enabling chat or support widgets, or preserving interface preferences. They sit in the grey zone between strictly necessary and clearly non-essential tracking.
Cookies in this hub
12
Provider families
7
Default consent view
Case-by-case
Functional cookies are not automatically exempt. If the function is genuinely requested by the user, the cookie may fall within the necessity exemption; if it simply improves convenience, prior consent is usually safer.
Assess functional cookies one by one. Look at the user journey, whether the feature was actively requested, and whether a privacy-friendly fallback exists.
Banner copy tip: Explain the feature in plain English, such as remembering language or loading live chat after the visitor asks for support.
Need platform-specific implementation advice? Review the matching hub for Shopify, WordPress, WooCommerce, PrestaShop.
Records the visitor's consent decisions on Google properties. Set on google.com and propagated to embedded YouTube, reCAPTCHA, and Maps.
Stores the user's consent state for Google services (e.g. cookie-banner choices on YouTube, Search). Read by Google embeds on third-party sites.
Stores the visitor's browser window dimensions so Meta can render embeds at the correct size. Set on facebook.com.
Stores the visitor's chat and presence state for Facebook Messenger / Instagram Direct. Session-only.
Stores the user's language preference for Meta-rendered content (Like button, embeds, Messenger).
LinkedIn datacenter-routing cookie. Required for LinkedIn-rendered embeds to function correctly. Limited to load-balancing — case-by-case necessity assessment usually applies.
Stores the visitor's consent decisions for use of non-essential cookies on LinkedIn properties.
Guest token used by X to authorise non-logged-in visitors when loading embedded tweets and timelines. Required for the embed to render — case-by-case necessity assessment when the embed itself is optional.
HubSpot Messages identifier. Used by the HubSpot chat widget to recognise returning visitors and continue prior chat threads.
Anonymous Intercom visitor identifier used to maintain conversation history for non-logged-in users.
Identifies a logged-in Intercom user and grants access to Messenger and conversation history without re-authentication.
Persists logged-in WordPress users' admin interface preferences (e.g., dashboard layout).
Run a CookieSentry scan to see which functional cookies appear on your live pages before consent, and export a report your privacy team can act on.
Run a free scan →