What to Do With a Deanonymized Visitor: The Playbook

Installing a deanonymization tool is the easy part. Within a day of dropping the tracking script, your dashboard fills with company names, and the real question arrives: now what? A list of identified accounts is not pipeline. Most teams that buy Warmly or RB2B stall here, treating the dashboard as a report to skim rather than a queue to work. This playbook is the workflow that turns an identified visitor into a routed, contacted, tracked opportunity, in five steps.

Why does acting on a deanonymized visitor matter so much?

Because the signal is perishable. A deanonymized visitor is a snapshot of intent captured while the person was on your site; the moment they leave, that intent starts to cool. The value is not in knowing a company looked, it is in reaching the right person while the problem that brought them is still top of mind. Treat identification as the start of a countdown, not the finish line.

The five-step playbook

Every identified visitor should pass through the same five gates in order. The first three are automated; the last two are where a human earns their time.

1. Qualify against your ICP. Filter, then route.
2. Enrich the record. Turn a company name into a contactable person.
3. Route to an owner in under five minutes. Alert plus CRM assignment.
4. Trigger the right outreach. Matched to the page they viewed.
5. Log and nurture the rest. Not everyone is ready today.

Step 1: Qualify against your ICP

A deanonymization tool identifies far more companies than you should ever contact. The first move is a fit-and-intent filter, not an SDR task. Score each identified account against your ideal customer profile, and gate on two things: does the company clear your firmographic floor, and did the visit show real intent (a pricing, demo, integrations, or product page, not a single blog read)? Only accounts that clear both go to a human. This is where a pain-first model earns its keep, described in our pain-first ICP scoring framework.

Step 2: Enrich the record

A company name is not contactable. Enrichment turns "Acme Corp viewed pricing" into a named VP of Sales with a verified email and a LinkedIn profile. Person-level tools like RB2B do some of this at the point of identification; for company-level matches, an enrichment provider fills in the buying-committee contacts you actually want to reach. The output of this step is a routable record, not a mystery.

Step 3: Route to an owner in under five minutes

Speed is the difference between a signal and a missed opportunity. The identified, enriched, ICP-cleared visitor should hit the right owner automatically: a Slack alert to the assigned rep and a CRM record created with the correct pipeline, stage, and owner, within seconds. If a human has to notice the dashboard, open it, and decide, you have already lost the window. This is the same discipline as inbound speed-to-lead: the routing is wired, not remembered.

Step 4: Trigger the right outreach

Match the touch to the evidence. A person-level match with a pricing-page view supports a personalized 1:1 email that references the specific problem the page addresses. A company-level-only match supports account-based outreach to the right persona, not a message blasted at a guessed inbox. Never fire a generic sequence on a deanonymized signal: the whole advantage of the signal is context, and a template throws it away.

Step 5: Log and nurture the rest

Most identified visitors are not ready to buy today, and that is fine. An account that cleared ICP but showed only light intent goes into a nurture track, not the cold-outreach queue. Log the visit as a data point, add the account to a retargeting or content nurture, and let repeat high-intent visits promote it back into the active queue. The goal is a system that escalates on evidence, not one that burns every name once and forgets it.

Person-level or company-level: does it change the play?

Yes, at steps 2 and 4. Person-level identification hands you a named individual, which unlocks a direct, personalized touch. Company-level identification tells you the account is in-market but leaves the "who" open, so you enrich for the buying-committee persona and run account-based outreach instead. For the privacy and coverage differences between the two, see person-level vs company-level identification. The table below maps the signal type to the right motion.

What are the most common mistakes?

The failure modes are predictable, and all of them come from skipping a step.

• Working the whole dashboard. Contacting every identified account ignores step 1 and buries reps in low-fit noise.
• Firing a generic sequence. A template on a deanonymized signal throws away the context that made the signal valuable.
• Manual routing. If a person has to check the dashboard, the five-minute window is already gone.
• No nurture path. Burning every name once with cold outreach wastes the accounts that would have converted on the third visit.

Where Artemis fits

Artemis GTM does not sell a data vendor; it wires the workflow this playbook describes on top of whichever tool fits your traffic. The Visitor Deanonymization agent ($349) installs the identification tool, tunes the ICP filters, and builds the enrichment, Slack alert, and CRM routing so an identified high-intent visitor reaches the right owner in seconds instead of sitting in a dashboard. It turns identification into a motion.

Related reading: how website visitor identification works explains the matching under the hood, and the B2B visitor identification tools comparison helps you pick the tool that produces the signal in the first place.

Frequently asked questions

Sources & references

• Oldroyd, McElheran & Elkington, "The Short Life of Online Sales Leads," Harvard Business Review (2011): the lead-response research on how sharply the odds of qualifying a lead fall as the minutes pass, the empirical case for routing a deanonymized visitor immediately.
• Gartner Sales Survey (reported by Demand Gen Report): finds 61% of B2B buyers prefer a rep-free experience and 73% avoid suppliers who send irrelevant outreach, the case for qualifying and personalizing before you contact an identified visitor.
• UK Information Commissioner's Office, "Legitimate interests" (UK GDPR guidance): the regulator's definition of the lawful basis most B2B visitor outreach relies on, and the transparency conditions attached to it.