Skip to main content
Cookie reference · CookieYes

The cookieyes-consent cookie

The CookieYes banner cookie that stores a visitor's consent choices and the consent ID for the site's consent log.

cookieyes-consent at a glance

Cookie name
cookieyes-consent
Vendor
CookieYes
Category
Functional
Party
First-party
Lifetime (observed)
365 daysObserved median across TagPipes scans. The vendor does not document a lifetime, so this is not its configured value.
Set on
.<your-domain>
Value format
Comma-separated key:value pairs starting consentid:<id>
Name match
Exactly cookieyes-consent

What the cookieyes-consent cookie does

The CookieYes banner sets cookieyes-consent to store the visitor's consent choices and a unique consent ID. The consent ID links the browser to the matching entry in the site's CookieYes consent log.

CookieYes documents the name, its role in consent logging and the consentid field. The rest of the value holds action flags and a yes or no value per category. CookieYes doesn't state a fixed lifetime on its documentation pages; 1 year is the commonly reported default, matches the median TagPipes observed, and can be changed in CookieYes settings.

What TagPipes observed

0.58%

of sites scanned set it (239 of 41,162)

365 days

median observed lifetime

TagPipes scanned 41,162 public websites between August 11, 2026 and September 13, 2026, loading up to three pages per site in a real browser as a first-time visitor. cookieyes-consent was present on 239 of them.

It was set as a first-party cookie on 229 sites and as a third-party cookie on 10. A site can count in both. Where it was stored as a persistent cookie, the median lifetime we recorded was 365 days.

Often found alongside

Percentage of sites with cookieyes-consent where the other cookie was also present.

Technologies detected on the same sites

  • Google Fonts on 84% of them (78% of all sites scanned)
  • Google Analytics on 74% of them (55% of all sites scanned)
  • CookieYes on 57% of them (0.39% of all sites scanned)
  • Google Tag Manager on 51% of them (30% of all sites scanned)
  • reCAPTCHA on 32% of them (32% of all sites scanned)

Aggregate figures across all sites scanned. Websites of TagPipes customers are excluded, no individual site is named, and cookie values are never read or stored. Snapshot dated September 13, 2026.

How to check for cookieyes-consent on a website

  1. Open the site in Chrome, then open DevTools (F12, or Cmd+Option+I on a Mac).
  2. Go to the Application tab and expand Cookies in the left panel.
  3. Select each domain listed there and look for cookieyes-consent. The Expires column shows when it will be deleted.
  4. If it is not there, reload the page. Many cookies are only set after a tag has loaded, and some only after a visitor has made a consent choice.

Sources

Purpose and value format checked against the vendor documentation above on . The observed lifetime and the figures under What TagPipes observed are TagPipes scan data from September 13, 2026, not values documented by the vendor. Vendors change their cookies, and sites can configure their own names and lifetimes. Browse all cookies.

Know every cookie your own site sets

TagPipes Pulse identifies the cookies dropped on your site and flags unclassified or miscategorized ones. Shield builds your cookie declaration from a real scan rather than a questionnaire.

See Pulse See Shield

TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.