Skip to content
CookieTosser

What does dev.to track?

Before any consent, dev.to loaded 1 tracking company and set 4 advertising or analytics cookies.

That's fewer tracking companies than most sites we scanned: 75% of the 2,450 sites we checked loaded more.

Scanned October 2, 2026 from Germany, loading dev.to once and clicking nothing. How we scan

Tracking companies
1
Tracking cookies
4
Third-party hosts
3
Cookies in total
5

Consent banner

No known consent management platform was detected on the page.

Companies contacted before consent

1 of the 2 companies it contacted before consent were analytics companies.

  • Google Analytics

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

    2 requestsAnalytics

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

  • forem.com

    forem.com

    1 requestUnclassified

Cookies set before consent

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

CookiePurposeSet byLasts
_gaAnalyticsdev.to13 months
_ga_TYEM8Y3JN3Analyticsdev.to13 months
ahoy_visitAnalyticsdev.toUnder a day
ahoy_visitorAnalyticsdev.to13 months
_Devto_Forem_SessionUnclassifieddev.to56 days

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.