This repository was archived by the owner on Apr 23, 2024. It is now read-only.
Basic setup for Consent V2 #15
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@BrentRobert what's the plan with Consent V2 support? |
Contributor
Author
We're currently in testing phase. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created an event based consent to gtag.
By default this option will be off and will have no impact on existing users.
The 'essential', 'marketing', 'analytical' and 'personalization' groups need to be available to sent all consent parameters.
The 'personalization' one did not exist, and is automatically created.
GTAG needs to be injected AFTER the 'phpro_cookie_gtag' block as it's important to first DENY every consent.