Overview
LiveAgent is a multi-channel customer support platform that embeds live chat widgets, help desk interfaces, and knowledge base portals on websites. Operators deploy the LiveAgent script to enable real-time chat between site visitors and support agents. The script also tracks visitor sessions and may collect behavioral context to help route conversations and personalize agent responses.
What This Script Does
LiveAgent's embed script loads from a tenant-specific subdomain (e.g., yourcompany.ladesk.com or a custom domain) and renders a chat launcher button. On page load, the script initializes a visitor session and may begin collecting contextual data before the user opens the chat.
Cookies set typically include a visitor session token and a chat widget state cookie, used to maintain session continuity and remember minimized/open widget state. Session cookies are typically short-lived; a persistent visitor identifier may be set with a longer expiry (e.g., 30 days) to recognize returning visitors.
Data collected on page load includes: page URL, referrer, IP address, User-Agent, and session timing. If the visitor initiates a chat, additional data is collected: typed messages, chat transcript, agent responses, and any pre-chat form fields completed (name, email, subject). This data is stored on LiveAgent's servers and visible in the agent console.
Consent & Compliance
LiveAgent's core chat functionality is functional — it delivers a support service that the user actively requests by clicking the chat button. Under GDPR, this can rely on legitimate interest (Article 6(1)(f)) or contract performance (Article 6(1)(b)) for the active chat session itself.
However, if the script sets cookies or collects visitor behavioral data on page load before any user interaction, the ePrivacy Directive's prior consent requirement applies to those activities. A persistent cross-session visitor identifier cookie also requires consent.
Under CCPA/CPRA, chat transcripts and visitor behavioral data collected are personal information subject to disclosure obligations.
Consent category: functional. The primary purpose is delivering an interactive support service, but pre-interaction data collection may require consent.
Should You Block This Without Consent?
Conditional. LiveAgent chat is a functional service delivery tool, and blocking it entirely would prevent users from accessing support. However, if the script sets persistent cookies or collects behavioral data before a user initiates chat, those components require prior consent under ePrivacy. Operators should configure LiveAgent to minimize pre-interaction data collection and set the script to load only after functional consent is granted if cookie writing on page load cannot be disabled.
Is LiveAgent GDPR compliant?
LiveAgent typically loads 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 LiveAgent 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 LiveAgent, not on LiveAgent itself.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
liveagent.comFunctionalliveagent.com is a functional domain operated by LiveAgent, used to run site features like chat, video, embeds, and preferences.
Frequently Asked Questions
Related Vendors
Manage consent for LiveAgent
ConsentStack automatically detects and manages LiveAgent trackers so your site stays compliant with global privacy regulations.