Website Visitors associates some site visits with a company after its tracking script is installed. A company match does not identify the individual visitor or prove buying intent. Review the visit and its source before deciding what to do next.
What can a team review?
Open Website Visitors and review the matched company’s domain, visit date, pages viewed, and source. Reject a false match and note when the information was recorded. Page and visit details add context for research; they do not establish who visited or why.
If the company is relevant, assign an owner, save it to a named list, or create a CRM task using the available action. Website Visitors can also send a Slack notification when a visit matches a saved filter.
How does it fit the sales workflow?
Signals -> Leads -> Enrichment -> Decision -> Outreach -> Pipeline
- Signals: Review the recorded visit, pages, source, and date.
- Leads: Check whether the company match is plausible; a matched company is not an identified person.
- Enrichment: Add relevant company or contact context only after checking its source and match.
- Decision: Assess fit, recency, contact restrictions, and suppression.
- Outreach: Contact someone only when applicable rules allow it. A visit should not trigger an automatic message by itself.
- Pipeline: Assign an owner and preserve the source and next action in CRM.
Before installing the script or routing visitor information to Slack, review notice, consent, access, retention, and the intended use. See the Website Visitors setup guide, Slack alert instructions, and visitor-tracking privacy checklist.
