Browser storage
The Messaging Web SDK uses cookies and Web Storage to restore sessions, remember preferences, and monitor reliability. This page lists entries that the SDK and its bundled libraries write, grouped by the origin that stores them. Entries depend on your configuration, enabled integrations, and browser storage permissions.
The SDK writes the entries marked Legacy only and Moving today, even when the site does not run legacy Chat or Embed. This keeps Messaging working alongside legacy Chat and Embed while customers transition.
After legacy Chat and Embed retire, Messaging will remove the Legacy only entries. It will no longer store anything on your site’s domain. It will keep Moving data on the AI Agent’s domain or stop storing it, with no change for end users.
In the tables, <handle> identifies your AI Agent, and <hostname> identifies the page that loads the SDK.
<scope> is origin:<API origin>, cluster:<cluster domain>, or default.
Other placeholders identify generated values, such as a request ID or a cache hash.
sessionStorage lasts for the browser tab’s session and survives page reloads.
localStorage has no automatic expiration; it remains until the SDK or browser removes it, or someone clears it.
A value can stop being valid before the browser removes its storage entry.
The data column describes stored values, including identifiers and authentication credentials.
Your page
Every entry that Messaging writes on your page has a Legacy only or Moving label. The loader and SDK write these entries on your page’s origin. These entries support version selection, launch settings, proactive campaigns, and live agent chat. For iframe-only embeds, the SDK runs on the asset origin, so any SDK storage belongs there.
In ada-functional-storage, localStorage holds botAssignment, proactive_conversations_shown, and proactive_conversations_shown_user fields keyed by handle.
The sessionStorage entry holds proactive_conversations_shown for the tab session.
Messaging writes these fields directly and does not use the @ada-support/web-storage package.
The SDK reads the optional ada.debug localStorage entry but does not create it.
Support debugging requires someone to set this entry manually.
Messaging asset host
Ada hosts the conversation runtime, chat interface, introduction, button, and integration frames on static.ada.support or messaging-assets.ada.support.
Their storage belongs to that asset origin.
The chat interface saves appearance preferences through the AI Agent’s storage frame, as listed in the next section.
For reset receipts, <mode> is normal or session.
<receipt> is high-water for sequenced requests or a generated request ID for older clients.
Datadog monitoring starts with tracking consent set to not-granted.
The SDK grants tracking after end user engagement, or before engagement for a random 1% sample of loads.
This internal tracking state does not represent a response to your website’s consent banner.
Datadog can write its temporary storage probes during initialization, before tracking starts.
RUM uses localStorage for _dd_s; the diagnostic logging library separately uses a cookie.
The RUM configuration does not fall back to cookies when localStorage is blocked.
The SDK disables Datadog session replay and does not enable stored user or global monitoring contexts.
Its Sentry configuration adds no cookies or Web Storage entries.
Standalone survey monitoring uses memory only.
Zendesk Chat redirects its __zlcmid, __zlcstore, and __zlcid values into ada-zd-session-<handle> on the AI Agent’s domain.
It does not create separate entries with those names on the asset origin.
AI Agent domain
The storage frame uses your AI Agent’s Ada domain, such as <handle>.ada.support, including the equivalent domain for your region.
The SDK uses localStorage in normal persistence mode and sessionStorage in session mode.
Web sessions started with an identity token use sessionStorage instead of normal localStorage persistence.
The dashboard’s Forget After Reload setting permits sessionStorage during a live agent handoff and clears that saved session when the handoff ends.
The SDK’s privateMode setting disables conversation persistence in Web Storage.
Zendesk Messaging can keep a separate localStorage record for anonymous handoff continuity, even when the main session uses sessionStorage.
These settings govern conversation persistence, not the host-page or monitoring entries above.
In this table, session cleanup means the SDK clears the saved session during a reset, identity change, or an expiration check. The configured retention period controls session reuse; it does not create a browser expiration timer for localStorage. An active live agent handoff can keep a session eligible for reuse.
The session cookie belongs to the AI Agent’s domain and is partitioned by the browser’s top-level site. JavaScript cannot read this HttpOnly cookie.
Out of scope
Native iOS, Android, and React Native SDK storage is outside this browser inventory, including storage used only inside their WebViews. See the existing browser storage list for legacy Chat and Embed. Custom apps and external media providers can set their own storage, which their providers document separately.