Visitors
Visitors shows everyone who has been on your website: where they came from, which pages they read, and — once they write, fill in a form or send you a WhatsApp message — who they turned out to be.
The Visitors pages need the View visitor intelligence permission (visitors.view),
which admins and supervisors have by default; you can give it to any role in
Settings → Roles. Linking a visitor to a person also needs the right to
edit that contact.
What gets recorded
Visitors are recorded on a website that runs the ConnectWiz chat widget and is connected with Capture with the chat widget code on, and with Record visits that come from an ad, a campaign link or another site switched on. Then, for every page:
| Recorded | Not recorded |
|---|---|
The page address (ad click ids such as gclid removed), its title | The visitor's IP address or browser string for the page journey |
| When the page was opened and how long it was visible | Anything the visitor types on your pages |
| The other site the visitor came from (its host only) | Pages on domains that are not your site's |
| Whether the page reported analytics or ads consent |
The page journey is sent when a page is hidden or left — not on every click — and also follows single-page apps that change the address without reloading.
The chat widget itself follows the same consent:
| Without analytics or ads consent | With it | |
|---|---|---|
| The visitor row (its chat id, first and last seen, a visit counter, the person once they write) | Kept — the chat needs it to recognise a returning browser and continue its conversation | Kept |
| IP address, browser (user agent), country | Not stored | Kept with the visitor and each visit |
| A log of the pages the chat opened on (Chat widget loads) | Not stored | Kept |
| The campaign of the page (utm) | Kept as an anonymous source, not linked to the visitor | Kept with the visitor |
Ad click ids (gclid, fbclid…) | Not stored | Kept with ads consent |
So for a visitor without consent the device, country and IP fields stay empty. When they write in the chat, their conversation works as always; the privacy notice's own record (who accepted which text, when) is kept as the evidence of that act.
Consent decides how far the journey reaches
ConnectWiz follows the consent your site's cookie banner reports (Google
Consent Mode, or window.cwConsent):
- With analytics or ads consent, every visit of the same browser lands on one visitor. With ads consent the ad click ids are kept too (see Connect your website).
- Without consent, the journey of that visit is kept on its own — the list shows it as an anonymous visitor marked This visit only. It is joined to the person only if they identify themselves in the same visit: they write in the chat, submit a form of your site, or send the WhatsApp code your site gave them.
Page journeys reported with consent are kept for 13 months, like the sources; page journeys without consent for 30 days. Both are deleted with the person when you erase a contact.
The list
Each row shows the visitor (the person's name once identified), their first
source / medium (for example google / cpc), campaign, landing
page, how many pages they read, and when they were last seen. The source is
worked out exactly as on Leads: the link's utm_source, else the
ad network, else the ad click id's network, else the referring site.
Filter by identified or anonymous, by source and campaign (the lists show the values your visitors actually have), by last seen dates, or search for a person's name, e-mail or phone, or a part of the landing page.
One visitor
Open a row to see the visitor's lifecycle:
- Where they came from — the first touch and, if different, the last one: source, medium, campaign, the ad, which ad click id it carried, and the site they came from. The first touch is never replaced by a later one.
- Pages visited — grouped by visit, in order, each with its title, time and time on page.
- Person — the contact they are linked to and how the link was made, the device (browser, system, phone or computer) and country.
- What they did — their conversations, website form submissions and ad leads, each opening where it lives, and a shortcut to the person in Leads.
Linking a visitor to a person
Visitors are linked automatically when they:
- write in the chat,
- submit one of your website's forms, or
- send the WhatsApp code your site added to the message.
From then on their visits, and the ad that first brought them, belong to the contact — even when the ad visit was days earlier.
You can also link by hand: open the visitor, choose Link to a person, then search for the contact or create a new one. The link is recorded in the audit log. Unlink undoes it: the visits it brought go back to anonymous, the person's first source is worked out again, and the automatic paths will not link this visitor to that person again (you still can, by hand).
When you merge two contacts, their visitors move to the contact that remains.