Skip to main content
Resolutions

"Enable Facebook integration"

What this Monitoring suggestion means, why you're seeing it and how to resolve it

Last updated About 3 hours ago

Enable Facebook integration is a suggestion from Consent Studio Monitoring, not an error. In the recommendations email it is listed under Suggestions. Active recommendations show on the Start page of your domain's dashboard and on the Recommendations page (Monitoring dropdown in the top bar).

Already handling consent for Facebook/Meta another way? Then this suggestion is safe to ignore. See Already handling consent another way? below.

What this recommendation means

Our scan found code from Facebook (Meta) running on your website, while the Facebook Pixel integration is not enabled in Consent Studio. The recommendation reads:

"You are running code from Facebook, without having the Facebook Pixel enabled in Consent Studio."

Your website and consent banner keep working as usual. The suggestion is about how the consent your visitors give in the banner reaches Meta.

Why you're seeing it

Two things are true for your website at the same time:

  • Monitoring found Facebook code on your website.

  • The Meta Pixel Consent API integration under Web CMP > Integrations is not switched on.

Why it matters: with the integration enabled, Consent Studio revokes consent for the Meta Pixel until consent is known, and grants it as soon as a visitor gives Marketing consent in your banner. Without the integration, Consent Studio does not pass your visitors' choice on to the Meta Pixel. See Meta Pixel Consent API x Consent Studio CMP.

How to resolve it

1

Enable the Meta Pixel Consent API integration

Switch on the integration in Consent Studio and add one line to your Meta Pixel base code. Follow the steps in Meta Pixel Consent API x Consent Studio CMP. For an overview of all integrations, see About built-in integrations.

2

Check the result

The suggestion closes by itself as soon as you switch on the integration and save. You don't have to wait for the next scan.

Already handling consent another way?

If you have set up your own method for handling consent for Facebook/Meta, this suggestion is safe to ignore. You can also dismiss it on the Recommendations page. Dismissed recommendations don't re-appear for a configurable cooldown period. See About Web Recommendations & Troubleshooting.

Common questions

My website works fine. Is something wrong?

No. This is a suggestion, not an error. Your website and banner keep working. It only tells you that Facebook code runs on your site while the Facebook integration is not enabled in Consent Studio.

Do I need to change my Meta Pixel code?

Yes, besides switching on the integration you add one line to your Meta Pixel base code. The exact line and where to put it are in Meta Pixel Consent API x Consent Studio CMP.

Which consent category does the Meta Pixel follow?

Marketing. Consent for the Meta Pixel is granted when a visitor grants Marketing consent in your banner.

I already handle Meta consent myself. Do I need this integration?

No. If you have set up an alternative method for handling consent for Facebook/Meta yourself, you can ignore or dismiss this suggestion.

Still unsure? Contact us and include your domain.

Was this helpful?

Still need help? Ask the team