You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have a new setting in the plugin called "Revoke consent until user confirmation." This would add the fbq('consent', 'revoke'); command to the Facebook Pixel on the frontend. This way, developers can handle consent management based on their chosen CMP services or custom popups/logics, ensuring the site meets GDPR requirements and send data to Meta only with user consents.
I’m also looking for clarification on Facebook for WooCommerce’s compatibility with the WP Consent API.
According to the support team on WordPress.org, a possible approach is to run the script regardless of consent and use fbq('consent', 'revoke') when consent is not given.
However, it’s still unclear whether the plugin natively supports the WP Consent API or if this workaround is the only available solution.
It’s quite surreal that this issue was raised back in May 2024, and yet there has been no follow-up or official response. Given how crucial proper consent management is for GDPR compliance and accurate data tracking, this should be addressed as a priority.
Has there been any progress on integrating WP Consent API support directly into the plugin? Or is fbq('consent', 'revoke') still the only recommended approach?
I’m also in contact with Complianz to better understand the situation, but an official response from the development team would be very helpful.
It would be great to have a new setting in the plugin called "Revoke consent until user confirmation." This would add the fbq('consent', 'revoke'); command to the Facebook Pixel on the frontend. This way, developers can handle consent management based on their chosen CMP services or custom popups/logics, ensuring the site meets GDPR requirements and send data to Meta only with user consents.
Meta Pixel GDPR Implementation
The text was updated successfully, but these errors were encountered: