Skip to content
CookieTosser

What does meta.com track?

Before any consent, meta.com loaded 1 tracking company and set 2 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 www.meta.com/de/en once and clicking nothing. How we scan

Tracking companies
1
Tracking cookies
2
Third-party hosts
7
Cookies in total
2

Consent banner

No known consent management platform was detected on the page.

Companies contacted before consent

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

  • Meta

    static.xx.fbcdn.net, connect.facebook.net, www.facebook.com, scontent.xx.fbcdn.net

    48 requestsSocial media

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

  • fbsbx.com

    lookaside.fbsbx.com

    5 requestsUnclassified
  • fbthirdpartypixel.com

    metadotcom.fbthirdpartypixel.com

    2 requestsUnclassified
  • conversionsapigateway.com

    gw.conversionsapigateway.com

    1 requestUnclassified

Cookies set before consent

The longest-lived tracking cookie it set was datr, lasting about 13 months.

CookiePurposeSet byLasts
datrAdvertisingwww.meta.com13 months
localeAdvertisingwww.meta.com7 days

The page also wrote 8 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.