Skip to content
CookieTosser

What does otto.de track?

otto.de loaded no advertising or analytics trackers before consent.

That's right in line with other .de sites we scanned: the typical one among 60 sites also loaded 0 tracking companies.

Scanned October 2, 2026 from Germany, loading www.otto.de once and clicking nothing. How we scan

Tracking companies
0
Tracking cookies
0
Third-party hosts
3
Cookies in total
8

Consent banner

The page loaded OneTrust, a consent management platform. Everything below was recorded before anyone answered it.

Companies contacted before consent

2 of the 3 companies it contacted before consent were unclassified.

None.

Other third parties (content delivery, consent, functional, unclassified)

  • onetrust.eu

    otto.my.onetrust.eu

    2 requestsUnclassified
  • cdndex.io

    reporting.cdndex.io

    1 requestUnclassified
  • Cloudflare

    cloudflare.com

    1 requestContent delivery

Cookies set before consent

CookiePurposeSet byLasts
cspUnclassifiedwww.otto.deUnder a day
devSpecsUnclassifiedotto.de12 months
KP_UIDzUnclassifiedwww.otto.de1 day
KP_UIDz-ssnUnclassifiedwww.otto.de1 day
visitorIdUnclassifiedotto.de13 months
BrowserIdFunctionalotto.de13 months
JSESSIONIDFunctionalwww.otto.deSession
OptanonConsentFunctionalotto.de13 months

The page also wrote 6 keys to local storage, which works like a cookie but isn't sent with requests.

Understanding this page

  • How to see which cookies and trackers a website loads

    A hands-on walkthrough for checking what a site sets before you've clicked anything, using Chrome and Firefox's built-in tools, plus how CookieTosser automates the same check every month.

  • What counts as valid cookie consent in the EU

    The rules that actually govern cookie banners — the ePrivacy Directive, the GDPR consent standard, the Planet49 ruling, the strictly-necessary exemption, and what "reject" has to offer compared with "accept.

  • Consent management platforms explained

    What a CMP banner is actually doing behind the scenes, how the IAB's TCF standard and Google's Consent Mode v2 fit in, and why a banner being present is no guarantee that nothing loads before you answer it.