Zendesk

Overview

Zendesk is a customer support platform providing helpdesk ticketing, live chat, messaging, and self-service knowledge base tools. The Zendesk Web Widget (Classic and Messaging variants) embeds a customizable support interface on websites, allowing visitors to search help articles, initiate live chat, send support tickets, and access bot-driven conversational support.

What This Script Does

Web Widget (Classic) The Classic Web Widget loads from static.zdassets.com and renders a floating support button and panel on the page. On initialization it:

• Contacts {subdomain}.zendesk.com to fetch widget configuration including available channels, hours of operation, and help center content
• Loads the help center search interface, which queries {subdomain}.zendesk.com/api/v2/help_center/ for article results
• Renders the contact form or live chat interface depending on agent availability
• Sets cookies to persist the active chat session so conversations survive page navigation

Cookies set by the Classic Widget:

• __zlcmid (first-party, 1 year) — Zendesk Live Chat messaging ID, uniquely identifies the visitor for conversation continuity
• zdVisitorId (first-party, 1 year) — Zendesk visitor identifier for matching returning visitors to previous support tickets
• ZD-suid (first-party, session) — Zendesk session unique identifier
• ZD-store (first-party, session) — widget state storage

Web Widget (Messaging) The Messaging variant (powered by Sunshine Conversations) loads a more modern conversational interface. It uses:

• localStorage to persist conversation history and user identity between sessions
• A WebSocket connection to {subdomain}.zendesk.com for real-time messaging
• messenger.zendesk.com for asset delivery

Live Chat Data Collection When a visitor initiates a chat:

• The pre-chat form collects name and email address (if configured by the site operator)
• Chat transcript content is stored in the Zendesk account
• Visitor information logged: IP address, User-Agent, page URL at chat initiation, referrer, browser language
• Agent routing decisions use tag-based logic configured by the site operator

Help Center Search Article search queries sent via the Widget are logged to Zendesk's analytics. Search terms, articles viewed, and article helpfulness ratings are recorded for knowledge base optimization reporting in the Zendesk Guide analytics dashboard.

Script filenames loaded: web_widget bundle from static.zdassets.com Domains contacted: static.zdassets.com, {subdomain}.zendesk.com, {subdomain}.zopim.com (legacy Live Chat), ekr.zdassets.com (consent integration)

Consent & Compliance

GDPR/ePrivacy: The Zendesk Web Widget serves a legitimate customer support function. Session cookies used to maintain an active chat conversation (ZD-suid) are functional and fall under the ePrivacy strictly necessary exemption — they persist a user-initiated transaction (a support conversation). However, the persistent visitor identifier cookies __zlcmid and zdVisitorId (both 1-year duration) are not strictly necessary for completing a single session and may require consent as non-essential functional cookies. Data collected through support interactions (name, email, chat content) must be disclosed in the privacy policy and covered by a lawful processing basis — typically the visitor's explicit consent via the pre-chat form, or legitimate interest in providing the requested support.

CCPA/CPRA: Data collected through Zendesk support interactions — contact information, chat transcripts, browsing context — constitutes personal information that must be disclosed. Zendesk acts as a service provider under CCPA when operating under a data processing agreement.

EU-US Data Transfers: Zendesk Inc. participates in the EU-US Data Privacy Framework (DPF) and offers Standard Contractual Clauses for EU-US data transfers.

Consent category: Functional (live chat support and help center).

Should You Block This Without Consent?

No. The Zendesk Web Widget provides customer support functionality that directly benefits site visitors. Session cookies maintaining an in-progress chat are strictly necessary for that conversation. Disclose Zendesk in the site's privacy policy and ensure the pre-chat form clearly explains data collection. The persistent visitor identifier cookies (__zlcmid, zdVisitorId) could be debated as requiring consent — operators with strict interpretations should review these against their privacy policy commitments and local regulatory guidance.