Adobe Advertising support for the General Data Protection Regulation
Para Adobe Advertising Search, Social, & Commerce; Adobe Advertising DSP; Adobe Advertising Creative; e Adobe Advertising DCO
The General Data Protection Regulation (GDPR), a law in effect May 25, 2018, gives all individuals (data subjects) within the borders of the European Union (EU) control of their personal data and simplifies the regulatory environment for international business. This law applies to all businesses (data controllers) that offer goods or services to, monitor the behavior of, or collect personal data from individuals within the borders of the EU at the time their personal data is processed, regardless of the data controller’s business location.
Adobe CX Enterprise acts as a data processor for any personal data it receives and stores on behalf of its customers. As a data controller, you determine the personal data that Adobe CX Enterprise processes and stores on your behalf.
This document describes how Advertising Search, Social, & Commerce; Advertising Creative; Advertising DSP (Demand Side Platform); and Advertising DCO support your data subjects’ GDPR data access and deletion rights using the Adobe Experience Platform Privacy Service API and Privacy Service UI.
For more information about what GDPR means for your business, see GDPR and Your Business.
Tipos de solicitação de dados compatíveis com o Adobe Advertising
O Adobe Experience Platform permite que as empresas concluam as seguintes tarefas:
- Access a data subject’s cookie-level data or device ID-level data (for ads in mobile apps) within Search, Social, & Commerce, Creative, DSP, or DCO.
- Delete cookie-level data stored within Search, Social, & Commerce, Creative, DSP, or DCO for data subjects using a browser; or delete ID-level data stored within DSP for data subjects using apps on mobile devices.
- Verifique o status de uma ou de todas as solicitações existentes.
Configuração necessária para enviar solicitações para o Adobe Advertising
To make requests to access and delete data for Adobe Advertising, you must:
-
Deploy a JavaScript library to retrieve and remove your data subject cookies. A mesma biblioteca,
AdobePrivacy.js, é usada para todas as soluções da Adobe CX Enterprise.note important IMPORTANT As solicitações para algumas soluções da CX Enterprise não exigem a biblioteca da JavaScript, mas as solicitações para a Adobe Advertising exigem. You should deploy the library on the webpage from which your data subjects can submit access and delete requests, such as your company’s privacy portal. The library helps you retrieve Adobe cookies (namespace ID:
gsurferID) so that you can submit these identities as part of access and delete requests via the Adobe Experience Platform Privacy Service API.When the data subject asks to delete personal data, the library also deletes the data subject’s cookie from the data subject’s browser.
note NOTE Deleting personal data is different than Opt-Out, which stops the targeting of an end user with audience segments. However, when a data subject asks to delete personal data from Creative, DSP, or DCO, the library also sends a request to Adobe Advertising to opt out the data subject from segment targeting. For advertisers with Search, Social, & Commerce, we recommend that you provide the data subjects a link to https://www.adobe.com/privacy/opt-out.html, which explains how to opt out of audience segment targeting. -
Identify your CX Enterprise organization ID and make sure it’s linked to your Adobe Advertising accounts.
Uma ID de organização da CX Enterprise é uma sequência de 24 caracteres alfanuméricos anexada com “@AdobeOrg”. A maioria dos clientes do CX Enterprise recebeu uma ID de organização. If your marketing team or internal Adobe system administrator doesn’t know your organization ID, or isn’t sure if it’s been provisioned, then contact Adobe Customer Care at gdprsupport@adobe.com. Você precisará da ID da organização para enviar solicitações à API de privacidade usando o namespace
imsOrgID.note important IMPORTANT Entre em contato com o representante da Adobe Advertising de sua empresa para confirmar se todas as contas da Adobe Advertising de sua organização — incluindo contas do DSP ou anunciantes, contas do Search, Social, & Commerce e contas do Creative ou do DCO — estão vinculadas à sua ID da organização da CX Enterprise. -
Use either the Adobe Experience Platform Privacy Service API (for automated requests) or the Privacy Service UI (for ad-hoc requests) to submit access and delete requests to Adobe Advertising on behalf of the data subjects, and to check the status of existing requests.
For advertisers who have a mobile app to interact with data subjects and launch campaigns with DSP, you must download the Privacy-ready Mobile SDKs for CX Enterprise. The Mobile SDKs allow data controllers to set opt-out status flags, retrieve the data subject’s device ID (namespace ID:
deviceID), and submit requests to the Privacy Service API. Seu aplicativo móvel exigirá um SDK versão 4.15.0 ou superior.When you submit a data subject’s access request, the Privacy Service API returns a data subject’s information based on the specified cookie or device ID, which you then must return to the data subject.
When you submit a data subject’s delete request, the cookie ID or device ID and all cost, click, and revenue data associated with the cookie are deleted from the server.
note NOTE If your company has multiple CX Enterprise organization IDs, then you must send separate API requests for each. No entanto, você pode fazer uma solicitação de API para várias subsoluções da Adobe Advertising (Search, Social, & Commerce, Creative, DSP e DCO), com uma conta por subsolução.
All steps are necessary for Adobe Advertising. For more information about these and other related tasks you need to perform using the Adobe Experience Platform Privacy Service, and where to find the necessary items, see “Privacy Service overview.”
Valores de campo obrigatórios em solicitações JSON do Adobe Advertising
"company context":
"namespace": **imsOrgID**"value":<sua ID da organização da CX Enterprise>
"users":
-
"key":<geralmente o nome do titular dos dados> -
"action":**access**ou**delete** -
"user IDs":-
"namespace": **411**(que indica o espaço de cookies adcloud) -
"value":<o valor real da ID do cookie do titular dos dados conforme recuperado deAdobePrivacy.js>
-
-
"include": **adCloud**(que é o produto Adobe que se aplica à solicitação) -
"regulation": **gdpr**(que é o regulamento de privacidade que se aplica à solicitação)
Exemplo de solicitação enviada pelo titular dos dados usando uma ID de usuário do Adobe Advertising recuperada de AdobePrivacy.js
{
"companyContexts":[
{
"namespace":"imsOrgID",
"value":"5AB13068374019BC@AdobeOrg"
}
],
"users": [
{
"key": "John Doe",
"action":["access"],
"userIDs":[
{
"namespace":"411",
"value":"Wqersioejr-wdg",
"type":"namespaceId",
"deletedClientSide":false
}
]
}
],
"include":[
"adCloud"
],
"regulation":"gdpr"
}
Campos de dados retornados para solicitações de acesso
Este é um exemplo de uma resposta de acesso para o Adobe Advertising.
{
"jobId":"12345AD43E",
"action":"access",
"product":"adCloud",
"status":"complete",
"results":{
"userIDs":[
{
"namespace":"411",
"userID":" Wqersioejr-wdg "
}
],
"receiptData":{
"impressionCount":"100",
"clickCount":5,
"geo":[
"United States of America",
"San Francisco CA"
],
"profile":[
{
"pixelid":"111",
"ut1":"abc",
"ut2":"def",
"ut3":"ghi",
"ut4":"jkl",
"ut5":"mno"
},
{
"pixelid":"123",
"ut1":"abc",
"ut2":"def",
"ut3":"ghi",
"ut4":"jkl",
"ut5":"mno"
}
],
"matchingSegments":[
{
"segmentName":"AP4 - Art/Culture - In-Market",
"segmentID":"kV1mPa2aqPNWKSNtf325",
"serviceProvider":"Adobe"
},
{
"segmentName":"eXelate Australia Demographic - Jobs & Education - Job Seekers",
"segmentID":"2213789",
"serviceProvider":"exelate"
}
]
}
}
}