The visitor journey

Every conversation comes with a backstory. Before a customer types a word, they arrived from somewhere, on some device, and browsed a few pages. Vivollo captures that journey quietly in the background and shows it in the context panel, so whoever picks up the chat — human or AI — already understands the situation.

Crucially, all of this is gathered with privacy by design: the useful context is kept, the sensitive raw data is not.

What gets captured

When a visitor starts chatting, Vivollo notes a handful of helpful things:

• Device — their browser, operating system, and whether they're on a phone, tablet, or desktop. (A customer struggling on mobile is a different conversation than one on a big screen.)
• Location — country, region, city, and timezone. Enough to be helpful with shipping or store hours, never more.
• Traffic source — how they found you: the campaign, medium, or referring site, when that information is available. You can tell an ad click from a returning bookmark.
• Returning visitor — whether you've seen them before, and how many times.

The pages they browsed

Vivollo also records the pages a visitor viewed, with how long they spent on each. This turns a vague question into an obvious one: when someone asks "is this available?" right after sitting on a product page for two minutes, you (and the agent) know exactly what "this" means.

You'll see this two ways in the workspace:

• In the thread — page views are woven into the conversation at the moment they happened, so the browsing and the chat read as one story.
• In the timeline — a complete, chronological feed of the visitor's whole session: every page, and when each conversation began.

Their other conversations

People come back. When a visitor has chatted before, the workspace links to their related conversations, so a follow-up isn't a cold start. Your team can glance at what was discussed last week instead of asking the customer to recap.

Privacy, by design

Helpfulness and respect aren't in tension here — Vivollo is built so you get the context without holding sensitive data you don't need:

• No raw IP address is ever stored. Location comes from Cloudflare's edge-derived geography (country, region, city), not from keeping the visitor's IP.
• Sensitive bits in page links are stripped before anything is saved, so a password or token that happened to be in a URL never lands in your records.
• A "forget this visitor" action wipes a person's captured journey — their pages, traffic data, and custom attributes — when they ask to be forgotten or your policy requires it. The conversation history itself is kept for your records, but the personal trail is erased.

This is what lets Vivollo be genuinely useful with visitor context while staying on the right side of KVKK and GDPR.

Next

• See where this appears for your team → The inbox
• Store your own custom attributes on a visitor or chat → Metafields
• Understand how the agent uses this context → Agentic AI