*** ** * ** ***

User consent and privacy settings. These settings help PAL SDK make decisions about the identifiers used while generating nonce signals.

| Constructors ||
|---|---|
| `https://developers.google.com/ad-manager/pal/html5/reference/class/goog.pal.ConsentSettings#goog.pal.ConsentSettings.constructor` |   |

| Properties ||
|---|---|
| `https://developers.google.com/ad-manager/pal/html5/reference/class/goog.pal.ConsentSettings#goog.pal.ConsentSettings.forceLimitedAds` | Whether to force limited ads mode for the ad request. |

## Constructors

*** ** * ** ***

### constructor

`new ConsentSettings(): https://developers.google.com/ad-manager/pal/html5/reference/class/goog.pal.ConsentSettings`

| Returns ||
|---|---|
| `https://developers.google.com/ad-manager/pal/html5/reference/class/goog.pal.ConsentSettings` |   |

## Properties

*** ** * ** ***

### forceLimitedAds

`forceLimitedAds: boolean` Whether to force limited ads mode for the ad request. When unset or set to a `false` value, PAL determines the limited ads status from TCF data set in a CMP. When set to the `true` value, PAL uses limited ads mode regardless of TCF signals. In limited ads mode, PAL doesn't store, access, or send user identifiers for ad serving purposes. When the app enables programmatic limited ads, the app might still use invalid traffic detection-only storage. For details, see `GoogleAdManagerSettings.disableLimitedAdsStorage`. For details on limited ads, see [Limited ads](https://support.google.com/admanager/answer/9882911) and [Limited ads and first party identifier settings](https://developers.google.com/ad-manager/pal/html5/limited-ads-first-party-identifier-settings).