GDPR Compliance: Facebook Pixel & Conversion API Integration Inquiry

I will try to answer your questions:

1. If the user accepts cookies, the pixel loads, but if they don’t accept them, it DOES NOT load (thus, I cannot track what that user does).

This is the expected behaviour, users have the right to opt out of tracking.

2. Facebook recommends using the Conversion API for better measurement, and PixelYourSite has been recommended to me. I’ve been told that I need to remove the pixel script that the cookie plugin loads and do everything through PixelYourSite. Is that correct? Or can I continue using my cookies plugin to load the Facebook Pixel (only if the user accepts cookies) and use PixelYourSite exclusively for the Conversion API?

It’s not possible to use our plugin just for API events, we need to control both the pixel and API events, so that deduplication works.

3. I’m not sure if I understand correctly that the Conversion API does not require user consent for cookies.

In essence, you need user’s permission for API events only. Those are Meta’s terms, but also GDPR requirements.

4. In case both the pixel and API have to be managed through PixelYourSite, does it seem like PixelYourSite will always load the pixel? To comply with GDPR, I need the pixel to only load if the user accepts cookies… Is that possible with PixelYourSite? (I’d like to continue using my cookies plugin).

As a general answer, we offer consent plugins developers filter that allow them to control our tags and API events. I don’t know if the consent plugin that you use blocks our events, that’s something you need to test.

5. And I understand that the Conversion API is something ADDITIONAL to the pixel, right? Would PixelYourSite be responsible for loading the Facebook pixel and the Conversion API simultaneously? Isn’t that redundant?

API events act like a back-up for pixel events. If both the pixel and the API are received, Meta will do something called deduplication, meaning that only the pixel event is processed.