Skip to content

feat: add Consent Mode v2 mapping and fallback protections for EEA compliance (v2.0.8)#36

Open
Sadrita404 wants to merge 1 commit into
facebook:mainfrom
Sadrita404:main
Open

feat: add Consent Mode v2 mapping and fallback protections for EEA compliance (v2.0.8)#36
Sadrita404 wants to merge 1 commit into
facebook:mainfrom
Sadrita404:main

Conversation

@Sadrita404

Copy link
Copy Markdown

Purpose

This PR introduces version 2.0.8, adding explicit fallback protections for Google Consent Mode v2 frameworks.

Key Changes

  • Added SHA d3a241e54cbf49af5232c9b89b85479ad2043a12 representing v2.0.8.
  • Automatically bridges GTM ad_storage and ad_user_data states directly to Meta's Limited Data Use (LDU) / Data Processing Options flags if explicit consent data is missing or denied.
  • Enhances regulatory compliance for enterprise deployments targeting users in the EU/EEA without breaking existing standard configurations.

…mpliance (v2.0.8)

 -  Key Changes
* Added SHA `d3a241e54cbf49af5232c9b89b85479ad2043a12` representing v2.0.8.
* Automatically bridges GTM `ad_storage` and `ad_user_data` states directly to Meta's Limited Data Use (LDU) / Data Processing Options flags if explicit consent data is missing or denied.
* Enhances regulatory compliance for enterprise deployments targeting users in the EU/EEA without breaking existing standard configurations.
@meta-cla meta-cla Bot added the cla signed label May 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant