This article provides comprehensive answers to all questions related to Cognigy.AI's usage of cookies in the Webchat.
It depends on the way the Webchat connects to the Webchat Endpoint. There are two variants, using HTTP Polling and using a Websocket.
Yes, it will get an "IO" cookie when using HTTP Polling.
Am I using HTTP Polling or Websockets?
By default, the Webchat will initiate with HTTP Polling and then immediately try to upgrade to a Websocket, meaning "both". You can override this behavior by using the "forceWebsockets" and "disableWebsockets" option as described in our Webchat Documentation. Because most modern browsers don't even allow third-party cookies without further configuration, we override the "forceWebsockets" option to "true" for those browsers.
What is the "IO" cookie used for?
The IO cookie is used as a compatibility layer to ensure that every message you send is forwarded to and processed by the same endpoint service in our backend.
Is the "IO" cookie used for user tracking?
No, since the "IO" cookie will not be stored in your browser. The "IO" cookie will not be stored in your browser since it does not have an "expiry date" set. After you reload your page, you will get a new "IO" cookie.
How can I make sure I only use Websockets?
You can do that by configuring your Webchat Embedding with the "forceWebsockets" option set to "true". To learn more about this, follow our Webchat Documentation.
You have to configure the Webchat to only use Websockets.
Why would I not use Websockets at all times?
If your end users are connecting from a restricted network environment (e.g. a Company or School network), they might get issues with Websockets due to technically outdated firewall or proxy setups.