# Consent Built-In Integrations (/docs/consent-management/configuration/consent-integrations/consent-built-in-integrations)

## Overview [#overview]

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.

Learn [how to customize Consent integrations](./customizing-consent-integrations.mdx) on your airgap.js script tag through our use case guide.

## ✅ Consent rules [#-consent-rules]

### Google Consent Mode [#google-consent-mode]

Please refer to [this page](./google-consent-mode.mdx).

### Google Ads Non-Personalized Advertising (NPA) [#google-ads-non-personalized-advertising-npa]

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`):

- [Manage privacy settings](https://developers.google.com/tag-platform/security/guides/privacy)

### Microsoft Consent Modes [#microsoft-consent-modes]

Please refer to the following pages:

- [Microsoft UET Consent Mode](./microsoft-uet-consent-mode.mdx)
- [Microsoft Universal Pixel Consent Mode](./microsoft-universal-pixel-consent-mode.mdx)

## 🚫 Do-not-sell integrations [#-do-not-sell-integrations]

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.

<Callout type="info">
  💡 These integrations are enabled whenever the 'tracker overrides trigger purpose', which defaults to `SaleOfInfo`, is both respected and unconsented.
</Callout>

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

### Google Ads Restricted Data Processing (RDP) [#google-ads-restricted-data-processing-rdp]

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:

- [Restricted data processing (CCPA) settings in Google’s publisher ad tags — AdMob & AdSense program policies](https://support.google.com/admob/answer/9598414)
- [Helping publishers comply with the California Consumer Privacy Act (CCPA) — Ad Manager and Ad Exchange program policies](https://support.google.com/admanager/answer/9561023)

### Facebook Pixel — Limit Data Use (LDU) [#facebook-pixel--limit-data-use-ldu]

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:

- [Data Processing Options for Users in California — Facebook for Developers](https://developers.facebook.com/docs/marketing-apis/data-processing-options/)
- [Limiting How Data is Used for People in California — Facebook for Business](https://www.facebook.com/business/help/1151133471911882)

### TikTok Pixel — Limit Data Use (LDU) [#tiktok-pixel--limit-data-use-ldu]

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:

- [Limited Data Use (LDU) for the Events API and Pixel — TikTok for Business Developers](https://business-api.tiktok.com/portal/docs?id=1770092377990145)

### YouTube Privacy-Enhanced Mode [#youtube-privacy-enhanced-mode]

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](./customizing-consent-integrations.mdx#list-of-all-supported-consent-integrations) 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:

- [Turn on privacy-enhanced mode — YouTube Help](https://support.google.com/youtube/answer/171780?hl=en#:~:text=Turn%20on%20privacy-enhanced%20mode)

### Vimeo Do Not Track Mode [#vimeo-do-not-track-mode]

We automatically override `player.vimeo.com` requests to enable their `dnt` (Do Not Track) player parameter. [Read more about this parameter here](https://help.vimeo.com/hc/en-us/articles/12426260232977-Player-parameters-overview).

### Wistia Do Not Track Mode [#wistia-do-not-track-mode]

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](https://wistia.com/support/developers/embed-options#donottrack)

## 🌐 Browser standards [#-browser-standards]

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

- [Do-Not-Track](https://en.wikipedia.org/wiki/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](https://globalprivacycontrol.org/) (Brave sets this on by default)

We are considering integrating with the new [Advanced Data Protection Control](https://www.dataprotectioncontrol.org/) standard designed to support a bannerless web with browser-provided consent signals.