Visitor context without turning live chat into surveillance

Visitor context is useful right up to the point where it becomes creepy. Operators need to know enough to avoid asking obvious questions. Visitors should not feel that opening a chat window creates a permanent dossier. Convor keeps the context close to the conversation: current page, recent messages, declared contact details, useful tags, and consent state.

Continuity is not full identity

A visitor should be able to refresh the page and continue the same conversation. That does not mean the product knows who the person is. Convor uses a technical visitor record and token flow for continuity. If the visitor later provides an email or fills a form, that becomes explicit context. Until then, the system should not pretend it has a complete customer profile.

The current page often explains the question

A message like does this include integrations means something different on a pricing page than inside API documentation. The widget forwards host page navigation into the iframe so Convor can use the real customer-site URL for triggers and operator context. That context helps, but it should stay proportional. Page data belongs in the support workflow, not in a hidden analytics product bolted onto chat.

UTM data is attribution context

Campaign parameters can help support and sales teams understand why a visitor arrived. A launch campaign, a paid ad, or an onboarding email gives useful background. It does not justify collecting every browser signal. Convor extracts standard UTM fields as support context and keeps that scope predictable.

Consent has to change behavior

Consent is not meaningful if refusal changes nothing. Visitor consent routes and settings exist so the product can record and respect choices. Depending on the setup, consent can affect optional tracking, proactive triggers, retention, or what context appears to operators. A privacy policy page is not enough if the widget and API ignore the decision.

The dashboard should summarize context, not bury the operator in it. If a field does not help someone answer better, it probably should not be in the default view.