What is the viewer_token cookie?
This cookie is associated with csync.loopme.me. It is used to track visitors on multiple websites in order to present relevant advertising based on the visitor's preferences.
Our October 2026 scan found it on 6 sites (0% of the 2,450 we scanned), set before any consent.
- Purpose
- Advertising
- Belongs to
- csync.loopme.me
- Set as
- First-party on 17% of sites, third-party on 83%
- Typical lifetime
- 3 months (vendor says: 31 days) — longer than the vendor documents
Sites that set viewer_token before consent
The highest-ranked 6 of 6 sites.
- amazon.com33 tracking companies
- amazon.co.za32 tracking companies
- idnes.cz42 tracking companies
- rediff.com42 tracking companies
- amazon.sa32 tracking companies
- buffalo.edu5 tracking companies
How to stop it
Declining non-essential cookies in a site's consent banner should stop viewer_token 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 from the Open Cookie Database (Apache 2.0).
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.