Cross-domain Conversation Continuity
Implement cross-domain conversation continuity in the era of first-party cookies.
Discover how iAdvize handles data storage in this Help Center article : https://help.iadvize.com/hc/articles/216438047
Since the 2024 phase-out of third-party cookies, iAdvize can no longer reliably link visitor identities across domains. While this is good news for privacy in general, it means that multi-domain clients need to add a query parameter to their pages to maintain conversation continuity between websites that do not share a top-level domain. The principle is as follows. First, you need to detect whether the visitor browsing the website is in the middle of a conversation. To do this, we need to use the iAdvize web SDK and, more specifically, the iAdvize.get method on the conversation:id property. If the Web SDK returns a conversation identifier, then a conversation is in progress.
If the visitor is in the middle of a conversation on site A, and clicks on a link that will take him to site B, you'll need to add a specific url parameter to this link (named “idzconvid”, and which will take as its value the conversation identifier retrieved from the iAdvize.get method) so as to guarantee conversation continuity between site A and site B.
This is how it should be implemented :
Use the iAdvize WebSDK to retrieve the
conversationId
when a conversation is ongoing :
Add the conversationId to all relevant links.
Here is a full example of what it might look like :
See an example in this codesandbox : https://codesandbox.io/p/sandbox/cross-domain-conversation-continuity-hyx6fx
Last updated