Skip to content
Radioso Docs home
Open app

Visitor data

A conversation records a handful of facts about the visit that started it, so operators can triage abuse, see where traffic comes from, and recognize a returning visitor. This page lists every one of those fields, where it’s visible, and what happens to it.

What gets recorded

Radioso records these once, when a conversation starts, and never overwrites them for that conversation. The time zone is the one fact recorded more than once, on each visitor message:

  • IP address — the address the request came from, resolved from the trusted end of the forwarded-for chain.
  • Country, region, city — read from a geo header the deployment’s load balancer or CDN supplies, when one is present.
  • Browser user agent — the raw User-Agent header.
  • Browser language — the raw Accept-Language header, plus the primary tag Radioso derives from it (de-DE,de;q=0.9 becomes de).
  • Entry page — the page the chat opened on.
  • Referrer — the page that sent the visitor there.
  • Time zone — the IANA zone the visitor’s browser reports, such as America/Los_Angeles, when the browser reports a valid one. Radioso stores it on each visitor message and uses it to date a routine that resumes after an approval click, where no visitor request is live: the routine reads the zone of the visitor’s last message, so “tomorrow” means the visitor’s tomorrow. It never appears in a stored trace or the history API, and it goes when the conversation does.

A durable visitor key — generated by the embed launcher and stored in the host page’s localStorage — links these facts, and every conversation the same browser starts, into one visitor record. See what the widget records. A host-verified customer id from signed visitor identity links conversations the same way and takes over once it appears, ahead of the visitor key.

Where it’s visible

Every field above except the time zone shows up for operators in the Inbox conversation drawer’s Visitor panel — see Operator console. The same fields, including the IP address, are available through the history API to a signed-in workspace session or an eligible personal or service-account credential — see Conversation history.

None of it reaches the model, a prompt, or a stored trace except the six fields behind the visitor_request context variable — country, region, city, language, referrer, and entry page — and even those never carry the IP address or the raw user agent. See Visitor request. The time zone is the one other fact a model reads: when a routine or skill step turns “tomorrow” into a date, its prompt names today’s date and the zone. A stored trace records only whether the zone came from the visitor, the conversation, the workspace setting, or the default, never the zone itself.

Retention

These fields live as long as the conversation that recorded them (the time zone on its messages): until someone deletes it, or until the workspace’s retention window erases it. Deleting the conversation removes them, and deleting the visitor removes the visitor record with every conversation it links — see Deleting conversation data. Deleting a workspace deletes every conversation, and every visitor record, that belongs to it.