Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to configure Consent Modes for GDPR compliance #2748

Open
razaanstha opened this issue May 20, 2024 · 2 comments
Open

Add an option to configure Consent Modes for GDPR compliance #2748

razaanstha opened this issue May 20, 2024 · 2 comments
Labels
type: enhancement The issue is a request for an enhancement.

Comments

@razaanstha
Copy link

razaanstha commented May 20, 2024

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

@rawdreeg rawdreeg added the type: enhancement The issue is a request for an enhancement. label May 24, 2024
@RiaanKnoetze
Copy link

@cl0udres
Copy link

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.

Looking forward to any updates on this.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

4 participants