What is the csm-hit cookie?
Used by Amazon's internal client-side metrics to measure page performance.
Our October 2026 scan found it on 14 sites (1% of the 2,450 we scanned), set before any consent.
- Purpose
- Functional
- Belongs to
- Amazon
- Set as
- First-party (under the site's own domain)
- Typical lifetime
- 12 months
Sites that set csm-hit before consent
The highest-ranked 14 of 14 sites.
- amazon.com33 tracking companies
- amazon.co.uk1 tracking company
- amazon.co.za32 tracking companies
- amazon.fr1 tracking company
- amazon.ca1 tracking company
- primevideo.com1 tracking company
- amazon.es1 tracking company
- amazon.com.br1 tracking company
- amazon.com.mx34 tracking companies
- audible.com25 tracking companies
Show 4 more sites
- amazon.ae32 tracking companies
- amazon.nl1 tracking company
- amazon.com.tr1 tracking company
- amazon.sa32 tracking companies
How to stop it
Declining non-essential cookies in a site's consent banner should stop csm-hit being set on later visits. 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.