Skip to navigation

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.

Name or patternStorage typePurposeLifetimePersonal data or chat content
ada-messaging-sdk-rollout:<hostname>:randomlocalStorageMoving. Keeps the same random assignment when the loader selects an SDK version.Until cleared.Random rollout value; no end user identifier or chat content.
ada-messaging-sdk-rollout:<hostname>:versionlocalStorageMoving. Records the SDK version selected by the loader.Updated when the loader selects a version; otherwise until cleared.Build identifier only; no personal data or chat content.
ada-rollout-<handle>localStorageMoving. Keeps the display decision consistent when an AI Agent has a partial rollout.Until cleared; written only for a rollout between 0% and 100%.Random rollout value; no end user identifier or chat content.
ada_embed_cross_window_drawer_open_<handle>sessionStorageMoving. Remembers whether the chat window is open during a live agent chat when crossWindowPersistence is enabled.Tab session; removed when live agent chat ends or the SDK clears the saved window state.Open or closed flag only; no personal data or chat content.
ada_embed_cross_window_live_chat_<handle>sessionStorageMoving. Records an active live agent chat when crossWindowPersistence is enabled.Tab session; removed when live agent chat ends or the SDK clears the saved window state.Activity flag only; no personal data or chat content.
ada_proactive_seen_<handle>sessionStorageMoving. Records proactive campaigns already shown during the tab session.Tab session.Campaign IDs only; no end user identifier or chat content.
ada_proactive_seen_user_<handle>localStorageMoving. Prevents a proactive campaign configured for one display per end user from appearing again.Until cleared.Campaign IDs only; no end user identifier or chat content.
ada_proactive_ranked_seen_<handle>localStorageMoving. Records shown campaigns so ranked proactive campaigns advance in order.Until cleared; matching campaign IDs reset after all eligible campaigns have appeared.Campaign IDs only; no end user identifier or chat content.
ada-functional-storage: botAssignmentlocalStorageMoving. Keeps the AI Agent assignment consistent across visits.Until cleared.Agent choices only; no end user identifier or chat content; other existing fields remain.
ada-functional-storage: proactive_conversations_shown, proactive_conversations_shown_userlocalStorage and sessionStorageLegacy only. Shares proactive campaign history with legacy Chat and Embed.localStorage: until cleared, with campaign history updated as campaigns appear; sessionStorage: tab session.Campaign IDs only; no end user identifier or chat content; other existing fields remain.

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.

Name or patternStorage typePurposeLifetimePersonal data or chat content
_dd_slocalStorageGroups reliability events into Datadog monitoring sessions and links them to an anonymous browser identifier.Until cleared; the anonymous browser ID survives session expiration after 15 minutes of inactivity or 4 hours.Random monitoring session and anonymous browser IDs, sampling flags, and timestamps; no authentication credential or chat content.
_dd_sCookieGroups diagnostic logs into Datadog sessions and links them to an anonymous browser identifier when cookies are available.1 year from the last cookie write; the monitoring session expires after 15 minutes of inactivity or 4 hours.Random monitoring session and anonymous browser IDs, sampling flags, and timestamps; no authentication credential or chat content.
_dd_test_<generated ID>localStorageTests whether Datadog can use localStorage.Removed immediately after the test.Temporary random test value; no end user identifier or chat content.
dd_cookie_test_<generated ID>CookieTests whether Datadog can set cookies.Removed immediately after the test; otherwise expires after 1 minute.Fixed test value; no personal data or chat content.
dd_site_test_<generated ID>CookieTests the cookie domain when Datadog diagnoses an unexpected cookie session state.Removed after the test; otherwise expires after 1 second.Fixed test value; no personal data or chat content.
LaunchDarkly_<environment hash>_<context hash>localStorageCaches feature flag values for an AI Agent.Until cleared or removed when LaunchDarkly replaces older cached contexts.Agent configuration and hashed Agent context; no end user identifier or chat content.
LaunchDarkly_<environment hash>_ContextIndexlocalStorageTracks cached Agent contexts so LaunchDarkly can remove older entries.Until cleared; updated when feature flags are cached.Hashed Agent contexts and cache timestamps; no end user identifier or chat content.
pusherTransportTLSlocalStorageCaches the last successful secure connection method when Messaging uses Pusher.Cache validity lasts 30 minutes; the entry remains until replaced, cleared, or removed after a connection failure.Connection method, timing, and retry count; no personal data or chat content.
ada_outage_backofflocalStorageRemembers the connection retry count when the AI Agent’s storage service is not mounted.Removed when the service recovers; otherwise until cleared.Retry count only; no personal data or chat content.
ada:<handle>:<scope>:session:durable-clear-receipt:<mode>:<receipt>sessionStorageRecords a completed session reset so a repeated request does not clear a newer session.Tab session; the high-water receipt updates as requests complete.Generated request IDs or sequence counters; no end user identifier, authentication credential, or chat content.

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.

