Description
Currently, the GDPR API subjects responds with the Journey Customer cookie ID. This specific response is being deprecated and the cookie ID will no longer be provided through the GDPR API subjects search.
Originally, the Journey Customer cookie ID represented the end user in the Journey Services. Before the release of Identity Stitching, customers could submit a GDPR request for that cookie ID, and the corresponding Journey Data was exported/removed from the journey services accordingly.
With the release of Identity Stitching, customers should now delete the full journey history for an end user now by submitting a GDPR request with the corresponding externalContactId. The cookie ID is no longer necessary. To free up resources and complete the deprecation of legacy Journey services, we must stop providing the cookie ID from the GDPR API subjects call.
Change Category
API
Change Context
In order to fully deprecate the legacy Altocloud Journey Customer services and free up related resources, we must remove Journey Customer cookie id response in the subject request. Since the release of Identity Stitching customers have been able to use the external contact ID in the same fashion to access and remove the same information.
Change Impact
This change affects customers who rely on the GDPR API subjects search to return a journeyCustomer cookie ID. On the date of change, the GDPR API will no longer return a journeyCustomer cookie ID in response to the subjects search. The GDPR API will return a journeyCustomer cookie ID until the removal date on May 24, 2023.
Date of Change
May 24, 2023
Impacted APIs
GET /api/v2/gdpr/subjects
References
[GDPR-491]
[GDPR-492]