Skip to content
GDPR Obligationscalendar_todayUpdated: 17 November 2026schedule6 min read

Which Cookie Is This? The Most Common Cookies Explained

verifiedLast reviewed 17 November 2026 · GDPRWise legal team

Names like _ga, _fbp or __cf_bm say little on their own. This article lists the cookies found most often on business websites, who sets them, what they do and whether they need consent, and what to do with a cookie you cannot identify.

summarizeKey Takeaways
  • check_circleA cookie name usually tells you which tool set it: _ga is Google Analytics, _fbp is the Meta pixel, __cf_bm is Cloudflare.
  • check_circleWhether a cookie needs consent depends on its purpose. Strictly necessary cookies are exempt, analytics and marketing cookies are not.
  • check_circleEvery cookie belongs in your cookie policy with its provider, purpose and retention period, including the strictly necessary ones.
  • check_circleA cookie that no database recognises usually comes from your own website platform, a plugin or custom code. Find out what it does before you classify it.

You open your browser tools or a scan report and see names like _ga, _fbp or __cf_bm. Every cookie on your website was set by a tool you (or your web builder) installed, and the name usually tells you which one. Below you find the cookies that appear most often on business websites, grouped by what they do, and what to do with a name that is not on the list.

Two obligations depend on it.

Consent. Under the ePrivacy rules (Article 5(3) of the ePrivacy Directive, implemented in national law in every EU country) you need prior consent for every cookie that is not strictly necessary for a service the visitor asks for. Whether a cookie is strictly necessary depends on its purpose, so you cannot decide that without knowing what it does. See Cookies and Consent: What Do You Need to Know?.

Transparency. Consent is only valid if the visitor was informed beforehand, and the GDPR requires you to explain every processing of personal data (Article 13 GDPR). In practice that means a cookie policy that lists, for every cookie, the name, provider, purpose and retention period. See What Must Be in Your Cookie Policy?.

How to read the tables

  • A * at the end of a name stands for a variable part, such as an ID.
  • The category is the usual one. It can differ depending on how you use the tool, so check it against your own situation.
  • Retention periods are not listed, because they depend on the version and configuration of each tool. A scan of your own website reads the actual lifetime of every cookie.

Strictly necessary and technical cookies

These cookies make the website work or keep it secure. They need no consent, but they do belong in your cookie policy.

Cookie Set by What it does
PHPSESSID Websites built with PHP Keeps a visitor’s session together, for example a login or a form in several steps
JSESSIONID Websites built with Java Same: session management
ASP.NET_SessionId Websites built with ASP.NET Same: session management
XSRF-TOKEN Many frameworks Protects forms against forged requests (CSRF)
__cf_bm Cloudflare Tells real visitors apart from automated bots
cf_clearance Cloudflare Remembers that the visitor passed a security check
wordpress_logged_in_* WordPress Keeps a user logged in
wordpress_test_cookie WordPress Checks whether the browser accepts cookies
wp_woocommerce_session_* WooCommerce Links the visitor to their shopping cart
woocommerce_cart_hash, woocommerce_items_in_cart WooCommerce Track changes to the shopping cart
__stripe_mid, __stripe_sid Stripe Fraud prevention for online payments
pll_language Polylang (WordPress) Remembers the chosen language
CookieConsent, OptanonConsent, cookieyes-consent Cookie banners (Cookiebot, OneTrust, CookieYes) Store the visitor’s cookie choice
__dpl Lovable (website builder) Appears to link the visitor to one version of the website, so that pages and files stay in sync. The provider does not document this cookie publicly

Analytics cookies

These cookies measure how visitors use your website. They need prior consent.

Cookie Set by What it does
_ga, _ga_* Google Analytics Store a random ID to tell visitors apart
_gid Google Analytics Tells visitors apart within one day
_gat Google Analytics Limits the number of requests sent to Google Analytics
_clck, _clsk Microsoft Clarity Recognise the visitor and the session for recordings and heatmaps
_hjSessionUser_*, _hjSession_* Hotjar Recognise the visitor and the session for recordings and heatmaps
_pk_id*, _pk_ses* Matomo Store a visitor ID and the data of the current visit

Marketing cookies

These cookies follow visitors for advertising: measuring campaigns, building audiences and showing ads again later. They need prior consent.

Cookie Set by What it does
_fbp, _fbc Meta pixel (Facebook, Instagram) Recognise the visitor and the ad they clicked, for ads and conversion measurement
_gcl_au, _gcl_aw Google Ads Measure whether an ad click leads to a conversion
IDE Google (DoubleClick) Shows and measures personalised ads across websites
NID Google Stores preferences and is used for ad personalisation
bcookie, lidc, li_sugr LinkedIn Recognise the browser for the LinkedIn Insight Tag and embedded LinkedIn features
_ttp TikTok pixel Recognises the visitor for ads and conversion measurement
MUID, _uetsid, _uetvid Microsoft Advertising (Bing) Recognise the visitor for ads and remarketing
VISITOR_INFO1_LIVE, YSC Embedded YouTube videos Register video views and preferences, also used for advertising
hubspotutk, __hstc HubSpot Recognise the visitor and link visits to a contact after a form is submitted

No list is complete: there are thousands of cookies, and new ones appear every month. This is how you find out what an unknown cookie does.

  1. Scan your website. A scan shows which cookies are set, by which domain and for how long, and matches each one against a cookie database with provider, purpose and category.
  2. Look at who sets it. A cookie set by another domain (for example .doubleclick.net) belongs to that provider. A cookie set by your own domain comes from your website platform, a plugin or your own code.
  3. Ask the source. If a cookie is still unknown after the scan, it is not in the public cookie databases. That is typical for cookies of newer website builders, smaller plugins and custom code. Ask your web builder or agency, or search the documentation of the platform for the cookie name.
  4. Classify it only once you know its purpose. Do not label a cookie “necessary” because it looks technical. If nobody can tell you what it does, consider removing the tool that sets it.
  5. List it in your cookie policy. An unknown cookie is still a cookie on your website. Record what you found, and complete the missing details yourself.
cookie

Free tool

Cookie Policy Generator

We scan your website like a visitor and detect every cookie with its provider, purpose and retention period. Generate the policy with a free account.

Scan my cookiesarrow_forward
  1. Make an inventory of every cookie your website sets, preferably with a scan instead of from memory.
  2. For each cookie, record the provider, the purpose, the retention period and the category.
  3. Remove tools you no longer use. Every cookie you do not set is one you do not have to explain.
  4. Make sure analytics and marketing cookies are only set after the visitor has consented.
  5. List all cookies in your cookie policy, including the strictly necessary ones.
  6. Repeat after every change to your website: a new plugin, a chat widget, an embedded video. The cookie audit template helps you do that step by step.
auto_awesomeWhich cookies does your website set?

The free GDPRWise scan visits your website like a real visitor and shows every cookie it finds, with provider, purpose, retention period and category. No account needed.

ShareshareLinkedInmailEmail
GW
GDPRWise Editorial

This article was written by the GDPRWise team and reviewed by our privacy experts. We regularly review our content for accuracy and legal correctness.