User consent and privacy settings. These settings help PAL SDK make decisions about the
identifiers used while generating nonce signals.
| Constructors | |
|---|---|
constructor
|
|
| Properties | |
|---|---|
allow
|
Whether PAL has consent to use identifiers and storage. |
force
|
Whether to force limited ads mode for the ad request. |
Constructors
constructor
new ConsentSettings(): ConsentSettings
| Returns | |
|---|---|
ConsentSettings
|
|
Properties
allowStorage
allowStorage: boolean
true as PAL automatically determines storage consent based on TCF data.
If factors other than TCF data determine whether or not to use limited ads in your app,
you can use the forceLimitedAds property to force limited ads mode, which
disables identifiers and storage used for ad serving. In a future release, the
allowStorage property becomes non-functional. Before this release,
allowStorage, TCF data, and forceLimitedAds are considered
when determining storage consent. During that transition period, do not set
this property to false or leave the property unset. These approaches might result in
disabling storage, which can reduce the effectiveness of ad requests. After the update,
you can stop setting this property. For details, see
Limited ads and first party identifier settings.
forceLimitedAds
forceLimitedAds: boolean
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 and
Limited ads and first party identifier settings.