We provide a few built-in third-party integrations which allow you to integrate consent rules with third party providers or auto-enable privacy-preserving features in third-party trackers.

These integrations can enable you to tag certain known tracker domains as essential, which would otherwise have to be tagged as Analytics/etc.

Please refer to this page.

We automatically override requests to some known trackers to proactively opt-in to privacy-preserving feature flags for CCPA/CPRA do-not-sell compliance. This can mean enabling a search query parameter or replacing domains with compatible less-privacy-invasive alternatives.

πŸ’‘ These integrations are enabled whenever the 'tracker overrides trigger purpose', which defaults to SaleOfInfo, is both unconsented and respected.

The tracker overrides trigger purpose can be configured via the data-tracker-overrides-unconsented-purpose attribute on the airgap.js script element.

We can override Google Ads / Doubleclick requests to enable their "Restricted Data Processing" mode. Unlike our other integrations, this is not enabled by default. Read more about this mode:

We override Facebook Pixel requests to enable their "Limited Data Use" feature, which limits how data can be stored and processed by Facebook based on local laws. Read more about this feature:

We automatically override requests to use, provided as part of YouTube's "Privacy-Enhanced Mode". Read more about this mode:

We automatically override requests to enable their dnt (Do Not Track) player parameter. Read more about this parameter here.

We automatically integrate with Wistia's embed APIs and override iframe requests to enable the doNotTrack option. Read more about this option:

We automatically opt users out of unessential tracking when any of these browser features are enabled:

We automatically opt users out of 'sale of personal information' tracking purposes when any of these browser features are enabled:

We are considering integrating with the new Advanced Data Protection Control standard designed to support a bannerless web with browser-provided consent signals.

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:

<script data-tracker-overrides="off" src="">

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-tracker-overrides="GoogleConsentMode FacebookLDU" src="">
<script data-tracker-overrides="GoogleConsentMode:ad_user_data=SaleOfInfo;ad_personalization=SaleOfInfo FacebookLDU" src="">

The full list of supported integration names can be found below:

Integration NameConfig NameAdditional Parameters
Google Consent ModeGoogleConsentModeYou 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*GoogleAdsRDPNone
Facebook LDUFacebookLDUNone
YouTube Privacy-Enhanced ModeYouTubePrivacyEnhancedModeNone
Vimeo Do Not Track modeVimeoDNTNone
Wistia Do Not Track modeWistiaDNTNone

* Google Ads RDP is not enabled by default and must be explicitly enabled depending on your use case.