Google Chrome has announced plans to block third-party cookies end of 2023. Pega embedded AWS CCP Screen will be impacted ?

General
, , , , , ,
1

Google Chrome has announced plans to block third-party cookies will there be any impact to Pega embedded CCP Screen functionality in Pega.

Please see the below information from pega :backhand_index_pointing_down:

Amazon Connect uses cookies for authentication. As part of Google’s Privacy Sandbox initiative, Google Chrome has announced plans to block third-party cookies (that is, cookies passed between two top level domains). This topic explains what you need to do to ensure your agents can continue using Chrome with Amazon Connect.

  • If you are using custom agent applications with the CCP, Customer Profiles, or Wisdom, you must upgrade to the latest available version of the Amazon Connect Streams API. This upgrade prevents the blocking of third-party cookies from impacting Amazon Connect across Chrome and all supported browsers.

  • If you are using the Amazon Connect CTI Adapter, you need to upgrade to the latest version of the CTI Adapter (version 5.21.1 onwards).

We recommend existing customers upgrade to the latest version of the Streams API before the end of 2023. If this is not possible, you can apply a Chrome enterprise policy to enable third-party cookies for your Amazon Connect instance. While a viable interim solution, we recommend that customers still upgrade as soon as possible in case Google does not support this override indefinitely.

Link reference:-

https://privacysandbox.com/open-web/#the-privacy-sandbox-timeline
https://chromeenterprise.google/policies/#BlockThirdPartyCookies
https://docs.aws.amazon.com/connect/latest/adminguide/admin-3pcookies.html

2

@DSundaravadivelu In essence, the Pega embedded Amazon Connect CTI functionally should not be affected. The key lies in upgrading to the most recent version of the Amazon Connect Streams API.it’s always a good idea to stay updated with any changes and adapt accordingly to ensure smooth operation of your applications.

3

Thanks @penus1! I suppose the streams API is used to host the CCP within Pega to deliver the CTI link. So, am I right in understanding that it needs to be updated within the Pega infrastructure by @DSundaravadivelu ? If so, is there any documentation that you can help with for the same ?

4

@penus1 Thanks for your reply. Based on the Pega CTI Link Configuration with AWS Connect, The documents not providing any information on which API version the CTI link will use.

We don’t have any plans for upgrade sooner. Is there any way we can check to see what API version Pega is trying to connect AWSConnect ? So that we can confirm the Pega 8.3 will be impact based on the change from Google Chrome.

5

@HaribhaskarA17012342 To change the amazon-connect streams version, override PegaCall script bundle, remove amazon-connect-streams-v1.2.0.2 and create a new file as amazon-connect-streams-V1.8.x. Once the new file is added add the new file to PegaCall script bundle.

6

The version which we’ve inhouse is less than 1.7 and is 1.2.0.2