The Meta Pixel (connect.facebook.net) tracks visitor behaviour for ad targeting and conversion measurement and transmits data to Meta in the USA.
The Meta Pixel is a pure marketing tool — there is no variant that would be permitted without consent. Unlike with analytics tools, anonymisation does not help here: the purpose is recognising individual people across websites, and that is exactly what requires prior, active agreement under § 25 (1) TDDDG.
In the Fashion ID decision (C-40/17) the CJEU made clear that site operators and Meta are jointly responsible for the collection and transmission of the data. In practice that means: you need not only the consent but also the joint-controllership agreement (controller addendum) provided by Meta, and you must disclose its core content in the privacy policy.
The Conversions API (server-side tracking) does not change the legal position. Events transmitted server-side need the same consent as the client-side pixel — running the API without a consent check merely moves the problem to the server.
For marketing tracking, § 25 (1) TDDDG applies: access to the device only with prior consent. The CJEU stresses the joint controllership of site operator and Meta for the collection. Without consent and without a joint-controllership agreement (Art. 26 GDPR) there is no basis.
The free scan checks the delivered HTML and shows which services are embedded, whether a cookie banner is detected and whether privacy-policy and legal-notice links are present — with context for each finding. It is not a substitute for legal advice.
This text is general information to the best of our knowledge, not legal advice. For an individual case, consult a law firm specialising in IT law.