Does suuport pixel plugins?

Hi Raoul,

there is no dedicated PixelYourSite connector, but you do not really need one: FAZ Cookie Manager blocks the pixels that PixelYourSite (or any other pixel plugin) loads, because it works at the script and network level rather than by integrating with each plugin one by one.

When a pixel plugin outputs a tag – the Meta/Facebook Pixel (connect.facebook.net / fbevents.js), TikTok, Pinterest, Google Ads and GA4, and so on – FAZ intercepts it both in the page HTML (server side) and when it is injected by JavaScript at runtime, and holds it back until the visitor accepts the matching category (Marketing for advertising pixels, Analytics for measurement). The major pixel providers are already in the built-in provider list, so in most setups this works out of the box: with consent denied the pixel does not fire and no request reaches the third party, and on accept it is released.

The one thing I would recommend is to keep a single source of truth for consent. PixelYourSite has its own GDPR / cookie-consent options; if you let FAZ handle the gating, turn those off in PixelYourSite for the same pixels, so the two are not both trying to decide when a pixel may fire. FAZ then blocks before consent and releases on accept.

If you fire Google tags through PixelYourSite, FAZ also supports Google Consent Mode v2, so the Google consent signals are set correctly.

If a specific pixel is loaded in an unusual way and is not caught automatically, you can add a rule for it under Settings -> Script Blocking (match by URL fragment, script ID, or CSS class), and running the built-in Cookie Scanner will pick up the cookies it sets so they appear in your cookie declaration.

If you tell me exactly which pixels you run, I am happy to confirm they are covered.

@alekv thank you!