Skip to navigation

Overview

Configure how Messaging retains conversation state and which link protocols it permits.

Limitations

Only Owners and Admins see the Data & privacy tab.

Messaging evaluates configured persistence when a page loads or refreshes. An open page does not continuously expire its conversation.

Persistence controls browser state. They do not replace your organization’s data-retention or Redactions settings.

Capabilities & configuration

Select a persistence setting for Messaging under Data & privacy.

SettingBehavior
Never ForgetRetain conversation history and variables across visits, subject to browser storage availability.
Forget After Tab CloseRetain state across same-tab refreshes. Clear it when the tab closes.
Forget After ReloadStart again after a reload, except during an active human support session.
Forget After…Apply the configured duration when the page next loads or refreshes.

During an active human support session, Forget After Reload retains the session in tab storage. A same-tab refresh returns to the same conversation.

That exception ends when the human support session ends or the tab closes. It applies across Messaging’s live agent integrations.

The SDK’s privateMode setting stores no session state. It does not provide the same handoff-refresh exception as Forget After Reload.

Enable IP tracking under Privacy to log each end user’s IP address in conversation metadata. Changes save automatically.

Implementation & usage

Non-custom persistence changes save automatically.

Test Messaging persistence with the human support integrations and identity flow you use.

To configure data controls:

  1. Open Config > Channels > Messaging > Data & privacy.
  2. Select the required Persistence setting.
  3. Set the duration if you select Forget After….
  4. For a custom duration, click Save.
  5. Add any required custom URI schemes under Approved link protocols.
  6. Test refresh, tab closure, sign-out, and account switching.

Use the SDK persistence reference and reporting differences for integration-specific behavior.

Read Personalization and identity before you add signed-in users or cross-device conversation access.