A Company Visited Your Website: Was It a Buyer, Applicant, or Vendor?
TL;DR: A company visiting your website is a reason to investigate, not proof of a buying project. Sales and growth teams should inspect page purpose, account fit, and existing relationships before choosing a contact. Separate company identification from person identity, and keep uncertain traffic out of automatic sales follow-up.
Does a company visit mean someone wants to buy?
No. A company match tells you which account was associated with website activity; it does not reveal the visitor’s motivation or establish that a named contact wants a conversation. Qualification starts after identification.
Our company reveal identifies companies behind anonymous website traffic. To associate activity with a specific person, send an identify event when the visitor submits a form, signs in, or provides an email address. A company match alone does not tell you which employee read a page.
Start with the pages visited and the account relationship. Those clues help you decide what deserves research, while leaving the visitor’s actual purpose open until you have stronger evidence.
| Observed context | Plausible interpretation to check | What remains unknown |
|---|---|---|
| Careers or job application pages | Recruiting-related research | Whether the visitor is an applicant |
| Help articles or support pages | Existing-user or troubleshooting activity | The visitor’s identity and relationship |
| Supplier, partner, or company information | Vendor or partnership research | Whether a commercial buying need exists |
| Product, pricing, or integration pages | Possible product evaluation | Who visited and whether an active purchase exists |
How can you separate buyers from applicants and vendors?
Use page purpose to form a hypothesis, then check it against the account’s fit and relationship to your company. Do not assign a person-level label from a page path alone.
Create page groups that reflect the way your own website works. A careers section has a different primary purpose from a pricing page, but navigation labels can hide mixed uses. Inspect the actual content before making a rule that routes every visit into the same sales motion.
- Recruiting context: Review careers and application paths before considering sales action
- Support context: Check whether the account is already a customer and whether another team owns the relationship
- Supplier context: Inspect partner or procurement context without assuming the visitor represents a potential buyer
- Commercial context: Look for activity related to your product’s buyer task and check account fit separately
An account may produce several kinds of traffic. Keep the observed activity attached to the decision rather than collapsing every session into a permanent company label. A company associated with recruiting traffic today is not necessarily ineligible for every future sales conversation.
Referrer data is available only when the browser or event source provides it. Browser privacy settings, redirects, and referrer policies can leave it blank. An empty field does not establish that someone typed your address or arrived from a particular campaign.
What should you check before routing an account?
Check fit, relationship, and evidence quality before handing the account to a rep. A visit should not override the reasons your team would otherwise exclude or hold the account.
- Fit: Confirm that the company matches the business model, segment, and problem your team serves
- Relationship: Check customers, active opportunities, ownership, and recent conversations
- Activity: Preserve the relevant pages, events, and observation time
- Identity: Distinguish the matched company from any separately identified person
- Next decision: State what additional evidence would justify research or outreach
Use the same fit criteria you would apply without the visit. Otherwise, page activity can become an excuse to contact accounts outside your market. A record that passes the fit check can still require a hold when ownership or relationship data is unresolved.
Connect our Salesforce integration and map the CRM fields you need for audiences and exclusions. Enable writes separately when the workflow needs to send supported records back to Salesforce. Before using a customer or opportunity filter, confirm that its source field is mapped and current.
When should you hold or exclude website traffic?
Hold traffic when its meaning or account relationship is unresolved. Exclude it from a particular motion when a documented rule establishes that the motion is inappropriate.
A hold is a request for more evidence. An exclusion is a targeting control. Keeping those decisions separate makes it easier to revisit an account without losing why the initial activity was not actionable.
| Condition | Recommended response | Release condition |
|---|---|---|
| Only noncommercial page context is visible | Hold sales outreach from this signal | A separate relevant business reason is verified |
| Account is a customer or has an active deal | Route to the existing owner or exclude from net-new outreach | The responsible owner approves the appropriate motion |
| Company identity or CRM match conflicts | Hold automatic action | Resolve the company and relationship match |
| Contact is selected only because the company visited | Research role relevance | Verify why that person owns the problem |
| A person has opted out | Suppress outreach under your process | Do not treat another company visit as renewed permission |
Create dynamic exclusions with filters for companies or people. Matching records are excluded from targeting, and a company exclusion also covers its associated people. Review that scope before applying a company-wide rule to an issue that affects only one contact.
Test the filter against records that should be held and records that should remain eligible. Inspect the resulting audience, then correct any missing relationship fields or overly broad conditions before using it to trigger outreach.
What does corroborating activity add?
Corroborating activity can strengthen the case for account research, but it does not turn an inference into a confirmed buying project. Keep each signal’s source and meaning separate.
A pricing visit and a product question from an identified person are different evidence. The second can contain an explicit request; the first usually supplies page context. Review what each observation actually supports before combining them into a priority decision.
Do not assume that several events represent independent people or independent reasons to buy. Check visitor and session context where available, and avoid presenting repeated events as a count of interested stakeholders.
Keep company buying intent separate from contact intent when choosing a message and channel. Account activity can justify research without establishing that a particular employee is involved in the activity or wants a sales call.
How does Unify support this workflow?
We provide website activity filters and exclusion controls that you can use to build a reviewable qualification workflow. Your team still defines what counts as relevant activity and decides when a rep should act.
Filter website activity by viewed pages, URL patterns, events, campaign parameters, sessions, and recency. Combine those inputs with the appropriate CRM fields to build an audience around your qualification criteria, then inspect the accounts it includes.
To turn website visits into relevant outbound, review the activity, check account fit, and route the account to the appropriate owner. Give the rep the relevant pages and relationship context so they can evaluate the account before selecting a contact or writing a message.
- Growth teams: Own page grouping and explain what the observed event means
- Sales managers: Define the evidence a rep should receive with a routed account
- RevOps: Maintain relationship fields, exclusions, and exception ownership
If research leads to outreach, refer to a relevant business issue rather than claiming you watched the contact browse. When selecting or enriching a person, retain the origin of the contact data so a rep can check the chosen value and resolve conflicting records.
What mistakes should you avoid?
Preserve the boundary between observed traffic and inferred motivation.
- Calling every identified account a buyer
- Inferring a named person from company-level activity
- Treating a careers visit as permanent account disqualification
- Ignoring existing customer or opportunity ownership
- Using missing source data as evidence for a preferred explanation
Sign up for Unify to put this workflow into practice with your own account context.
Frequently asked questions
Can I identify the employee from a company visit?
A company match alone does not identify an employee. To associate activity with a person, send an identify event containing information such as their email address when they provide it.
Is a pricing-page visit buying intent?
It can justify research into commercial relevance, but it does not prove a project, budget, or willingness to speak.
Should careers-page visitors be excluded forever?
No. Hold that activity out of an automatic sales motion unless other evidence supports outreach. Avoid permanent account judgments from one page purpose.
What if the account is already a customer?
Check the account owner and route the context to the appropriate customer motion. Do not place the account into net-new outreach by default.
Does a missing referrer mean direct traffic?
Not necessarily. Browser privacy settings, redirects, or referrer policies can leave that information blank. Keep the source unknown unless other evidence establishes it.
How should I choose the contact?
Choose someone whose current responsibilities match the business problem. Keep contact selection separate from the company visit.
Glossary
- Company reveal: Associating anonymous website traffic with an account
- Identify event: An event supplying person information so activity can be associated with that person
- Page purpose: The primary task a page is designed to help a visitor complete
- Corroboration: Additional evidence relevant to a specific interpretation
- Hold: A temporary pause while a decision-relevant uncertainty is resolved
Sources
- Website visitor intent - Unify (Unify)
- How to create an exclusion - Unify (Unify)
- How to integrate Unify with Salesforce (Unify)
- Turn Website Visitors Into Outbound | Unify (Unify)
- Company Buying Intent Is Not the Same as a Contact Wanting a Sales Call (Unify)
- B2B Contact Data Provenance: How Records Reach Your CRM (Unify)
