You may integrate the Web Tag for a single LivePerson account across two or more websites with different base domains (for example, a.com and b.com). Web messaging is supported in this use case, and there is also capability to maintain the consumer's experience "across domains", also known as cross-domain.
This page explains LivePerson’s web messaging support for persisting the consumer’s identity, conversation, and other information while they navigate across different domains.
Example use case:
- Consumer starts a conversation on a webpage on
a.com that is tagged with your LivePerson account's Web Tag. - Consumer navigates to a webpage on
b.com that is also tagged with your LivePerson account's Web Tag. - The same conversation automatically loads on the
b.com webpage (expected "cross-domain" behavior).
Unauthenticated cross-domain web messaging
What is the “Cross-Domain” feature?
This account feature (when activated) enables a web messaging consumer's unauthenticated identity, conversation, and other information to persist while navigating between multiple sites that possess different base domains, provided that all sites are tagged with the same LivePerson account.
This feature enables a seamless, continuous experience for unauthenticated consumers across sites that the LivePerson account declares/configures as "Monitored Domains".
How to enable / requirements:
- Enable the Cross-Domain feature flag
- Contact your LivePerson Account Team, or the LivePerson Customer Care team via 24/7 Messaging at LivePerson.com, for assistance with enabling Cross-Domain
- Configure the different domains in the “Monitored Domains” whitelist
- See this Knowledge Center article for instructions
- The current web messaging consumer must be unauthenticated and using a capable/supported browser
- See below for browser limitations
Due to modern browser limitations and privacy initiatives support is limited to only certain browser/OS combinations.
Read more about how unauthenticated cross-domain works and browser/OS limitations in the developer documentation: Unauthenticated cross-domain web messaging
Authenticated cross-domain web messaging
LivePerson web messaging supports authenticated consumer identities in addition to unauthenticated.
While unauthenticated identities are generated anonymously by LivePerson and stored in browser storage, authenticated identities are provided by your website on each page.
Why is the "Cross-Domain" feature optional for authenticated identities and conversations?
Enabling the Cross-Domain feature is not required for authenticated identities and conversations to persist across different domains, as in that case the consumer's authenticated identity is provided by you on each page, and not completely dependent on browser storage like unauthenticated identities are.
In some cases you still might choose to enable the Cross-Domain feature with authenticated engagements in order to support "Step-Up" flows (unauthenticated "step up" to authenticated), and/or persist other non-identity information across domains.
Since the consumer's identity is provided by you (your website) on each page, and not persisted in browser storage, cross-domain functionality to persist the authenticated identity should work in all supported browsers for LivePerson web messaging (recent versions of Chrome, Edge, Firefox, and Safari).
Read more about how authenticated cross-domain works and browser/OS limitations in the developer documentation: Authenticated cross-domain web messaging