Customizing Consent Integrations
By default, we enable all of our available consent integrations except Google Ads RDP. Should you wish to enable/disable some or all of these integrations, you can do so via the data-tracker-overrides script attribute:
Disabling all consent integrations, relying only on regulation of network requests & cookies:
HTML
<script data-tracker-overrides="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:
HTML
<script data-tracker-overrides="GoogleConsentMode FacebookLDU" src="https://transcend-cdn.com/cm/BUNDLE_ID/airgap.js"> <script data-tracker-overrides="GoogleConsentMode:ad_user_data=SaleOfInfo;ad_personalization=SaleOfInfo FacebookLDU" src="https://transcend-cdn.com/cm/BUNDLE_ID/airgap.js">
| 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 RDP* | GoogleAdsRDP | None |
| Facebook LDU | FacebookLDU | None |
| YouTube Privacy-Enhanced Mode | YouTubePrivacyEnhancedMode | None |
| Vimeo Do Not Track mode | VimeoDNT | None |
| Wistia Do Not Track mode | WistiaDNT | None |
* Google Ads RDP is not enabled by default and must be explicitly enabled depending on your use case.