Website
Who is on your site, and who they turn out to be
Sessions, pages, identified visitors and intent, on the records they belong to.
Install the snippet and the page fills with who is on your site and what they looked at. The interesting moment is when an anonymous visitor becomes a person you already know, and every past session attaches to their record.
The page
- Visitors
- Identified and anonymous, with the company when it can be resolved.
- Sessions
- Per visitor: pages, time on page, referrer, the campaign they came from.
- Events
- Form submissions, chat starts, clicks on tracked links.
- Intent
- Pricing views, docs deep-dives, repeat visits, surfaced as signals worth acting on.
How a visitor is identified
- They submit a form, or start a chat and share an email.
- They click a tracked link in an email you sent.
- Your site calls identify when they sign in.
- From then on, their sessions, past and future, are on their record under Website.
What to do with it
A deal page can then say they visited pricing yesterday. A workflow can create a task when a known contact hits pricing twice in a week. The brief mentions it. The assistant can list every identified visitor from a target account this month.
Around website
The parts of the workspace this one works with.
Website tracking
One snippet on your site. Then sessions, pages, identified visitors and intent, on the records they belong to.
Install the snippet and the Website visitors page fills with who is on your site and what they looked at. Identify a visitor once and every past session attaches to their record.
Website chat
Live chat on your site, wired into the Inbox and the helpdesk. Identified visitors link to their record.
Visitor conversations land in the Inbox in real time, on a lane of their own. A visitor who shares an email links to their person record, so the chat sits on the same page as everything else you know about them. Turn on ticket creation and nothing is dropped after hours.
Google Ads
Campaign performance, search terms, keywords and negatives, and the funnel from click to customer, next to the pipeline it produced.
Ads spend is only interesting next to what it produced. Connect Google Ads and the Ads tab in Reports shows campaigns, search terms and the funnel from impression to paying customer, with the pipeline attributed to it.
Questions
Does it identify people by IP?+
It resolves companies from the network when possible. People are identified only by something they did: a form, a chat, a link, a sign-in.
Where does the data live?+
In your workspace, on the records. Nothing is sold or shared.
Does it slow the site down?+
The script is small and loads after the page. Events are batched.
Is this a cookie banner problem?+
It sets a first-party identifier. Whether your site needs consent for that depends on where your visitors are; the snippet can be loaded after consent.
Can the assistant answer first?+
A routing rule can hand the first reply to the assistant with a skill, and a human takes over when it hands off.
Does it work with our existing chat tool?+
It replaces it. One widget, one inbox.
Does it change my campaigns on its own?+
No. Reading is automatic. Changes only happen when you ask.
MCC accounts?+
Yes. Connect the manager account and pick the client accounts.
Try website on your own data
Connect your email, then open a person. Most of the product shows up on that one page once the mail is in.
More in Measure
The daily brief, reports, goals, website visitors and money.
What is overdue, who is waiting, what has gone quiet, and what is on the calendar. Written before you open it.
Pipeline, revenue, outreach, calls, templates, sequences, rep leaderboards, engagement, and the tabs you build yourself.
Pin a target to a metric, per user, team or workspace. Attainment computes itself.
Receipts read on their own. Invoices that are legally yours. Both reconciled against the bank.