Skip to content

Unidentified cookies and storage

Have you seen one of these names? They were written by real websites, in cookies or in the browser’s storage. We do not know yet which tool writes them. If you do, tell us: Cookie Rocks will recognise it, on every site.

  • 632names waiting for a tool
  • 531written before the visitor chose, on most sites where we saw them
  • 307kept with no end date, in local storage or IndexedDB

30 of 632 names

  • hs-cta-interactionsIndexedDB

    No end dateseen on 58 sites, in 15 countrieswritten before the visitor chose on 66% of them

    Our guess: HubSpot (tracking) (found on every site that has this name)

    I know where it comes from

  • clabdfrLocal storage

    No end dateseen on 44 sites, in 9 countrieswritten before the visitor chose on 100% of them

    No guess yet.

    I know where it comes from

  • XSRF-TOKENCookie

    8 daysseen on 39 sites, in 15 countrieswritten before the visitor chose on 90% of them

    No guess yet.

    I know where it comes from

  • _acceptanceStateLocal storage

    No end dateseen on 36 sites, in 10 countrieswritten before the visitor chose on 3% of them

    No guess yet.

    I know where it comes from

  • gdpr_encoding_modesLocal storage

    No end dateseen on 35 sites, in 9 countrieswritten only after a choice

    No guess yet.

    I know where it comes from

  • taboola global:user-idLocal storage

    No end dateseen on 32 sites, in 9 countrieswritten before the visitor chose on 34% of them

    Our guess: Taboola Pixel (found on every site that has this name)

    I know where it comes from

  • _gbcAcceptanceStateLocal storage

    No end dateseen on 26 sites, in 7 countrieswritten only after a choice

    No guess yet.

    I know where it comes from

  • _unifiedIdLocal storage

    No end dateseen on 25 sites, in 8 countrieswritten before the visitor chose on 32% of them

    Our guess: Mediavine (found on every site that has this name)

    I know where it comes from

  • _xsdLocal storage

    No end dateseen on 22 sites, in 11 countrieswritten before the visitor chose on 91% of them

    No guess yet.

    I know where it comes from

  • cfz_google-analytics_v4Cookie

    1 yearseen on 22 sites, in 14 countrieswritten before the visitor chose on 95% of them

    No guess yet.

    I know where it comes from

  • cfzs_google-analytics_v4Cookie

    Until the browser closesseen on 22 sites, in 14 countrieswritten before the visitor chose on 95% of them

    No guess yet.

    I know where it comes from

  • gc_session_idCookie

    1 dayseen on 19 sites, in 2 countrieswritten before the visitor chose on 100% of them

    Our guess: GrowthCode (found on every site that has this name)

    I know where it comes from

  • gcid_firstCookie

    3 monthsseen on 18 sites, in 2 countrieswritten before the visitor chose on 100% of them

    Our guess: GrowthCode (found on every site that has this name)

    I know where it comes from

  • os_jwt_requiredLocal storage

    No end dateseen on 18 sites, in 4 countrieswritten before the visitor chose on 83% of them

    Our guess: OneSignal (found on every site that has this name)

    I know where it comes from

  • cb_session_idCookie

    1 yearseen on 16 sites, in 9 countrieswritten before the visitor chose on 94% of them

    No guess yet.

    I know where it comes from

  • uc_interaction_typeLocal storage

    No end dateseen on 16 sites, in 8 countrieswritten only after a choice

    No guess yet.

    I know where it comes from

  • wf-fluentforms-path-trackerCookie

    Until the browser closesseen on 16 sites, in 5 countrieswritten before the visitor chose on 100% of them

    No guess yet.

    I know where it comes from

  • wpconsent_analytics_decisionSession storage

    Until the tab closesseen on 16 sites, in 9 countrieswritten only after a choice

    No guess yet.

    I know where it comes from

  • country_codeCookie

    1 monthseen on 15 sites, in 10 countrieswritten before the visitor chose on 100% of them

    No guess yet.

    I know where it comes from

  • o2s-chlCookie

    1 dayseen on 15 sites, in 3 countrieswritten before the visitor chose on 93% of them

    No guess yet.

    I know where it comes from

  • slick-server-debug-messagesLocal storage

    No end dateseen on 15 sites, in 3 countrieswritten before the visitor chose on 87% of them

    Our guess: Slickstream (found on every site that has this name)

    I know where it comes from

  • pdocs_drag_hint_seenLocal storage

    No end dateseen on 14 sites, in 5 countrieswritten before the visitor chose on 7% of them

    Our guess: the WordPress plugin "powerful-docs" (common to the sites that have this name)

    I know where it comes from

  • 1p-data-v3Cookie

    1 yearseen on 13 sites, in 1 countrywritten before the visitor chose on 100% of them

    Our guess: Gravito first-party profile (found on every site that has this name)

    I know where it comes from

  • gravitoSyncCookie

    1 dayseen on 13 sites, in 1 countrywritten before the visitor chose on 100% of them

    Our guess: Gravito first-party profile (found on every site that has this name)

    I know where it comes from

  • nadzOptiIndexedDB

    No end dateseen on 13 sites, in 7 countrieswritten before the visitor chose on 100% of them

    Our guess: Notifadz (found on every site that has this name)

    I know where it comes from

  • regionCookie

    1 dayseen on 13 sites, in 9 countrieswritten before the visitor chose on 100% of them

    No guess yet.

    I know where it comes from

  • _dcidCookie

    1 yearseen on 12 sites, in 8 countrieswritten before the visitor chose on 75% of them

    No guess yet.

    I know where it comes from

  • utm_mediumCookie

    2 monthsseen on 12 sites, in 8 countrieswritten before the visitor chose on 75% of them

    No guess yet.

    I know where it comes from

  • utm_sourceCookie

    2 monthsseen on 12 sites, in 8 countrieswritten before the visitor chose on 83% of them

    No guess yet.

    I know where it comes from

  • _ftaCookie

    1 yearseen on 11 sites, in 5 countrieswritten before the visitor chose on 100% of them

    No guess yet.

    I know where it comes from

How your answer helps

  1. You tell us where a name comes from. A plugin, a theme, a service, a line of code: a short sentence is enough.
  2. We check it at the source. We read the tool’s own documents and look at the sites where the name was seen. Nothing is added on a guess.
  3. Every site benefits. Once confirmed, the name joins its tool’s page, and the next version of Cookie Rocks holds it, lists it in the cookie policy, and erases it after a no.

Where these names come from

Each day, Cookie Rocks visits real websites in many countries, as a new visitor who has not clicked anything yet. It notes every cookie and every key the pages write. Most belong to a tool we already know. The others land here, with what we saw: how long they last, on how many sites, and whether they were written before the visitor chose. We never show which sites.

A name you do not see here may already be known: search the known cookies. For the other kinds of storage, see Browser storage; for how long cookies stay, How long cookies last.