...
GDPR consent is separated into two main sides: consent for vendors, which are third parties in the site that may use personal data from the users (ad providers, analytics systems, etc.), and consent for the publisher itself, when personal data is processed by the publisher.
While vendor consent is pretty much standard to be available in CMPs, publisher consent may not be needed in every application, given that for a great deal lot of publisher sites, no personal information is directly processed by the publisher. AdConsent makes vendor consent available out of the box, but for the cases where publisher consent is also needed, the function setPublisherPurposes needs to be called at configuration time to enable publisher consent in AdConsent. This feature applies to GDPR only.
...
| Code Block |
|---|
PubConsentSettings = {
purposes: [<array of Integer>],
legIntPurposes: [<array of Integer>],
stacks: [<array of Integer>],
legIntStacks: [<array of Integer>],
customPurposes: {
definition: [<array of {
id: Integer,
name: String,
description: String,
descriptionLegal: String}>],
purposes: [<array of Integer>],
legIntPurposes: [<array of Integer>]
}
}COPY |
PubConsentSettings.purposes
...
Array holding the IAB standard stacks used by the publisher that are under the publisher's Legitimate Interest. It works just like the PubConsentSettings.legIntPurposes field , but now applied to stacks.
...
Array holding the custom purposes definitions. A custom purpose is defined by its id, name, description and descriptionLegal fields. These fields should be written in English. To provide additional translations to these purposes, the setTranslationFiles API function must be used to accomplish that.
...