What is the datagrail_consent_id_s cookie?
A companion to DataGrail's datagrail_consent_id cookie, part of its consent management platform.
Our October 2026 scan found it on 5 sites (0% of the 2,450 we scanned), set before any consent.
- Purpose
- Necessary
- Belongs to
- DataGrail
- Set as
- First-party (under the site's own domain)
- Typical lifetime
- 12 months
Sites that set datagrail_consent_id_s before consent
The highest-ranked 5 of 5 sites.
- zillow.com4 tracking companies
- netgear.com3 tracking companies
- konghq.com6 tracking companies
- forticloud.com0 tracking companies
- trulia.com4 tracking companies
Related cookies
Other cookies from DataGrail.
- datagrail_consent_id7 sites
- datagrail_consent_version_s4 sites
How to stop it
Declining non-essential cookies in a site's consent banner should stop optional cookies, though a necessary cookie like this one may still be set. Blocking third-party cookies in your browser settings stops the third-party kind everywhere, and clearing cookies for a site removes any it already set.
Description written by CookieTosser, for a cookie the Open Cookie Database doesn't cover.
Understanding this page
- How cookie lifetimes work, and why a 13-month _ga matters
What a cookie's "expires" field actually controls, why Google Analytics ships a 2-year default that many sites cut down to 13 months, and how Safari's 7-day cap on script-set cookies changes the picture.
- First-party vs third-party cookies (and why "first-party" still tracks you)
What the distinction actually means technically, why browsers only block one of the two, and how CNAME cloaking, server-side tagging and cookies like _ga let sites keep tracking under their own domain.
- How to block or limit trackers
Browser privacy settings, content blockers, Global Privacy Control and clearing cookies compared honestly — what each one actually stops, what it doesn't, and what it costs you in return.