docs: document enableTCFConsentCollection across SDKs [LIN-2078] - #169
Open
Shofiya2003 wants to merge 1 commit into
Open
docs: document enableTCFConsentCollection across SDKs [LIN-2078]#169Shofiya2003 wants to merge 1 commit into
Shofiya2003 wants to merge 1 commit into
Conversation
Add a Reading consent from a TCF CMP section to the Send Consent guide and to the Android, iOS, Flutter and React Native SDK pages, plus API reference table rows. The method derives Google Ads consent from an IAB TCF v2.2/v2.3 CMP's IABTCF_* keys; explicit setConsent values still win per signal. Supported on iOS and, from android-sdk 4.2.0, on Android.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Documents
enableTCFConsentCollection, which derives Google Ads consent from an IAB TCF v2.2/v2.3 CMP's standardIABTCF_*keys (purposes 1+7 forad_user_data, 3+4 forad_personalization, both gated on Google vendor consent, TCF vendor 755). ExplicitsetConsentvalues still win, per signal.setConsentmapping.Each page notes the opt-in is a legal judgement, that only TCF-compliant CMPs write these keys, and that the flag is not persisted so it must be called on every launch before
init.