Nodals RTD Module: Add support for publisher to override standard TCF… #14004
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
|
While I think your partner is in for a legal battle, no concerns about your choice here |
patmmccann
approved these changes
Oct 10, 2025
|
Thanks, @patmmccann |
ChrisHuie
approved these changes
Oct 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
… consent checks
Type of change
Description of change
We are working with a publisher who have a different setup.
No tcfControlModule installed and their position is that vendors "shouldn't seek to try to establish legal bases through the TCF as they are operating on the legal basis established by the controller, i.e us". In a nutshell, this change allows a publisher to explicitly state that they have gathered consent, so we can proceed without running our usual TCF consent checks.
Whilst we've added support for this new configuration flag, we will not yet open it up in documentation.
Other information