Appearance
Builder — Listeners
The Listeners button in the builder's left icon rail controls what an agent pays attention to while a shopper browses your site. It opens a dialog with one checkbox, Use page views to personalize. Tick it to let that agent reference the pages the shopper visited before they opened the chat.
Listeners is available only to accounts that have page view capture turned on.
Screenshotthe builder left icon rail with the Listeners dialog open, showing the "Use page views to personalize" checkbox
Two settings, two different jobs
Personalizing on browsing history takes two separate settings, and they do different things.
- Page view capture, in Settings → Consent, decides whether a shopper's journey is recorded at all. It covers every agent in your organization, and it is off by default.
- Use page views to personalize, in the Listeners dialog, decides only whether that one agent uses the journey in its replies.
| Page view capture | Chat on the page | Use page views to personalize | Journey recorded | Agent personalizes |
|---|---|---|---|---|
| Off | — | — | No | No |
| On | None | — | Yes | Not applicable |
| On | Present | On | Yes | Yes |
| On | Present | Off | Yes | No |
An agent with Use page views to personalize switched off still has the shopper's journey recorded for your organization. That agent simply does not use it.
Nothing carries over between the two
Turning Page view capture on in Settings does not switch any agent on. Each agent is opt-in and starts off. Open every agent that should personalize and tick the box yourself. The reverse holds too: ticking the box on one agent changes nothing for your organization or for your other agents.
While Page view capture is off, the per-agent checkbox is greyed out, and the dialog tells you why.
What gets stored
The shopper's most recent paths on your site — up to 10 of them — are kept in that shopper's own browser, under your organization. A shopper who comes back later carries on the same journey. If the shopper withdraws consent, it is cleared.
Capture also needs the current install snippet on your site. See Publish & Deploy.