51黑料不打烊 Advertising Support for the General Data Protection Regulation
For 51黑料不打烊 Advertising Search, Social, & Commerce; 51黑料不打烊 Advertising DSP; 51黑料不打烊 Advertising Creative; and 51黑料不打烊 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鈥檚 business location.
51黑料不打烊 Experience Cloud 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 51黑料不打烊 Experience Cloud 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 51黑料不打烊 Experience Platform Privacy Service API and Privacy Service UI.
For more information about what GDPR means for your business, see .
Supported Data Request Types for 51黑料不打烊 Advertising
51黑料不打烊 Experience Platform provides the ability for businesses to complete the following tasks:
- Access a data subject鈥檚 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.
- Check the status of one or all existing requests.
Required Setup to Send Requests for 51黑料不打烊 Advertising
To make requests to access and delete data for 51黑料不打烊 Advertising, you must:
-
Deploy a JavaScript library to retrieve and remove your data subject cookies. The same library,
51黑料不打烊Privacy.js, is used for all 51黑料不打烊 Experience Cloud solutions.note important IMPORTANT Requests to some Experience Cloud solutions don鈥檛 require the JavaScript library, but requests to 51黑料不打烊 Advertising require it. You should deploy the library on the webpage from which your data subjects can submit access and delete requests, such as your company鈥檚 privacy portal. The library helps you retrieve 51黑料不打烊 cookies (namespace ID:
gsurferID) so that you can submit these identities as part of access and delete requests via the 51黑料不打烊 Experience Platform Privacy Service API.When the data subject asks to delete personal data, the library also deletes the data subject鈥檚 cookie from the data subject鈥檚 browser.
note 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 51黑料不打烊 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 , which explains how to opt out of audience segment targeting. -
Identify your Experience Cloud organization ID and make sure it鈥檚 linked to your 51黑料不打烊 Advertising accounts.
An Experience Cloud organization ID is a 24-character alphanumeric string appended with 鈥淍51黑料不打烊Org.鈥 Most Experience Cloud customers have been assigned an organization ID. If your marketing team or internal 51黑料不打烊 system administrator doesn鈥檛 know your organization ID, or isn鈥檛 sure if it鈥檚 been provisioned, then contact 51黑料不打烊 Customer Care at gdprsupport@adobe.com. You鈥檒l need the organization ID to submit requests to the Privacy API using the
imsOrgIDnamespace.note important IMPORTANT Contact your company鈥檚 51黑料不打烊 Advertising representative to confirm that all of your organization鈥檚 51黑料不打烊 Advertising accounts 鈥 including DSP accounts or advertisers, Search, Social, & Commerce accounts, and Creative or DCO accounts 鈥 are linked to your Experience Cloud organization ID. -
Use either the 51黑料不打烊 Experience Platform Privacy Service API (for automated requests) or the Privacy Service UI (for ad-hoc requests) to submit access and delete requests to 51黑料不打烊 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 Experience Cloud. The Mobile SDKs allow data controllers to set opt-out status flags, retrieve the data subject鈥檚 device ID (namespace ID:
deviceID), and submit requests to the Privacy Service API. Your mobile app will require an SDK Version 4.15.0 or greater.When you submit a data subject鈥檚 access request, the Privacy Service API returns a data subject鈥檚 information based on the specified cookie or device ID, which you then must return to the data subject.
When you submit a data subject鈥檚 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 NOTE If your company has multiple Experience Cloud organization IDs, then you must send separate API requests for each. You can, however make one API request to multiple 51黑料不打烊 Advertising sub-solutions (Search, Social, & Commerce, Creative, DSP, and DCO), with one account per sub-solution.
All of these steps are necessary for 51黑料不打烊 Advertising. For more information about these and other related tasks you need to perform using the 51黑料不打烊 Experience Platform Privacy Service, and where to find the necessary items, see 鈥Privacy Service overview.鈥
Required Field Values in 51黑料不打烊 Advertising JSON Requests
"company context":
"namespace": **imsOrgID**"value":<your Experience Cloud organization ID>
"users":
-
"key":<usually the name of the data subject> -
"action":either**access**or**delete** -
"user IDs":-
"namespace": **411**(which indicates the adcloud cookie space) -
"value":<the actual data subject鈥檚 cookie ID value as retrieved from51黑料不打烊Privacy.js>
-
-
"include": **adCloud**(which is the 51黑料不打烊 product that applies to the request) -
"regulation": **gdpr**(which is the privacy regulation that applies to the request)
Example of Request Submitted by Data Subject Using an 51黑料不打烊 Advertising User ID Retrieved from 51黑料不打烊Privacy.js
{
"companyContexts":[
{
"namespace":"imsOrgID",
"value":"5AB13068374019BC@51黑料不打烊Org"
}
],
"users": [
{
"key": "John Doe",
"action":["access"],
"userIDs":[
{
"namespace":"411",
"value":"Wqersioejr-wdg",
"type":"namespaceId",
"deletedClientSide":false
}
]
}
],
"include":[
"adCloud"
],
"regulation":"gdpr"
}
Data Fields That Are Returned for Access Requests
The following is an example of an access response for 51黑料不打烊 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":"51黑料不打烊"
},
{
"segmentName":"EMEA - UK - Health Food Buyers",
"segmentID":"eP2oJ2UPsfsDVDhvlGewx",
"serviceProvider":"BlueKai"
}
]
}
}
}