A website visitor follow up email that gets replies: pick the right person from the pages they read, send within days, never mention the visit, stay compliant.
A good website visitor follow-up email goes to the person most likely to own the problem the visited pages point to, lands within one or two business days, and talks about that problem without ever mentioning the visit. Pricing visits point to a budget owner, docs and security pages to a technical lead, and careers-only visits to nobody.
Someone from a 200-person freight company read your pricing page three times this week and never filled in a form. Visitor identification turned that into a company name. Now you have to decide who to email, when, and what to say. Get it wrong and a warm account becomes a deleted email or a privacy complaint.
This guide covers the email, not the tracking tool. For the identification side, see how website visitor identification works.
A website visitor follow-up email should talk about the problem the visited pages point to, in four to six lines, with one easy question at the end. It should not mention the visit. The pages give you the topic and the timing; the email reads like well-researched outreach that arrives at the right moment.
Here is the difference in one pair of opening lines:
Weak: “Hi Dana, I noticed someone from Kestrel Freight was on our pricing page yesterday.”
Better: “Hi Dana, finance teams moving off spreadsheet expense approvals usually ask two things first: what it costs per seat and whether it syncs with NetSuite. Both answers are below, in two lines.”
The first line tells Dana she was watched. The second shows you understand the decision she is probably making. Vendors disagree here: some templates still open with the page visit, while Knock2’s script guide says the page should shape the angle but never be named. We side with Knock2, and the compliance section below explains why.
Only visits that show a decision in progress deserve a personal email: repeat pricing visits, integration or API docs, security and compliance pages, and comparison pages, from a company that fits your ideal customer profile. A single blog read is research. It belongs in a nurture campaign or nowhere.
Use this table to turn pages into a person, an angle and a deadline. The role column is the part most guides skip.
| Pages read | Who to email | Angle for the email | Send within |
|---|---|---|---|
| Pricing, two or more visits in a week | Budget owner: department head, finance or ops lead | Cost model and what drives the price for a team their size | Same or next business day |
| Integrations, API docs | Technical evaluator: head of engineering, systems or RevOps owner | How the specific integration works and how long set-up takes | 1–2 business days |
| Security, trust, DPA pages | IT or security lead, sometimes legal | Offer the security pack or questionnaire answers up front | 1–2 business days |
| Comparison or “vs” pages | The likely project owner (team lead in the buying function) | A criterion most comparisons miss, without naming the rival | 1–2 business days |
| Case study in their industry | Team lead building the internal case | A similar company’s problem and the before/after, briefly | Within the week |
| One blog post, homepage only | Nobody personally | Nurture or retargeting | No email |
| Careers pages only | Nobody | Probably a job seeker | No email |
Email the person who owns the decision the pages suggest, not whoever the tool guesses was browsing. The person on your pricing page might be an analyst asked to pull options together. Writing to the budget owner about cost, or the technical lead about the integration, puts the email in front of someone who can act on it.
When two or three different page types show up from the same company in a few days, you are probably looking at a buying group. Don’t send the same email to everyone on the same morning. Start with the most senior relevant person, then reach the technical or finance contact two or three days later with a different angle. Each person needs their own reason to reply; how AI SDRs personalise emails covers how to find one.
Finding the person is a contact-data lookup. In Outbound Labs that data comes from B2B data provider APIs and is billed by the provider, as in any other AI SDR campaign.
Follow up within one or two business days for most strong signals, and the same or next business day for repeat pricing visits. After about two weeks, treat the signal as stale and move the company to nurture. Faster is better, but “within the hour” advice comes from a different situation.
The speed figure everyone quotes comes from a 2011 Harvard Business Review audit of 2,241 US companies. Only 37% replied to web leads within an hour and 23% never replied at all. Firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that waited even one hour longer. That is a strong finding, but it measured people who submitted an inquiry and expected a call. An anonymous visitor asked for nothing. An email within minutes of a pricing visit can feel less like service and more like surveillance.
So our rule: use speed to beat the decision, not to prove you were watching. Knock2’s guide treats signals older than 14 days as decayed, and we agree. After two weeks, the evaluation has usually moved on.
Here are three worked examples for a hypothetical company selling expense-management software. The companies and names are made up; the reasoning is the point.
What happened: A 200-person freight company viewed /pricing on Monday, Wednesday and Thursday, and /integrations/netsuite once. Who we would email: the head of finance operations, because pricing plus an accounting integration points to the person who owns spend and the finance system. When: Thursday or Friday morning.
Subject: netsuite sync and per-seat cost
Hi Dana,
Finance teams moving off spreadsheet expense approvals usually ask two things first: what it costs for a team of around 200 and whether approved expenses land in NetSuite without re-keying.
Short answers: pricing is per active submitter, so occasional travellers cost less than full-time users, and approved expenses post to NetSuite as bills with the cost centre attached.
Would a 15-minute walkthrough with your NetSuite admin on the call be useful, or is it simpler if I send the field mapping?
Ben
The email offers a document as an alternative to a call. That gives Dana an easy yes even if she isn’t ready to talk.
What happened: A 60-person software company read /docs/api and /security in two sessions on the same afternoon. Who we would email: the head of engineering or whoever owns internal tools, since API and security reading is technical due diligence. When: next business day.
Subject: security questionnaire for expense tools
Hi Priya,
When engineering teams get asked to vet an expense tool, the slow part is usually the security questionnaire rather than the integration.
We keep ours pre-filled, along with the API rate limits and the SSO set-up notes. Want me to send the pack so it’s ready if this lands on your desk?
Ben
No demo pitch. A technical evaluator wants less work, so the offer removes work.
What happened: A company in your ICP viewed /careers, a job listing and one blog post. Who we would email: nobody. The most likely reader is a candidate. An email to their finance director about expense software would be irrelevant at best and awkward at worst. Leave the company in a nurture list and wait for a stronger signal.
No. Mentioning the visit makes the email about your tracking rather than their problem, and it invites the question you least want: how do you know that? The timing already makes a relevant email feel relevant. Naming the page adds nothing except discomfort.
Sometimes someone will ask how you found them anyway. Answer briefly and honestly about where their contact details came from, and offer an easy way out: “We use a B2B contact database to find the right person at companies we think we can help. If this isn’t useful, say so and I won’t email again.” Don’t list pages or visit counts.
Treat vendor numbers with care too. RB2B reports a 30% positive reply rate on more than 300,000 visitor emails a month, but an independent teardown points out the figure is self-reported and compares warm, high-intent visitors with cold lists. Expect better replies than cold outreach, not miracles.
There are two separate checks, and most guides only cover the first. The tracking script on your site needs a lawful basis and, in practice, consent before it runs. The email you send needs its own basis, must tell the person where you got their details, and must stop the moment they object. This is our reading of the guidance, not legal advice.
The tracking. The UK regulator’s ICO guidance on storage and access technologies, finalised on 29 April 2026, covers tracking pixels, scripts and tags, not only cookies. In the EU, the EDPB’s Guidelines 2/2023 (version 2.0, adopted 7 October 2024) say pixel tracking falls under Article 5(3) of the ePrivacy Directive, and that IP-only tracking can too unless you can show the IP address doesn’t come from the user’s device. Using visits to target sales outreach doesn’t look like any of the narrow exceptions to us, so plan on consent.
The email. The ICO’s business-to-business marketing guidance says the PECR email consent rule doesn’t apply to corporate subscribers such as limited companies and LLPs, but sole traders and some partnerships are treated like individuals. You still need a UK GDPR lawful basis and must tell people you will market to them. GDPR Article 14 says that when you got someone’s data from a third party and use it to contact them, you must give the privacy information, including the source, by the first communication at the latest. Article 21 gives everyone an unconditional right to object to direct marketing.
In practice that means one short line naming where the contact data came from, a link to your privacy notice, a one-word opt-out, and a suppression list that every tool you use respects. In the US, CAN-SPAM covers business email too, so keep an opt-out and a postal address in every message.
The usual failures are emailing every company the script names, naming the visit, writing to the wrong role and letting alerts pile up unread. Alerts nobody acts on are the same as no identification at all. Run this check before every send:
| Check | If yes |
|---|---|
| Company outside your ICP? | Don’t send |
| Careers pages only, or a competitor or vendor? | Don’t send |
| Open opportunity or existing customer? | Alert the account owner instead |
| Contact previously objected or unsubscribed? | Don’t send, in any channel |
| UK sole trader or unincorporated partnership? | Email only with consent |
| Signal older than 14 days? | Move to nurture |
| Draft mentions the visit, page or time? | Rewrite |
| Email says where the contact data came from, with an opt-out? | If no, add it |
Outbound Labs includes visitor identification in its plans: 1,000 identified visitors a month on Growth ($149) and 10,000 on Scale ($499), as listed on our pricing page. Its six agents (Researcher, Strategist, Prospector, Writer, Sender and Closer) handle the research, contact finding and drafting, and you approve every campaign before anything sends. We explain why that approval step matters in what an AI SDR should never do without your approval.
Sending stays conservative: up to 40 emails per inbox per day, and campaigns pause automatically if bounces go above 2%. A warm account is worth protecting; our guide to deliverability for AI cold email explains how. If you’d rather do this by hand, the table and checklist above work just as well.
RB2B pricing from its own page: Free, Starter $79, Pro from $149, Pro+ from $199. See what each includes, the cost per identified visitor and hidden costs.
Eathan Brown · 28 Oct 2026 · 8 min readRB2B alternatives compared using prices from each vendor's own page: Leadfeeder, Albacross, Warmly, Vector and more, plus the cost per identified visitor.
Eathan Brown · 25 Oct 2026 · 9 min readBelkins reviews from Clutch, Trustpilot and TrustRadius, its four published prices, cost per held meeting maths, and who should skip it. Checked Nov 2026.
Eathan Brown · 2 Nov 2026 · 8 min readSDR agency vs in house SDR compared on speed to meetings, control, management load, contracts, meeting quality and attrition, with a switch-over checklist.
Eathan Brown · 2 Nov 2026 · 8 min read