Genesys Cloud
Deprecation: journeyCustomer cookie id from GDPR API subjects response contract
Announced on | Effective date | Aha! idea |
---|---|---|
2023-02-22 | 2023-03-24 | - |
On May 17, 2023, Genesys will remove one aspect of the GDPR API’s response contract. The GDPR API will not return a journeyCustomer cookie id in response to the subjects search. On February 22, 2023, Genesys will discontinue support for the ability to return a journeyCustomer cookie id through the GDPR API subjects search. The GDPR API will return a journeyCustomer cookie id until the removal date on May 24, 2023.
FAQs
What does this mean?
Between the announcement date and the removal of the feature, Genesys will not address bugs or minor issues specific to this feature. Genesys will continue to resolve any major breakage until the removal date.
Am I affected?
This feature deprecation affects customers who rely on the GDPR API subjects search to return a journeyCustomer cookie id.
What do I need to do before the removal date?
Currently, customers do not have a direct method to access the journeyCustomer cookie id outside the GDPR API subjects search. Therefore, Genesys recommends that customers do not use the GDPR API subjects search to return a journeyCustomer cookie id.
The POST GDPR API, POST /api/v2/gdpr/requests will continue to support journeyCustomer. The GDPR API will continue to return subjects that match all other subjects including name, userId, externalContactId, dialerContactId, socialHandle, externalId, addresses, phoneNumbers, and emailAddresses.
For more information about the GDPR API, see GDPR & Privacy APIs in the Genesys Cloud Developer Center.
Who should I contact if I need help or have additional questions?
Reach out to your local Genesys representative or contact My Support.