Visitors' conversations
Read what visitors asked a widget, with the answers, their sources and the visitors' thumbs up or down, for 90 days.
Open the widget’s Logs tab to see this month’s figures and the latest conversations, newest first, with the thumbs up and down. Links in the tab open the Logs page filtered on the widget: Conversations, Answers and Changes. In Conversations you read each one, with the number of questions, the thumbs and the credits it used. A thumbs down can come with a few words from the visitor about what was wrong: open the conversation to read them.
- Visitors are anonymous. Each one shows as a short random identifier (
end_userin the API), the same for every conversation from the same browser. - With Visitors’ chat history on (the default), a visitor who comes back finds their conversations where they left them, on the same browser.
- Conversations are kept 90 days after their last message, then deleted.
- Questions asked in the app’s preview (the designer) are not listed.
- Visitors can leave thumbs only when Thumbs up and down is on in the widget’s Config tab (
settings.feedback). - Deleting the widget deletes its conversations. What they cost stays in your usage.
What visitors see and what you see
| Visitors | You, in Logs | |
|---|---|---|
| History on | A Past chats list in the chat, with the conversations they had on this browser, which they can reopen. | Every conversation, 90 days, with the answers, sources, costs and thumbs. |
| History off | Every visit starts fresh. The current conversation is not remembered. A widget-specific proof remains for limits, but Lookio refuses history reads while this option is off. | The same list as before: the setting only changes what visitors can reopen. |
The setting is Visitors’ chat history in the widget’s Config tab (settings.visitor_history in the API).
Turning history back on makes retained conversations available again on the same browser, as long as its proof is still valid. This does not restore expired or deleted conversations. Turning feedback off also keeps existing ratings and comments. Apply these changes with Save preferences.
How the history stays private:
- The browser keeps a signed resumption proof for its random visitor identifier in the chat frame’s own storage, not in your page. It is partitioned per site, and never shared with the site that hosts the widget, so your page cannot read it.
- A visitor needs that proof to reopen the conversations of their identifier. They cannot reach another visitor’s.
- The identifier is the short visitor id you see in Logs. It identifies a browser, not a person.
The same conversations are available from the API (GET /v1/widgets/{widget_id}/conversations), the CLI and the MCP. They are the workspace’s logs filtered on the widget: GET /v1/logs/conversations?widget_id=...&rating=down lists the conversations where visitors were not satisfied, across your widgets, API keys and the MCP.