What does tagesspiegel.de track?
Before any consent, tagesspiegel.de loaded 1 tracking company and set 3 advertising or analytics cookies.
That's fewer tracking companies than most sites we scanned: 75% of the 2,450 sites we checked loaded more. Among the 60 other .de sites we scanned, the typical one loaded 0 tracking companies — tagesspiegel.de loaded more.
Scanned October 2, 2026 from Germany, loading www.tagesspiegel.de once and clicking nothing. How we scan
- Tracking companies
- 1
- Tracking cookies
- 3
- Third-party hosts
- 8
- Cookies in total
- 20
Consent banner
The page loaded Sourcepoint, a consent management platform. Everything below was recorded before anyone answered it. 1 tracking company still loaded while it was unanswered.
Companies contacted before consent
3 of the 7 companies it contacted before consent were unclassified.
- Google Analytics1 requestAnalytics
www.googletagmanager.com
Other third parties (content delivery, consent, functional, unclassified)
- urbanjournalism.org59 requestsUnclassified
participaid.urbanjournalism.org
- k5a.io6 requestsUnclassified
cl.k5a.io, streams-cdn.k5a.io
- benelph.de1 requestUnclassified
benelph.de
- Sourcepoint1 requestConsent banner
cdn.privacy-mgmt.com
- Piano1 requestFunctional
cdn.piano.io
- Cloudflare10 requestsContent delivery
cdnjs.cloudflare.com
Cookies set before consent
The longest-lived tracking cookie it set was _pcus, from Piano, lasting about 13 months.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| _pcus | Advertising | tagesspiegel.de | 13 months |
| __pat | Analytics | tagesspiegel.de | 30 days |
| __pvi | Analytics | tagesspiegel.de | 1 day |
| _k5a | Unclassified | tagesspiegel.de | 12 months |
| _sp_v1_data | Unclassified | www.tagesspiegel.de | 30 days |
| _sp_v1_p | Unclassified | www.tagesspiegel.de | 30 days |
| _sp_v1_ss | Unclassified | www.tagesspiegel.de | 30 days |
| traffic_source | Unclassified | tagesspiegel.de | 30 days |
| __adblocker | Functional | www.tagesspiegel.de | Under a day |
| __cf_bm | Functional | tagesspiegel.de | Under a day |
| __cf_bm | Functional | piano.io (third party) | Under a day |
| __cf_bm | Functional | c2.tagesspiegel.de | Under a day |
| __cf_bm | Functional | vx.tagesspiegel.de | Under a day |
| __pnahc | Functional | www.tagesspiegel.de | 3 months |
| __tbc | Functional | tagesspiegel.de | 13 months |
| _pcid | Functional | tagesspiegel.de | 13 months |
| _pctx | Functional | tagesspiegel.de | 13 months |
| _pprv | Functional | tagesspiegel.de | 13 months |
| consentUUID | Functional | tagesspiegel.de | 12 months |
| xbc | Functional | tagesspiegel.de | 13 months |
The page also wrote 4 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.