Transcend provides several built-in third-party integrations that allow you to integrate consent rules with external providers or automatically enable privacy-preserving features in third-party trackers.

These integrations can help you tag certain known tracker domains as Essential, which might otherwise need to be tagged as Analytics, Advertising, etc.

To learn how to customize these integrations on your airgap.js script tag, please refer to the Customizing Consent Integrations guide.

These integrations are related to specific consent modes and standards:

Please refer to Transcend's dedicated documentation page for Google Consent Mode.

We can override Google Ads / Doubleclick requests to enable their "Non-Personalized Advertising" feature. Unlike most of our other integrations, this is not enabled by default. Read more about this feature (see allow_ad_personalization_signals):

Please refer to the following pages:

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 may involve enabling a search query parameter or replacing domains with compatible, less-privacy-invasive alternatives.

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. This mode is useful for restricting the collection of sensitive data, such as health and financial information. Unlike most of 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.

We can also force all requests to facebook.com and facebook.net to include an LDU flag using our request override functionality. This can be enabled by adding "FacebookLDU:strict" to your data-tracker-overrides / airgap.loadOptions.trackerOverrides config, e.g. data-tracker-overrides="VimeoDNT YouTubePrivacyEnhancedMode WistiaDNT GoogleConsentMode FacebookLDU:strict". This mode is not required, and helps to ensure that the LDU flag is added to Facebook requests even when Facebook Pixel might otherwise be misconfigured.

Read more about this feature:

We override TikTok Pixel requests to enable their "Limited Data Use" feature, which limits how data can be stored and processed by TikTok based on local laws.
We can also force all requests to tiktok.com to include an LDU flag using our request override functionality. This can be enabled by adding "TikTokLDU:strict" to your data-tracker-overrides / airgap.loadOptions.trackerOverrides config, e.g. data-tracker-overrides="VimeoDNT YouTubePrivacyEnhancedMode WistiaDNT GoogleConsentMode TikTokLDU:strict".

Read more about this feature:

We automatically override youtube.com requests to use youtube-nocookie.com (provided as part of YouTube's "Privacy-Enhanced Mode") when the Advertising or SaleOfInfo purpose is respected and unconsented. You can configure this integration to use different trigger purposes, or to be force-enabled - see this table for details.

We recommend that the youtube-nocookie.com data flow be given the Essential purpose, which we do automatically whenever the youtube.com data flow is given any purpose.

Read more about this mode:

We automatically override player.vimeo.com 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 fast.wistia.com 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: