What does heart.org track?
Before any consent, heart.org loaded 5 tracking companies and set 4 advertising or analytics cookies.
That's more tracking companies than 78% of the 2,450 sites we scanned.
Scanned October 2, 2026 from Germany, loading www.heart.org once and clicking nothing. How we scan
- Tracking companies
- 5
- Tracking cookies
- 4
- Third-party hosts
- 21
- Cookies in total
- 15
Consent banner
The page loaded OneTrust, a consent management platform. Everything below was recorded before anyone answered it. 5 tracking companies still loaded while it was unanswered.
Companies contacted before consent
4 of the 11 companies it contacted before consent were functional companies.
- The Trade Desk5 requestsAdvertising
js.adsrvr.org, insight.adsrvr.org, match.adsrvr.org
- Google Ads1 requestAdvertising
ad.doubleclick.net
- Google Analytics8 requestsAnalytics
www.googletagmanager.com
- Optimizely4 requestsAnalytics
logx.optimizely.com, cdn.optimizely.com, a25670000279.cdn.optimizely.com
- Cloudflare Web Analytics1 requestAnalytics
static.cloudflareinsights.com
Other third parties (content delivery, consent, functional, unclassified)
- OneTrust12 requestsConsent banner
cdn.cookielaw.org, geolocation.onetrust.com
- Fundraise Up23 requestsFunctional
cdn.fundraiseup.com, static.fundraiseup.com, fndrsp.net
- Google6 requestsFunctional
www.google.com, fonts.googleapis.com, fonts.gstatic.com
- Coveo5 requestsFunctional
static.cloud.coveo.com
- Schema App3 requestsFunctional
cdn.schemaapp.com, data.schemaapp.com
- jsDelivr2 requestsContent delivery
cdn.jsdelivr.net
Cookies set before consent
The longest-lived tracking cookie it set was optimizelyEndUserId, from Optimizely, lasting about 6 months.
| Cookie | Purpose | Set by | Lasts |
|---|---|---|---|
| _gcl_au | Advertising | heart.org | 3 months |
| optimizelyEndUserId | Advertising | heart.org | 6 months |
| _oeu1790937377252r0.738522904432442$… | Analytics | a25670000279.cdn.optimizely.com (third party) | 6 months |
| optimizelySession | Analytics | heart.org | 6 months |
| fundraiseup_cid | Unclassified | heart.org | 13 months |
| fundraiseup_func | Unclassified | heart.org | Session |
| fundraiseup_stat | Unclassified | heart.org | Session |
| SC_ANALYTICS_GLOBAL_COOKIE | Unclassified | www.heart.org | 13 months |
| shell#lang | Unclassified | www.heart.org | Session |
| __cf_bm | Functional | heart.org | Under a day |
| __RequestVerificationToken | Functional | www.heart.org | Session |
| ASLBSA | Functional | www.heart.org | Session |
| ASLBSACORS | Functional | www.heart.org | Session |
| ASP.NET_SessionId | Functional | www.heart.org | Session |
| OptanonConsent | Functional | heart.org | 12 months |
The page also wrote 9 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.