Skip to content
CookieTosser

What does colorado.edu track?

Before any consent, colorado.edu loaded 8 tracking companies and set 15 advertising or analytics cookies.

That's more tracking companies than 89% of the 2,450 sites we scanned.

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

Tracking companies
8
Tracking cookies
15
Third-party hosts
31
Cookies in total
25

Consent banner

No known consent management platform was detected on the page.

Companies contacted before consent

4 of the 15 companies it contacted before consent were social media companies.

  • Google Ads

    ad.doubleclick.net, 12320119.fls.doubleclick.net, 12399946.fls.doubleclick.net, stats.g.doubleclick.net

    11 requestsAdvertising
  • Bombora (IPredictive)

    js.ipredictive.com, ad.ipredictive.com

    2 requestsAdvertising
  • Spotify Ads

    pixel.byspotify.com

    1 requestAdvertising
  • TikTok

    analytics.tiktok.com, analytics-ipv6.tiktokw.us

    7 requestsSocial media
  • Snap

    tr.snapchat.com, sc-static.net, tr6.snapchat.com

    6 requestsSocial media
  • Meta

    connect.facebook.net, www.facebook.com

    5 requestsSocial media
  • LinkedIn

    snap.licdn.com, px.ads.linkedin.com

    4 requestsSocial media
  • Google Analytics

    www.googletagmanager.com, region1.analytics.google.com

    8 requestsAnalytics

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

  • gtranslate.net

    cdn.gtranslate.net

    1 requestUnclassified
  • getrave.com

    www.getrave.com

    1 requestUnclassified
  • Google

    www.google.com, adservice.google.com, fonts.googleapis.com, fonts.gstatic.com

    6 requestsFunctional
  • Spotify

    pixels.spotify.com

    2 requestsFunctional
  • Microsoft Azure

    localist-images.azureedge.net

    8 requestsContent delivery
  • Google Cloud

    mpc-prod-25-s6uit34pua-wl.a.run.app

    1 requestContent delivery
  • Amazon Web Services

    capi-automation.s3.us-east-2.amazonaws.com

    1 requestContent delivery

Cookies set before consent

The longest-lived tracking cookie it set was _ga, from Google Analytics, lasting about 13 months.

CookiePurposeSet byLasts
_fbpAdvertisingcolorado.edu3 months
_gcl_auAdvertisingcolorado.edu3 months
_scidAdvertisingcolorado.edu13 months
_scid_rAdvertisingcolorado.edu13 months
_tt_enable_cookieAdvertisingcolorado.edu13 months
_ttpAdvertisingcolorado.edu13 months
bcookieAdvertisinglinkedin.com (third party)12 months
cuAdvertisingipredictive.com (third party)12 months
IDEAdvertisingdoubleclick.net (third party)13 months
lidcAdvertisinglinkedin.com (third party)1 day
sc_atAdvertisingsnapchat.com (third party)13 months
ttcsidAdvertisingcolorado.edu13 months
ttcsid_CCRH2EJC77UDPV42AVRGAdvertisingcolorado.edu13 months
_gaAnalyticscolorado.edu13 months
_ga_WW2LE17NC1Analyticscolorado.edu13 months
__spdtUnclassifiedwww.colorado.edu12 months
_hashUnclassifiedugrad.apply.colorado.edu13 months
_hashUnclassifiedgrad.apply.colorado.edu13 months
_hashVUnclassifiedugrad.apply.colorado.edu13 months
_hashVUnclassifiedgrad.apply.colorado.edu13 months
_nodeUnclassifiedugrad.apply.colorado.eduSession
_nodeUnclassifiedgrad.apply.colorado.eduSession
__cf_bmFunctionallinkedin.com (third party)Under a day
li_gcFunctionallinkedin.com (third party)6 months
X-ABFunctionalsc-static.net (third party)1 day

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.