GDPR Delete of Identity Data

About Deleting Identity Data

When you delete identity data, the system performs these actions:

• orphans any identity IDs (which are the base IDs that are created by SAS Customer Intelligence 360) that are associated with the request. This means that an internal ID (the datahub ID) still exists in the system, but it is no longer connected to any information. This internal ID can still be used to reference generic event data, but that data is no longer associated with customer information.
• deletes other identity types (such as customer ID and login ID) that are associated with the request.
  Note: To honor opt-out requests from email and SMS communication, email addresses and phone numbers are retained in contact preferences. Retaining these addresses prevents SAS Customer Intelligence 360 from contacting any customers that have opted out of communication and also submitted a request for deletion under GDPR guidelines. However, email addresses and phone numbers are no longer associated with any identity data or event records.

  To remove the email addresses from the system, you must perform a separate request to delete records based on the identity type of email_id. To remove phone numbers, use the sms_id identity type.

• deletes email imprints that are associated with the request.

Delete Identities through the User Interface

1. Create the CSV file with the identity values that you want to delete. Follow these guidelines:
   • Make sure the CSV file includes a header row. The first row is always interpreted as a header row.
   • Values can be only subject IDs, customer IDs, or login IDs.
   • Each row in the CSV file should be a unique value.
   • Limit the input data to a maximum of 256 characters per row.

2. On the navigation bar, click AdministrationGeneral. Then click Table Management in Application Settings.

3. Create a table with the DELETELIST type. When you create the table, set these options on the data item:
   1. Enable the Identity check box to configure the data item as an identity column.
   2. Set the Identity type field to the identity type of the values that are in the CSV file.

   Click Done to return to the Table Management page.

4. Upload the CSV file.
   1. Enable the check box for the table that you created and click .
   2. Click Browse, select the file on your local computer, and click OK.

   The delete process starts when the file is imported.

5. To check the status of the delete request:
   1. On the Table Management page, click the entry for the table.
   2. Navigate to the Import History page.
   3. Find the entry for the most recent import job and click .

Delete Identities through the REST API

Use the customerJobs endpoint of the Marketing Data API to delete identity data from your system.

To submit a request to delete identity data:

1. Set up authorization for the REST API. For REST API calls, in most situations the access point type is going to be a General Access Point.

   When you create the access point, make note of the value in the External gateway host field. Use this value when you see the variable <external gateway host> in the documentation.

2. Send a POST call to the customerJobs endpoint to delete data. The call is similar to this example:
   POST https://<external gateway host>/marketingData/customerJobs

   POST https://<external gateway host>/marketingData/customerJobs

   Note: Be sure to use the JWT as the authentication token when you submit any REST calls.

   In the body of the call, define the delete request as a JSON object:

   { "jobType": "GDPR_DELETE", "identityType": "subject_id", "identityList": [ "12343455" ] }

   {
     "jobType": "GDPR_DELETE",
     "identityType": "subject_id",
     "identityList": [
       "12343455"
     ]
   }

   The delete request contains these members:

   Members of the Customer Delete Request

   Name	Required or Optional	Type	Description
   jobType	Required	String	The job type. Set this value to GDPR_DELETE.
   identityType	Required	String	The identity type that you are using to search the database. Use one of these values: customer_id login_id subject_id Note: You cannot submit a GDPR delete request with other identity types (such as device_id or visitor_id), because they are not considered strong identifiers for an individual.
   identityList	Required	List	The actual values of customer identities to delete. The value should match a real customer identity in the system. For example, if you specify a subject ID, data that is associated with the login ID and customer ID is also deleted for that customer. Follow these guidelines: Values must be lowercase. Values must match the type that is specified for identityType. The format for this value is similar to this example: ["subject_id1","subject_id2","subject_id3"] In the output data, a blank row is returned if there is no data associated with that ID.

   The response to the POST call contains the request ID for the delete job.

3. Use the request ID to view the request’s status. Submit a GET call similar to this example:
   GET https://<external gateway host>/marketingData/customerJobs/<delete_request_ID>

   GET https://<external gateway host>/marketingData/customerJobs/<delete_request_ID>

   After the request is processed, all data and customer attributes for the specified identity types are deleted.