What cookies does LivePerson set?

LivePerson sets several persistent cookies: lpLastVisit (up to 1 year), LivePersonID and lpVID (1–2 years) for cross-session visitor recognition and proactive targeting, plus a session cookie (lpSessionID) to maintain active conversations. The persistent cookies require consent in most configurations.

How does ConsentStack manage LivePerson?

ConsentStack treats LivePerson as conditional. The session cookie for active chat is permitted as functional. Persistent visitor identification and behavioral monitoring cookies used for proactive engagement are blocked until consent is granted, aligning your deployment with GDPR and ePrivacy requirements.

What tracker domains does LivePerson use?

ConsentStack has catalogued tracker domains for LivePerson including liveperson.net, lpsnmedia.net and liveperson.com. These are the network destinations LivePerson's scripts contact, which a consent platform blocks until a visitor agrees.

LivePerson - Conversational AI Chat Consent & Privacy

Q: Does LivePerson require cookie consent?

It depends on the deployment. Reactive chat with session-only cookies can be treated as functional without consent. However, proactive engagement rules and persistent visitor identification cookies — which monitor behavior before any interaction — require prior consent under GDPR and ePrivacy.

Back to Vendor Library

Overview

LivePerson is an enterprise-grade conversational AI and digital customer engagement platform used by large retailers, financial services firms, airlines, and telecommunications providers. Its platform combines AI-powered chatbots (through its Conversational Cloud and the Bella AI engine) with live human agent routing, enabling companies to manage customer service conversations across web chat, SMS, WhatsApp, Apple Messages for Business, and other messaging channels from a single platform. LivePerson has been in the conversational commerce space since 1995 and serves Fortune 500 companies globally.

On websites, LivePerson manifests as a messaging widget — typically a chat button or invitation banner — that opens a conversation window for customer support, sales assistance, or automated bot interactions. The widget integrates deeply with the host site's context, reading page-level signals to determine when and how to engage each visitor.

What This Script Does

Script loading: LivePerson loads from lptag.liveperson.net/tag/tag.js?site=[account-id] — a tag management script keyed to the merchant's LivePerson account. A secondary script bundle is loaded asynchronously from lpsnmedia.net or liveengage.com CDN endpoints.

Widget initialization: The tag script initializes the LivePerson Conversational Cloud SDK, which renders the chat widget UI and establishes a WebSocket connection to LivePerson's real-time messaging infrastructure at [account].msg.liveperson.net. WebSocket connections handle real-time message delivery between the visitor and the agent or bot.

Cookies set:

lpLastVisit — First-party persistent cookie, up to 1 year, records the timestamp of the visitor's last interaction with the LivePerson widget for engagement rule evaluation
lpSessionID — First-party session cookie, session duration, maintains the active conversation session and correlates messages within a single engagement
LivePersonID / LPSID-[accountId] — Persistent cookies, 1–2 years, store an anonymized visitor identifier used for conversation continuity across page navigations and multi-session engagement history
lpVID — Visitor ID cookie used for proactive engagement targeting, persists up to 1 year

Behavioral monitoring for proactive engagement: A significant feature of LivePerson is its proactive invitation system. The tag script monitors visitor behavior — pages viewed, time on page, scroll depth, exit intent signals, and referrer sources — to evaluate engagement rules configured in the LivePerson Conversational Cloud. When a visitor matches a rule (e.g., "spent more than 60 seconds on the pricing page"), LivePerson can automatically display an invitation to chat. This behavioral monitoring occurs before the visitor initiates any interaction.

Data transmitted: Conversation content, visitor context (current URL, referrer, pages visited), device information, and engagement metadata are sent to LivePerson's servers for routing, reporting, and AI model training.

Consent & Compliance

LivePerson is categorized as functional.

Core chat (functional): Session cookies (lpSessionID) necessary for maintaining an active conversation qualify for the strictly necessary exemption under ePrivacy — the visitor has explicitly requested the chat service by initiating a conversation.
Proactive engagement and persistent visitor identification: The LivePersonID, lpVID, and lpLastVisit persistent cookies that support cross-session visitor recognition and proactive targeting are not strictly necessary. These require consent under GDPR/ePrivacy, as they monitor visitor behavior and build engagement profiles before any service has been requested.
GDPR: LivePerson offers a DPA and operates as a data processor. Standard Contractual Clauses cover EU-US data transfers.
CCPA/CPRA: Conversation transcripts and behavioral targeting data constitute personal information. LivePerson operates as a service provider; disclosures should appear in the site's privacy policy.

Should You Block This Without Consent?

Conditional. If LivePerson is deployed strictly for reactive support (widget loads only when the user clicks a chat button) with session-only cookies, it can be classified as functional and loaded without a consent gate. If proactive engagement rules and persistent visitor identification cookies are active — which is the default enterprise configuration — the behavioral monitoring components require consent before the tag fires.

Is LivePerson GDPR compliant?

LivePerson typically loads marketing and functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So LivePerson can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads LivePerson, not on LivePerson itself.

Visit website

Consent Categories

Functional

Also Known As

LivePerson chatLivePerson AIconversational AI consententerprise live chat GDPRliveperson widget

Industries

Computers Electronics and TechnologyProgramming and Developer SoftwareBusiness and Consumer ServicesMarketing and Advertising

Tracked Domains (3)

LivePerson's trackers are rarely seen, seen on under 1% of the sites ConsentStack has scanned. Scan your own site to see which of these are firing before consent.

liveperson.netMarketing

liveperson.net is a marketing domain operated by LivePerson, used to serve ads, build audiences, and measure ad conversions. Seen on under 1% of scanned sites.

lpsnmedia.netMarketing

lpsnmedia.net is a marketing domain operated by LivePerson, used to serve ads, build audiences, and measure ad conversions. Seen on under 1% of scanned sites.

liveperson.comFunctional

liveperson.com is a functional domain operated by LivePerson, used to run site features like chat, video, embeds, and preferences. Seen on a small share of scanned sites.