Signals
Website Signals
Website Signals show which target companies and target contacts are engaging with your website.
Once the 1eye Vision snippet is installed, 1eyeᴬᴵ starts capturing website activity such as page visits, form activity, traffic source, UTM data, and visitor behavior. Website Signals help your team understand who is visiting, what they viewed, and which targets are worth acting on.
Use Website Signals to find active companies, identify relevant contacts, evaluate ICP and persona fit, track high-intent pages, and move the right targets into lists and campaigns.
Before you begin
To use Website Signals, you should have:
A 1eyeᴬᴵ workspace
The 1eye Vision snippet installed on your website
Your website domain added under Vision settings
Important forms added under form tracking URLs
ICPs and personas reviewed in your Knowledge Base
Exclusions reviewed so 1eyeᴬᴵ avoids companies you do not want to target
For this guide, we’ll use Snowbricks as the example workspace.
Field | Example |
|---|---|
Company | Snowbricks |
Domain | snowbricks.io |
Workspace admin | Matt Bru |
Admin email |
What Website Signals capture
Website Signals can include activity such as:
Page visits
Form activity
Traffic source
UTM parameters
Session activity
Company identification
Contact identification when available
ICP evaluation
Persona evaluation
Date and time of activity
This helps your team turn website traffic into target company and target contact intelligence.
How Website Signals work
Website Signals start with the 1eye Vision snippet.
A visitor lands on your website
The visitor views a page such as your homepage, pricing page, demo page, contact page, or content page.1eyeᴬᴵ captures the activity
The Vision snippet records page activity, source data, and other available signal context.1eyeᴬᴵ identifies the company or contact when available
If there is enough context, 1eyeᴬᴵ may identify the target company, target contact, or both.1eyeᴬᴵ evaluates fit
Companies are evaluated against your ICPs. Contacts are evaluated against your personas.The signal appears in your workspace
Your team can review the signal by company or by contact, filter it, export it, or act on it.
Website signal types
Website Signals can include different types of activity.
Signal type | What it means |
|---|---|
Page visit | A company or contact visited a tracked page on your website. |
Form activity | A company or contact interacted with a tracked form. |
Source activity | 1eyeᴬᴵ captured where the visitor came from. |
UTM activity | 1eyeᴬᴵ captured campaign parameters from the URL. |
Company identified | 1eyeᴬᴵ identified the company behind the activity. |
Contact identified | 1eyeᴬᴵ identified a person behind the activity when available. |
ICP match | 1eyeᴬᴵ evaluated the company as matching an ICP. |
Persona match | 1eyeᴬᴵ evaluated the contact as matching a persona. |
Page visits
Page visits show which pages a company or contact viewed.
Examples of tracked pages:
Page visits help your team understand interest level.
For example, a target company visiting your pricing page, demo page, and case study page may be more actionable than a visitor who only viewed the homepage.
High-intent pages
Some website pages usually show stronger intent than others.
High-intent pages may include:
Pricing page
Demo page
Contact page
Trial signup page
Product page
Comparison page
Case study page
Integration page
Security page
Gated content page
For Snowbricks, a company visiting snowbricks.io/pricing and snowbricks.io/demo may be a stronger signal than a company visiting only snowbricks.io.
Form activity
Form activity shows when visitors interact with important forms.
Common forms include:
Demo request forms
Contact forms
Trial signup forms
Newsletter forms
Webinar forms
Gated content forms
Waitlist forms
Event registration forms
For Snowbricks, important form tracking URLs may include:
Form activity is usually high intent because the visitor is taking a direct action.
Traffic source
Website Signals may include traffic source when available.
Traffic source helps your team understand how a company or contact reached your website.
Examples:
Direct traffic
Organic search
Paid search
LinkedIn
Email
Referral
Partner campaign
Content campaign
Event campaign
Traffic source helps your team connect website activity back to GTM motion.
For example, if a target company visits after a LinkedIn campaign, your team can use that context in follow-up.
UTM parameters
1eyeᴬᴵ can capture UTM parameters when they are present in the URL.
Common UTM parameters include:
Parameter | Example | What it tells you |
|---|---|---|
utm_source | Where the traffic came from | |
utm_medium | paid_social | The channel or medium |
utm_campaign | q2_pipeline_push | The campaign name |
utm_content | founder_ad_v1 | The ad, post, or creative variant |
utm_term | ai_data_platform | The keyword or audience term |
Example URL:
UTMs help your team understand which campaigns are driving target activity.
Company identification
When website activity comes in, 1eyeᴬᴵ may identify the company behind the visit.
A company signal may include:
Company name
Company domain
LinkedIn profile
Location
Industry
Employee count
Revenue when available
Founded year when available
Page visited
Time of visit
Signal count
ICP match when available
Example:
Field | Example |
|---|---|
Company | Northstar Analytics |
Domain | northstaranalytics.com |
Location | New York |
Industry | Software |
Employees | 420 |
Latest signal | Page visit |
Page | snowbricks.io/pricing |
ICP match | ICP - B2B-SAAS |
Use company identification to understand which accounts are showing activity.
Contact identification
When available, 1eyeᴬᴵ may identify a contact connected to website activity.
A contact signal may include:
Contact name
Title
Company
LinkedIn profile
Page visited
Time of visit
Signal count
Persona match when available
Example:
Field | Example |
|---|---|
Contact | Jordan Lee |
Title | VP Revenue Operations |
Company | Northstar Analytics |
Latest signal | Pricing page visit |
Persona match | REVOPS |
Not every website visitor can be identified as a person. Person-level identification depends on available signal data, enrichment match, source quality, and visitor context.
ICP evaluation for website signals
1eyeᴬᴵ evaluates identified companies against your ICPs.
When a company visits your website, 1eyeᴬᴵ checks whether that company matches one or more ICPs in your Knowledge Base.
For Snowbricks, ICPs may include:
B2B SaaS Companies
Revenue Operations Teams
AI-Native GTM Companies
Data Infrastructure Companies
Enterprise Sales Organizations
B2B Marketplaces and Platforms
If a company matches an ICP, 1eyeᴬᴵ may show an ICP badge on the company card.
Example:
ICP match explanation
When a company matches an ICP, 1eyeᴬᴵ may show an explanation.
Example:
Use the explanation to understand why the company was matched and whether it should move into a target list or campaign.
Why ICP evaluation matters
ICP evaluation helps your team focus on website visitors that are actually relevant.
It helps you:
Prioritize target companies
Reduce noisy traffic
Avoid wasting time on poor-fit accounts
Build cleaner target company lists
Improve credit efficiency
Launch campaigns with better fit
Without ICP evaluation, website traffic can become a long list of visitors.
With ICP evaluation, 1eyeᴬᴵ helps your team identify which companies matter.
Persona evaluation for website signals
1eyeᴬᴵ evaluates identified contacts against your personas.
When a contact is connected to website activity, 1eyeᴬᴵ checks whether that contact matches one or more personas in your Knowledge Base.
For Snowbricks, personas may include:
Revenue Operations Leader
Head of Data
VP Sales
VP Marketing
GTM Systems Leader
AI Transformation Leader
Founder or CEO
If a contact matches a persona, 1eyeᴬᴵ may show a persona badge on the contact card.
Example:
Persona match explanation
When a contact matches a persona, 1eyeᴬᴵ may show an explanation.
Example:
Use the explanation to decide whether the contact should be enriched, added to a target list, or moved into a campaign.
Why persona evaluation matters
Persona evaluation helps your team focus on the right people.
It helps you:
Prioritize relevant target contacts
Avoid engaging poor-fit contacts
Build cleaner target contact lists
Personalize outreach by role
Route contacts into the right campaigns
Follow up with better context
A website visit is more useful when you know both the company fit and the contact fit.
View website signals by company
Use Signals → By Company to review website activity at the account level.
This is useful when you want to answer:
Which companies are visiting our website?
Which companies have multiple signals?
Which companies match our ICPs?
Which pages did each company view?
Which companies should we add to target lists?
Which companies should we prioritize for campaigns?
Start here when you want to prioritize accounts.
View website signals by contact
Use Signals → By Contact to review website activity at the person level.
This is useful when you want to answer:
Which contacts are active?
Which contacts match our personas?
Which company does each contact belong to?
Which pages did each contact view?
Which contacts should we enrich?
Which contacts should we move into campaigns?
Use this view when you want to prioritize people inside active companies.
Search website signals
Use search to find a specific company, contact, domain, or page.
Examples:
Search is helpful when you know exactly what you are looking for.
Filter website signals
Use filters to narrow website signals.
You can filter by:
Company
Contact person
ICP
Persona
Type
Date range
For website activity, useful filters include:
Page signals
Form signals
ICP matches
Persona matches
Recent activity
Specific companies
Specific contacts
Filter by type
Use the type filter to focus on website-related signal types.
Useful types include:
Type | Use it to find |
|---|---|
Page | Website page visits |
Form | Tracked form activity |
ICP | Companies that matched an ICP |
Persona | Contacts that matched a persona |
Use this when you want to separate general browsing from higher-intent activity.
Filter by date range
Use date range to review website signals from a specific period.
Examples:
Today
Yesterday
Last 7 days
Last 30 days
After a product launch
After a LinkedIn campaign
After an email campaign
During a conference or event
During a paid campaign
Date range filters help your team connect website activity to GTM campaigns.
Sort website signals
Use sort to change the order of website signals.
You may sort by:
Most recent activity
Highest signal count
Company name
Contact name
Created date
Updated date
Use sorting to prioritize the companies or contacts that matter first.
Export website signals
Use Export CSV to download website signal data.
Export is useful when you want to:
Share website activity with your team
Analyze activity in a spreadsheet
Review target companies offline
Build a campaign plan
Compare website activity over time
Send signal data to RevOps
Review high-intent accounts with sales
Before exporting, use filters to narrow the data.
For example:
Show ICPs Only
Filter by Page or Form
Select the last 7 days
Export CSV
This gives your team a cleaner export with more actionable data.
Recommended workflow: company website signal
Use this workflow when you want to act on company-level website activity.
Open Signals → By Company
Review recent website visitors
Turn on Show ICPs Only
Look for high-intent pages such as pricing, demo, product, or contact
Review the ICP badge and match explanation
Open the signal timeline
Confirm the activity is relevant
Add the company to a target company list
Source matching target contacts
Launch or prepare a campaign
This workflow helps your team move from website activity to account prioritization.
Recommended workflow: contact website signal
Use this workflow when you want to act on person-level website activity.
Open Signals → By Contact
Review recent website activity
Turn on Show Personas Only
Look for high-intent page visits or form activity
Review the persona badge and match explanation
Open the signal timeline
Confirm the contact is relevant
Enrich the contact if needed
Add the contact to a target contact list
Launch or prepare a campaign
This workflow helps your team move from website activity to contact-level engagement.
Recommended workflow: high-intent website activity
Use this workflow when you want to find the most actionable website signals.
Open Signals
Select Filter
Set Type to Page or Form
Choose a recent date range, such as last 7 days
Apply filters
Review pricing, demo, contact, product, and comparison page activity
Check ICP and persona matches
Add the strongest companies and contacts to target lists
Prepare campaign follow-up with page context
This workflow helps your team focus on website activity that suggests stronger intent.
Best practices
Install Vision globally
Track all important GTM pages so 1eyeᴬᴵ can capture complete website activity.Track high-intent forms
Add demo, contact, trial, webinar, and gated content pages to form tracking URLs.Exclude low-value URLs
Exclude pages such as privacy, terms, login, admin, and internal app pages when they are not useful for GTM.Review company signals first
Start with companies to understand account-level activity.Use ICP matches to reduce noise
Turn on Show ICPs Only when you want to focus on target companies.Review contact signals next
Move from account-level activity to relevant people inside those companies.Use persona matches to prioritize contacts
Turn on Show Personas Only when you want to focus on target contacts.Prioritize high-intent pages
Pricing, demo, contact, product, comparison, and case study activity usually matters more than homepage activity.Use UTMs consistently
Clean UTM tagging helps you connect website activity back to campaigns.Act quickly on fresh signals
Recent website activity is usually more actionable than old activity.Keep your Knowledge Base current
If ICP or persona matches look wrong, update the Knowledge Base.Build lists from website signals
Move relevant companies and contacts into target lists instead of letting signals sit unused.
Troubleshooting
I do not see website signals
Check:
The 1eye Vision snippet is installed
Vision status shows installed
Your domain is included under Vision settings
The page is not excluded
Website traffic is reaching tracked pages
You are viewing the right date range
Filters are not hiding results
Website signals stopped appearing
Check:
The snippet is still live on your website
Your website was not recently redeployed without the snippet
Google Tag Manager is still published if you use GTM
Your domain is still included
The relevant pages are not excluded
Consent settings are not blocking the snippet
Browser extensions are not blocking tracking during testing
I see companies but not contacts
This can happen when company identification is available but person-level identification is not.
Not every visitor can be identified as a person.
Check:
Whether contact identification is available for the activity
Whether contact filters are hiding results
Whether personas are too narrow
Whether the contact view has a restrictive date range
ICP matches look wrong
Review ICPs in your Knowledge Base.
Check:
ICP descriptions
Company types
Industries
Company sizes
Use cases
Exclusions
If the ICP is too broad, 1eyeᴬᴵ may match too many companies.
If the ICP is too narrow, 1eyeᴬᴵ may miss good companies.
Persona matches look wrong
Review personas in your Knowledge Base.
Check:
Persona descriptions
Job titles
Seniority
Functions
Departments
Buying roles
If the persona is too broad, 1eyeᴬᴵ may match too many contacts.
If the persona is too narrow, 1eyeᴬᴵ may miss good contacts.
Form signals are not appearing
Check:
The form page has the Vision snippet installed
The form page is added under form tracking URLs
The form page is not excluded
The form is publicly accessible
The form is not blocked by consent settings
A test form activity was completed
Enough time has passed for activity to process
The export is too noisy
Before exporting:
Turn on Show ICPs Only or Show Personas Only
Filter by Page or Form
Select a recent date range
Filter by ICP or persona
Remove low-value pages from your review
Export only the focused view
I see traffic from companies we should not target
Add those companies to Exclusions in your Knowledge Base.
Common exclusions include:
Your own company
Current customers
Competitors
Vendors
Partners
Agencies
Poor-fit companies
FAQ
What are Website Signals?
Website Signals are activity from your website, such as page visits, form activity, traffic source, UTM data, and identified company or contact activity.
How do I start capturing Website Signals?
Install the 1eye Vision snippet on your website and make sure your domain is included under Vision settings.
Do I need to install the Vision snippet on every page?
For best results, install it globally across your website.
Can 1eyeᴬᴵ track forms?
Yes. Add important form pages under form tracking URLs so 1eyeᴬᴵ can track form-related activity.
Can I exclude pages from tracking?
Yes. Use excluded URLs for pages you do not want to track, such as login pages, admin pages, app pages, privacy pages, and terms pages.
What is a page signal?
A page signal shows that a company or contact visited a tracked page on your website.
What is a form signal?
A form signal shows activity from a tracked form.
What is an ICP match?
An ICP match means 1eyeᴬᴵ evaluated an identified company against your ICPs and found a match.
What is a persona match?
A persona match means 1eyeᴬᴵ evaluated an identified contact against your personas and found a match.
Why are some visitors anonymous?
Not every website visitor can be identified. Identification depends on available signal data, enrichment match, source quality, and visitor context.
Why do some companies not have ICP badges?
They may not match your current ICPs, or 1eyeᴬᴵ may not have enough context to evaluate them as a match.
Why do some contacts not have persona badges?
They may not match your current personas, or 1eyeᴬᴵ may not have enough context to evaluate them as a match.
Can I export Website Signals?
Yes. Use Export CSV to download the current signal view.
How do I improve Website Signal quality?
Keep your Vision setup clean, track important pages and forms, exclude low-value URLs, update ICPs and personas, and use exclusions.
Next step
Next, go to LinkedIn Signals to understand how 1eyeᴬᴵ captures and organizes activity connected to LinkedIn.