Getting website visitors to Salesforce is usually framed as an integration task. The connector takes an afternoon. The part that decides whether the project is useful or a mess is what a company visit is allowed to create inside your CRM: which object, under which account, owned by whom, and what happens when the same domain arrives twice.
Route website visitors to Salesforce without written rules and three problems appear: duplicate accounts for one company, contacts invented so a visit has somewhere to sit, and a task queue that fills faster than anyone reads it.
This guide is the rule set worth writing before you switch delivery on. It assumes Reveal for company identification and Automate for delivery, and it focuses on the object model, match keys, owner assignment and dedupe.
What a company visit actually gives you
Reveal names the company behind a visit when the visit arrives from that company’s own network, and returns a confidence level with the evidence behind the match. Visits from home broadband, mobile carriers, hosting providers and VPN exits stay anonymous. People are linked only from first-party data you already hold — form fills, logins, CRM imports — with a consent record attached.
That boundary should shape the routing. A visit is an account-level signal, not a person. If your design assumes every visit produces a Contact, you will either fabricate people or drop the signal. Keep one flow for companies and a separate flow for people.
Choose the match keys before the first delivery
Use three keys, in this order:

- Normalized company domain. Lowercase, strip
www, strip trailing dots, drop paths and query strings. Primary key for the Account and for the visit. - Salesforce Account ID, stored back on the Reveal side once a match exists, so the next visit does not re-match from scratch.
- Email domain of an existing Contact, only as a fallback when the Account has no website.
Never match on account name alone. “Acme”, “Acme Inc.” and “Acme Holdings” are three strings and often one company. Reps edit names; domains mostly stay put.
Stop free-mail and ISP domains at the door
Keep an explicit list of consumer mailbox and ISP domains and reject them before matching. A visit whose only domain evidence is a consumer provider is not an account, and creating one pollutes reporting permanently.
Handle the three dedupe cases
- One exact Account match. Attach the visit as a record. Never overwrite fields a rep owns.
- Domain on a Contact, no Account. Create the Account, attach the Contact, then attach the visit.
- Domain on two or more Accounts. Normal after mergers and inside enterprise hierarchies. Do not guess: send the visit to a review queue with a named owner and leave both accounts alone.
Map visits to accounts, owners and tasks
Store each visit as its own record instead of overwriting the Account. You keep history, and a bad match is deleted in one place.
| Reveal signal | Salesforce destination |
|---|---|
| Company name and domain | Account.Name, Account.Website — on create only |
| Confidence and evidence | Visit record |
| Intent score and hot pages | Visit record; latest score mirrored to the Account |
| ICP fit and segment | Account fields, read-only for reps |
| Playbook matched | Task subject prefix and the Visit record |
Owner assignment follows a fixed order: existing Account owner, then a named owner on the account team, then territory or round-robin, then a fallback owner who actually works the queue. The integration must never reassign an owner a person set by hand.
Tasks are where most implementations drift. Create a Task only when a playbook condition is satisfied — ICP fit true, a page from your named list seen, no open task of the same type on that account. Otherwise the visit stays a record and nobody gets an email.
Keep company and people signals in separate flows
Two flows, two responsibilities:

- Company flow: visit → Account (matched or created) → Visit record → optional Task. No Contact.
- Person flow: form fill or login with consent → Contact under the matched Account, consent field filled.
on company_identified(visit):
key = normalize(visit.domain)
if key in blocklist: drop
account = match_account(key)
if account is null: account = create_account(visit, owner=route(key))
record_visit(account, visit.confidence, visit.intent, visit.hot_pages)
if playbook.matches(visit) and no_open_task(account, playbook):
create_task(account, subject="Prynt: " + playbook.name, owner=account.owner)
Watch the queue before you let it write
Run delivery with create permissions off and review what would have been created. Count how many visits matched exactly one Account, how many hit the review queue, and whether the blocklist caught consumer domains. Enable creation once the queue is nearly empty and reps agree with the owner mapping. The /accuracy page explains how confidence and evidence are produced, and /docs covers delivery setup.
Privacy belongs in the record, not in a wiki. Company-level identification from network evidence and person-level identification from first-party data are different permissions: keep the consent reference on the Contact, check opt-out and suppression lists before delivery, and keep company evidence on the Visit record. The /legal/reveal-privacy-notice page describes what Reveal processes. This is not legal advice.
FAQ

Does Reveal create Leads or Contacts in Salesforce?
Neither by default. Company visits map to Accounts and Visit records; Contacts come only from first-party data with a consent record. Decide explicitly whether your team wants leads at all.
What happens to visits from VPNs, home offices and mobile networks?
They stay anonymous. You still see the session, but Reveal will not name a company it cannot evidence, so nothing is written to Salesforce.
How much does this cost?
Reveal Free covers 100 companies per month with 7-day history. Starter is $49/month (250 companies, 30 days, 14-day trial), Growth $129/month (600 companies, 2 sites, 90 days), Scale $299/month (2,000 companies, 5 sites, 365 days), Enterprise from $799/month. Automate, if you need branching and retries, is $39 per 1,000 executions.
Try it free
Start on the free plan, connect one site, and let the review queue tell you whether your match keys are right before you enable writes. Create your account at pryntid.com.
Try it free
Prynt is device intelligence with a free plan: 5,000 identifications a month, visitor IDs with confidence and bot detection — no credit card. Upgrade to Pro for VPN, proxy, tampering and behavioral signals.