Customizing Consent Integrations
Disable or enable specific integrations for your Consent Management product
Overview
By default, we enable all of our available consent integrations except Google Ads NPA and Google Ads RDP. Should you wish to enable/disable some or all of these integrations, you can do so via the data-integrations script attribute.
Disabling all consent integrations, relying only on regulation of network requests & cookies:
<script data-integrations="off" src="https://transcend-cdn.com/cm/BUNDLE_ID/airgap.js">To enable only specific integrations, you can pass a list of space-separated integration names. Each integration may accept optional named parameters that are ;-separated. For each parameter, you can specify a key and a value that are separated by =. Putting this all together in a few examples:
<script data-integrations="GoogleConsentMode FacebookLDU" src="https://transcend-cdn.com/cm/BUNDLE_ID/airgap.js">
<script data-integrations="GoogleConsentMode:ad_user_data=SaleOfInfo;ad_personalization=SaleOfInfo FacebookLDU" src="https://transcend-cdn.com/cm/BUNDLE_ID/airgap.js">List of All Supported Consent Integrations
| Integration Name | Config Name | Additional Parameters |
|---|---|---|
| Google Consent Mode | GoogleConsentMode | You can modify our default mapping to change how GCM purposes maps to Transcend purposes, e.g. ad_user_data=SaleOfInfo;ad_personalization=SaleOfInfo |
| Google Ads NPA* | GoogleAdsNPA | None |
| Google Ads RDP* | GoogleAdsRDP | Google Ads RDP can be selectively applied to specific tags with e.g. tags=TAG1,TAG2,TAG3 |
| Microsoft UET Consent Mode | MicrosoftUETConsentMode | You can modify our default mapping to change how the Microsoft UET Consent Mode ad_storage purpose maps to Transcend purposes, e.g. ad_storage=Advertising,SaleOfInfo |
| Microsoft Universal Pixel Consent Mode | MicrosoftUniversalPixelConsentMode | You can modify our default mapping to change how the Microsoft Universal Pixel Consent Mode ad_storage purpose maps to Transcend purposes, e.g. ad_storage=Advertising,SaleOfInfo |
| Facebook LDU | FacebookLDU | You can force all requests to facebook.com and facebook.net to include an LDU flag using our request override functionality with strict, i.e. FacebookLDU:strict. |
| TikTok LDU | TikTokLDU | You can force all requests to tiktok.com to include an LDU flag using our request override functionality with strict, i.e. TikTokLDU:strict. You can also modify which purpose(s) trigger LDU with purposes, e.g. purposes=Purpose1,Purpose2. By default, LDU is triggered by the SaleOfInfo purpose. |
| YouTube Privacy-Enhanced Mode | YouTubePrivacyEnhancedMode | You can modify which purpose(s) trigger YouTube Privacy-Enhanced Mode with purposes, e.g. purposes=Purpose1,Purpose2. By default, YouTube Privacy-Enhanced Mode is triggered by the Advertising and SaleOfInfo purposes. You can also force-enable YouTube Privacy-Enchanged Mode with on, i.e. YouTubePrivacyEnhancedMode:on |
| Vimeo Do Not Track mode | VimeoDNT | None |
| Wistia Do Not Track mode | WistiaDNT | None |
* Google Ads NPA and Google Ads RDP are not enabled by default and must be explicitly enabled depending on your use case.