Name or patternStorage typePurposeLifetimePersonal data or chat content
ada:<handle>:<scope>:sessionlocalStorage or sessionStorageSaves the end user session and language so Messaging can restore the conversation.Until session cleanup; tab session for sessionStorage.End user IDs, session authentication credential, language, and voice-consent conversation IDs; no message bodies.
messagingAuthStatelocalStorage or sessionStorageSaves the access and rotating refresh credentials needed to authenticate the chat session.Until session cleanup or replacement during credential renewal; tab session for sessionStorage.Authentication credentials, end user identifier, expiration time, and refresh counter; no chat content.
chatterlocalStorage or sessionStorageLegacy only. Shares the end user identifier with legacy Chat and Embed to restore the same session.Until session cleanup; tab session for sessionStorage.End user identifier; no message bodies.
sessionTokenlocalStorage or sessionStorageLegacy only. Shares the session authentication credential with legacy Chat and Embed.Until session cleanup or replacement; tab session for sessionStorage.Authentication credential; no chat content.
createdlocalStorage or sessionStorageRecords when the end user session started for retention checks.Until session cleanup; tab session for sessionStorage.Session creation timestamp; no chat content.
messagingCreatedClocklocalStorage or sessionStorageLegacy only. Identifies the time format used for the shared session creation timestamp.Until session cleanup; tab session for sessionStorage.Timestamp and time-format marker; no chat content.
ada:<handle>:<scope>:readlocalStorage or sessionStorageRemembers the last message read in each conversation.Until session cleanup; tab session for sessionStorage.Conversation and message IDs; no message bodies.
ada:<handle>:<scope>:handofflocalStorage or sessionStorageRecords whether a live agent handoff is active or pending.Updated as the handoff changes and removed during session cleanup; tab session for sessionStorage.Activity flag only; no personal data or chat content.
ada:legacy-handoff-observedlocalStorage or sessionStorageLegacy only. Records when Messaging observes a change in legacy live agent activity.Until cleared or updated; tab session for sessionStorage.Activity flag and timestamp; no personal data or chat content.
greetingLeaselocalStorage or sessionStoragePrevents multiple tabs from sending the same greeting at once.Released after the greeting attempt; validity lasts 30 seconds, with stale records removed during later use or cleanup.Hashed end user identifier, random owner ID, and expiration time; no chat content.
ada:<handle>:<scope>:session:pending-resetlocalStorage or sessionStorageKeeps an interrupted session reset pending until the related Zendesk record is cleared.Removed after the reset completes or session cleanup; tab session for sessionStorage.End user identifier or reset-completion flag; no chat content.
ada:<handle>:<scope>:session:zdm-companion-unreconciledsessionStorageRecords that the tab could not check the separate Zendesk Messaging continuity record.Tab session; removed after reconciliation or reset completes.Boolean flag only; no personal data or chat content.
ada:<handle>:<scope>:session:zdm-companion-supersededsessionStoragePrevents the tab from restoring a Zendesk Messaging identity that it has already replaced.Tab session; removed when its saved identity no longer matches or during cleanup.End user identifiers and a generation ID; no message bodies.
ada-user-theme-<handle>localStorage or sessionStorageRemembers the end user’s light, dark, or automatic theme choice.Until cleared or changed; tab session for sessionStorage.Appearance preference only; no end user identifier or chat content.
ada-user-text-size-<handle>localStorage or sessionStorageRemembers the end user’s text size choice.Until cleared or changed; tab session for sessionStorage.Appearance preference only; no end user identifier or chat content.
ada-zd-previous-tags-<handle>localStorage or sessionStorageSaves tags from the last Zendesk Chat handoff so the next handoff can remove them.Until replaced or Zendesk session cleanup; tab session for sessionStorage.Configured tag values, which can include personal data; no message bodies.
ada-zd-session-<handle>localStorage or sessionStorageSaves Zendesk Chat connection details so a live agent chat can resume after a reload.Until Zendesk session cleanup or reset; tab session for sessionStorage.Zendesk visitor and session identifiers, connection cache, and authentication-state markers; no message bodies.
zdMessagingExternalUserIdlocalStoragePreserves the end user identity for anonymous Zendesk Messaging handoffs across visits.Until the handoff ends, the continuity record expires, or reset clears it.End user identifier; no message bodies.
zdMessagingChatterCreatedlocalStorageRecords when the Zendesk Messaging continuity record started for retention checks.Until the handoff ends, the continuity record expires, or reset clears it.Session creation timestamp; no chat content.
zdMessagingGenerationlocalStorageIdentifies the current Zendesk Messaging continuity record so an older tab cannot overwrite it.Replaced on a new continuity save; removed when the handoff ends or reset clears it.Random generation ID; no end user identifier or chat content.
ada_outage_backofflocalStorage or sessionStorageRemembers the connection retry count across reloads while the storage frame is active.Removed when the service recovers; otherwise until cleared or the tab session ends for sessionStorage.Retry count only; no personal data or chat content.
ada:<handle>:<scope>:session:durable-clear-receipt:<mode>:<request ID>localStorage or sessionStorageRecords a completed reset when the asset frame cannot save its sessionStorage receipt.localStorage: until cleared; sessionStorage: tab session.Generated request ID only; no end user identifier, authentication credential, or chat content.
__Host-ada-session-<session ID>-<generation>Cookie, Secure and HttpOnlyStores the rotating session refresh credential in a server-set HttpOnly cookie to authenticate the end user’s chat session.Session, up to 7 days per issued cookie; renewal removes older generations.Authentication credential and session identifier; no chat content.

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.