This error message by Facebook, or Meta, is usually thrown when trying to configure the Facebook Pixel. There are 3 main reasons this error is thrown:
- If you’re using a WordPress plugin for example, or any local instance to check the configuration, that uses your browser to fire a Facebook Pixel. It might be you’re using a AdBlocker that blocks any requests to facebook.com.
- Maybe you’re checking the implementation directly from your account on Facebook.com/Meta.com. Facebook doesn’t use an AdBlocker obviously, but might stumble upon a Consent Management tool like Complianz. It will then logically come to this conclusion:
We detected event code but the pixel has not activated for this event, so no information was sent to Meta. Complianz will leave the code as is, but sets it to text/plain. Only on consent the event code is initialised and can be fired. You can disable the Integration for Facebook during the tests to verify your installation.
- The implementation is faulty, maybe an error in the Pixel ID, and you should check your browser console for errors. This can also spot issues with Consent Security Policies that can also deny third party sources.
