Integrations

We provide a few built-in third-party integrations which allow you 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.

We automatically integrate our default Functional, Analytics and Advertising tracking purposes into Google Consent Mode. This integration automatically updates Google Consent Mode whenever consent changes. This is supported by Google Tag Manager, Google Analytics, and Google Ads Conversion Tracking. Read more about this mode:

• Consent Mode (beta) - Analytics Help
• About consent mode (beta) - Google Ads Help

Our default consent mapping with Google Consent Mode is as follows:

• Analytics → analytics_storage
• Advertising → { ad_storage, ad_user_data, ad_personalization }
• Functional → { functionality_storage, personalization_storage, security_storage }
• SaleOfInfo → ads_data_redaction (enabled when 'tracker overrides trigger purpose' is unconsented and GoogleAdsRDP integration is enabled)

This mapping can be reconfigured for airgap.js versions 8.33.0 and later. In order to configure a specific parameter, set that parameter's associated trigger purposes (or force-enable the parameter) through the data-tracker-overrides script attribute. The following example sets the trigger purposes for analytics_storage to SaleOfInfo and Analytics:

data-tracker-overrides="[...] GoogleConsentMode:analytics_storage=SaleOfInfo,Analytics"

In order to force-enable a parameter, set its associated trigger purposes to on. The follow example does this for analytics_storage:

data-tracker-overrides="[...] GoogleConsentMode:analytics_storage=on"

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. Read more about this mode:

• Restricted data processing (CCPA) settings in Google’s publisher ad tags — AdMob & AdSense program policies
• Helping publishers comply with the California Consumer Privacy Act (CCPA) — Ad Manager and Ad Exchange program policies

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:

• Data Processing Options for Users in California — Facebook for Developers
• Limiting How Data is Used for People in California — Facebook for Business

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

• Turn on privacy-enhanced mode — YouTube Help

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:

• doNotTrack - Embed Options and Plugins - Support - Wistia

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

• Do-Not-Track

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

• Global Privacy Control (Brave sets this on by default)

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="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-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">

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

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