This record is generated by AI from the cited source. How AI is used
Consent settings link a feature matrix to consent records so revoking consent can remove dependent features from warehouse and historical data, or just report it; not yet for Redshift or Databricks.
- Platform
- Hightouch
- Capability
- Consent & preferences · Governance
- Vendor's name
- Consent settings
- First recorded
- Record last updated
Record dates describe acquisition and updates, not human review. About corrections.
Lifecycle history 1 state
- GASep 2026First recorded 17 Oct 2026 · recorded from the source history · vendor changelog · hightouch.com ↗ · archived copy, 25 Oct 2026 ↗
Something wrong or out of date in this record? , ideally with a link to better evidence. How corrections work
Consent & preferences on other platforms latest first
- TealiumOneTrust consent integration vendor/service-level consent signalsGA4 Nov 2026
- TealiumFacebook Conversions connector opt_out parameter removalRetired4 Nov 2026
- KlaviyoEmail tracking consent block on preference pagesGA3 Nov 2026
- Adobe AJOTracking consent enforcement without blocking email deliveryGA29 Oct 2026
- TealiumUsercentrics v3 consent integration Vendor ID configurationGA28 Oct 2026
- TealiumUsercentrics v2 consent integration consent-change callbacksGA21 Oct 2026
- TealiumDidomi v2 consent management integrationGA21 Oct 2026
- TealiumUsercentrics v3 consent integrationGA14 Oct 2026
- TealiumSecuriti.ai consent integrationGA14 Oct 2026
- TealiumMicrosoft Clarity tag Consent API v2 supportGA14 Oct 2026