Class: ConsentSettings

  • ConsentSettings provides various privacy and regulation settings for the PAL SDK.

  • These settings help in making decisions about the identifiers used for generating nonce signals.

  • The allowStorage property indicates if PAL has consent to use identifiers and storage, which needs to be determined by integrating with a CMP for IAB TCFv2 compliance.

Constructor

ConsentSettings

new ConsentSettings()

Properties

allowStorage

boolean

Whether PAL has consent to use identifiers and storage. This value should always be set to true now that PAL automatically determines storage consent based on TCF data. If TCF is insufficient for your app, you can use the forceLimitedAds property to force limited ads mode, which disables identifiers/storage used for ad serving. In a future release (approximately March 9, 2026), allowStorage will become a no-op. Before that date, allowStorage, TCF data, and forceLimitedAds will all be considered when determining storage consent. During that transition period, do not update your implementation to set this property false or to leave it unset, since that will result in disabling storage, which can reduce the effectiveness of ad requests. After that date, you may stop setting this property. For more information, see this article.

forceLimitedAds

public

boolean

Whether to force limited ads mode for the ad request. When unset or set to false, PAL will automatically determine the limited ads status from TCF data set by a CMP. When set to true, limited ads mode will be used regardless of TCF signals. In limited ads mode, PAL will not store, access, or send user identifiers for ad serving purposes. When programmatic limited ads are enabled, invalid traffic detection-only storage may still be used; see GoogleAdManagerSettings.disableLimitedAdsStorage. For more information about limited ads, see this general article and this PAL-specific article.