• Resolved bostrb

    (@boosterbast)


    Hi,

    I cannot find anywhere in the documentation for the plugin how consent is managed.

    I currently have the meta pixel via GTM. From their it is quite clear How I can manage consent. However, I would like to switch to the facebook for woocommerce plugin. As far as I understand it adds:

    • The meta pixel
    • COnversion API

    For both the meta pixel and the conversion API I need consent. How do I manage this with the facebook for woocommerce API. In my opinion this should be part of the documentation of the plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi @boosterbast

    Currently, the Facebook for WooCommerce plugin does not have an in-built consent management system. It’s designed to add the Facebook pixel and Conversion API to your WooCommerce site, but the management of user consent is typically handled at the site level, not the plugin level.

    To manage consent, you would need to use a plugin like CookieYes, Cookie Consent for WP, Complianz, Cookie Notice, etc.

    Once you have a consent management plugin in place, you can configure it to control the firing of the Facebook pixel and Conversion API based on the user’s consent.

    I hope this helps clarify things for you. We appreciate your feedback about the need for this information in our documentation and will consider it for future updates.

    Thanks!

    Thread Starter bostrb

    (@boosterbast)

    Hi Shaheem,

    Thanks for the reply. I actually use Complainz to manage consent. So is in facebook for woocommerce the CAPI als also developed to integrate with Complainz? How can I see that the CAPI is not firing until consent is given?

    I see complianz blocks connect.facebook.net intil consent is given. Is that URL used for the CAPI?

    • This reply was modified 6 months, 1 week ago by bostrb.

    Hi @boosterbast

    So is in facebook for woocommerce the CAPI als also developed to integrate with Complainz?

    Our plugin does not inherently integrate with Complianz or any consent management plugin. It simply provides the functionality for the Facebook Pixel and Conversion API. However, I can see that an enhancement request has already been made here: https://github.com/woocommerce/facebook-for-woocommerce/issues/2748

    I see complianz blocks connect.facebook.net intil consent is given. Is that URL used for the CAPI?

    It’s important to note that the Conversion API works server-side, so it doesn’t rely on cookies or the same mechanisms as the pixel, which is client-side. Therefore, blocking a URL like connect.facebook.net may not impact the CAPI.

    However, to ensure that the CAPI is not firing until consent is given, you would need to configure this within your consent management plugin, Complianz in this case. You might need to contact Complianz support for more detailed instructions on setting this up.

    I hope this clarifies your concern. If you have any other questions, feel free to ask.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘How is consent currently managed?’ is closed to new replies.