Home › Methods › Identify Companies in Session Recordings: What Is Realistic
Identify Companies in Session Recordings: What Is Realistic
You can identify companies in session recordings by resolving the visitor’s network address to an organisation and attaching that label to the recording. It works for a minority of B2B visits: BusinessMCP states roughly 20 to 35 percent. The result names a company, not a person, and is best treated as a lead for human follow-up.
How the match works
When a visitor loads your site, their request arrives from an IP address that belongs to a network. If that network belongs to a company, a data service can map the address to the organisation. The replay tool then tags the recording with the company, so a product or sales person can filter to recordings from named accounts.
BusinessMCP describes this on its session replay page: recordings link to an identified contact or to a company resolved from the network, and you can filter to identified visitors only. Its visitor identification page covers the identification product itself, and a free company lookup tool lets you try a resolution manually.
Key takeaway: a company label on a recording is a hypothesis about an account. Confirm it with behaviour, a form fill or a human check before you act.
What to expect
| Visitor type | Typical result |
|---|---|
| Employee on office network | Often resolves to the company |
| Employee on home broadband | Resolves to the internet provider |
| Mobile data | Carrier |
| VPN or cloud proxy | Hosting or VPN provider |
| Remote worker with a corporate VPN | Sometimes the company, sometimes not |
That is why match rates are modest. A vendor promising far above the range you see here deserves scepticism, and it is worth asking how the figure is calculated and whether internet providers are counted as matches.
Use cases for B2B teams
- Prioritising what to watch. Filter recordings to target accounts, instead of watching random sessions.
- Understanding the buying journey. See which pages a prospect’s team visits before a sales call.
- Product feedback from customers. Watch how existing customers use new features, with their company label.
- Sales alerts. Notify a rep when a named account visits pricing.
- Segmenting rage clicks. If a key account hits friction, escalate. See what rage clicks are.
Limits and pitfalls
- Low coverage. Most visits stay anonymous. Do not build a pipeline model on the assumption of full visibility.
- Wrong labels. A shared office, coworking space or parent company can produce misleading labels.
- Bots and cloud traffic. Filter them out; BusinessMCP says known bots are rejected at ingest.
- Overreach. Contacting a person because their network matched can feel intrusive. Use the match to prioritise, not to personalise creepily.
Privacy and compliance
Network addresses can be personal data in some contexts, and recordings add behaviour on top. Decide your lawful basis, document it, update your privacy notice and respect consent choices. BusinessMCP publishes guides on visitor identification and GDPR and consent modes, and says identify events wait for consent in gated modes. These are vendor documents; your counsel decides what applies to you. See also GDPR compliant session replay.
Evaluating a vendor
| Question | Why it matters |
|---|---|
| What share of B2B visits resolve to a company? | Calibrates expectations |
| Is the verdict labelled (company, ISP, unidentified)? | Avoids ISP-as-customer errors |
| Can you filter recordings by identified companies? | Saves review time |
| How is consent respected? | Compliance |
| What does it cost per resolved company? | Budget |
Test it on a week of your own traffic, then hand-check twenty named results. If more than a few look wrong, the data is not ready for sales use.
Where it fits in a replacement decision
If you are leaving Hotjar and sell to businesses, company context may be the feature that tips the decision, because Hotjar and Clarity do not identify visiting companies, per the comparison pages. It is not a reason by itself: BusinessMCP’s Growth plan costs $79 a month and has no surveys. Compare against your needs using our Hotjar alternatives guide and the vendor’s Hotjar comparison.
Verdict
Company identification adds a useful layer to recordings for B2B teams, with the caveat that most visits stay anonymous and every label is a hypothesis. Use it to decide which sessions to watch, confirm before acting, and keep the privacy basis documented.
A short workflow for B2B teams
- Turn on identification for a trial period, with consent gating configured as your legal basis requires.
- Export a day of visits with their verdicts and count how many are company, ISP, hosting or unidentified.
- Hand-check twenty named companies. Visit their sites, check their size and location against what you know about your audience.
- Pick three target-account behaviours worth alerting on, such as visiting pricing twice in a week.
- Review recordings of those accounts weekly, writing one finding per account.
- Decide what to do about the unidentified majority. Forms, chat and email capture remain the reliable ways to learn who a visitor is.
Mistakes to avoid
Counting ISP matches as customers. If the vendor’s number includes internet providers, your real company-level coverage is lower.
Emailing from a network match. A match names an organisation, not a contact. Reaching out to a named person requires a lawful basis of its own.
Skipping the privacy notice. If you record and identify, say so in plain words.
Overfitting to a few big names. A handful of enterprise accounts can dominate the list while smaller buyers stay invisible. Look at the whole picture, including unidentified sessions, before you decide which pages to improve.
Used with that discipline, company context turns a pile of recordings into a prioritised list. Used carelessly, it produces confident-looking noise. The difference is testing the output against reality in the first week.
Reading a recording with account context
Once a recording carries a company label, the questions you ask change. Instead of “where do visitors get stuck?”, you can ask “where did this prospect’s team get stuck, and did anyone from that account return afterwards?” That framing helps sales and customer success as much as product.
Keep the label in perspective. A single recording from a named company may be one curious employee, an analyst doing a competitor review or a contractor. Look for repetition: several sessions across days, several pages and a path that ends on pricing or documentation. Combine that with what your CRM already knows, and write a one-line note on the account rather than forwarding the raw recording around the company.
Frequently asked questions
Can session recordings show which company a visitor works for?
Sometimes. Tools can resolve a company from the visitor’s network. BusinessMCP says this works for roughly 20-35% of B2B visits.
Does this identify the person?
No. A network match names an organisation, not an individual. Recordings can be linked to a contact only when the person has been identified another way, such as a form fill.
Why do so many visits stay unidentified?
Home broadband, mobile data, VPNs and cloud proxies belong to providers, not employers.
Is company identification legal?
It depends on your jurisdiction, configuration and legal basis. Take advice; our article is general information only.
Sources
- BusinessMCP – Website visitor identification – https://businessmcp.com/website-visitor-identification
- European Commission – Data protection – https://commission.europa.eu/law/law-topic/data-protection_en