How to See Which Companies Visit Your Pricing Page (2026)

To see which companies visit your pricing page, you need two pieces: a visitor identification tool that resolves anonymous traffic to company names through reverse IP matching, and a page rule that flags or alerts on visits to your pricing path. Google Analytics 4 alone cannot do this. GA4 shows sessions, conversions, and traffic sources, but it will never tell you that three people from a 200 person software company read your pricing page twice this week.

The gap matters because pricing page traffic is the strongest buying signal most B2B websites produce. A visitor who reads a blog post might be a student, a bot, or a competitor. A visitor who opens the pricing page, checks the enterprise tier, and returns the next day is evaluating you. This guide defines what counts as a pricing page visit, explains how company identification works and where it honestly stops, and walks through alerts, segmentation by source, privacy practice, and the tools available in 2026 with verified pricing.

What Counts as a Visit to Your Pricing Page

A pricing page visit is one unique session that loads any URL under your pricing path, and a session ends after 30 minutes of inactivity. Define this before you buy tooling, because vendors count differently and your team will argue about the numbers later. A practical definition: any page view whose path matches /pricing, including subpaths such as /pricing/enterprise, counted once per session. One evaluator clicking between billing tabs for ten minutes is one visit. The same person coming back tomorrow is a second visit, and the return is the more interesting signal.

In VisiLead you encode the definition as a URL conversion goal. Go to Dashboard, then Settings, then Tracking, then Conversion Goals, create a URL goal, and set the pattern to /pricing* so the trailing star wildcard catches every subpage. The goal is matched on every page view, the matching visit is marked converted, and the conversion applies retroactively to every past visit from the same visitor, so you can see the full path that led to the pricing page. Pricing page visits also feed intent scoring: companies receive an ICP score from 0 to 100 and a high intent flag after three or more visits or one strong signal. The design principle behind the scoring is simple: being identified is not intent. Setup details live in the conversion goals documentation.

How Company Identification Works on Pricing Pages

Company identification matches a visitor's network address against a business IP graph and names the company only when the match clears a confidence threshold. VisiLead identifies companies worldwide this way and requires a minimum match confidence of 50 percent before a company is named. Below that threshold the visit stays anonymous, which costs you a lead record but protects you from confidently wrong data. Person level identification, which resolves a name, job title, LinkedIn URL, and business email when resolvable, runs on US traffic only.

Junk filtering happens before any lead is created. Government and military domains, education domains, residential ISPs, and consumer webmail domains are never turned into lead records, so your pricing page list is not padded with noise. Anonymous traffic is also labeled honestly: visits are badged as crawler, residential, or no match in the Companies table, which is how you distinguish a real evaluator from an ad verification bot hitting your pricing URL. On billing, one credit is spent only when a new company or a new person is revealed; repeat visits and returning visitors are free. The full mechanics are in identification and credits, and for the broader question start with who is visiting my website.

How to Set Up Pricing Page Visit Alerts for Sales

To implement pricing page visit alerts for sales, create an alert rule that fires on any visit matching /pricing* and deliver it to the Slack channel your team already watches. In VisiLead the setup takes five steps:

1. Go to Dashboard, then Alerts, then New alert, and name the rule.
2. Choose the page visit trigger and enter /pricing* as the path. The trailing star catches subpages like /pricing/enterprise.
3. Pick delivery channels: Slack through an incoming webhook URL for a channel like #sales, an email recipient, or a webhook to an HTTPS endpoint you control.
4. Click Send test. A sample alert for Acme Corporation with an ICP score of 92 and the page /pricing confirms the wiring.
5. Save the rule.

Each alert posts the rule name, company, domain, ICP score, location, and source, which is enough context for a rep to decide whether to act.

Two honest caveats. First, alerts fire once per matching visit and there is no digest or dedup mode today, so a very active company can ping the channel more than once in a day. Second, if you want spike style alerting rather than a ping on every visit, the closest fit is a repeat visit rule that fires when a company reaches a total visit count you choose (two or more), or an ICP score threshold rule that alerts only when a strong fit company shows up. The full walkthrough lives in the Slack alerts documentation.

How to Segment Pricing Page Visitors by Source or Campaign

To segment pricing page visitors by source or campaign, tag every link you control with UTM parameters and let a referrer based channel taxonomy classify the rest. VisiLead normalizes every visit into one of six channels: paid, organic, social, email, referral, or direct. Paid detection reads utm_medium values such as cpc, ppc, paid, and paidsearch, plus any medium containing ads, and maps the visit to the ad network itself: Google Ads, Bing Ads, Meta Ads, LinkedIn Ads, TikTok Ads, Reddit Ads, or X Ads. Ad serving referrers such as doubleclick and taboola are classified as paid even without tags.

AI assistants are treated as first class sources. Traffic from ChatGPT, Claude, Gemini, Perplexity, Copilot, You.com, and Phind is recognized and classified as organic on its own line, so you can see whether AI recommendations are sending buyers to your pricing page, a segment most analytics stacks still bury under direct or referral.

First touch and last touch attribution (source, medium, campaign, first referrer, and landing page) is attached automatically to identify and conversion events, with first touch captured on the first visit that carries a utm_source. In the company detail view, each visit in the timeline shows the channel and campaign that brought it, and the Channels report totals visits, identified companies, and hot leads per channel. Details are in attribution reporting.

UTM Tracking vs Server Side Analytics for Pricing Pages

UTM tracking describes the channel that sent a visit, server side identification describes who the visitor is, and a pricing page program needs both. They answer different questions, so comparing them as alternatives sets you up to pick the wrong one.

UTMs are free and universal, but they only describe links you tagged; when a prospect pastes a clean URL into a team chat, the visit lands in direct. Reverse IP identification works on every visit but cannot invent campaign context that was never tagged. Run both: UTMs feed first and last touch attribution, identification names the account, and together they produce the sentence sales actually wants, such as: LinkedIn Ads brought Acme Corporation to the pricing page twice this week.

Privacy Best Practices for Pricing Page Tracking

The best practices to respect privacy while tracking a pricing page are consent gated tracking, honoring Global Privacy Control, and identifying companies rather than profiling consumers. Concretely:

• Gate tracking behind consent where your audience requires it. VisiLead ships a manual consent mode: nothing is stored and no events are sent until your cookie banner grants consent, and revoking consent deletes the visitor id.
• Honor Global Privacy Control. A browser sending the GPC signal is not tracked, in both the automatic and the manual mode.
• Identify organizations, not consumers. Government, education, residential ISP, and webmail domains are never turned into lead records, which keeps private individuals out of your pipeline by design.
• Keep person level identification narrow. VisiLead runs person level resolution on US traffic only; elsewhere you work at the company level.
• Do not store what you do not need. VisiLead does not retain screen size, language, timezone, utm_term, or utm_content server side.

For the regulatory side in depth, read GDPR compliant visitor identification.

Tools That Track Companies Visiting Your Pricing Page

If you want a few options for tracking which companies visit your pricing page, the 2026 shortlist is VisiLead, Leadfeeder, RB2B, Factors.ai, Warmly, and 6sense, with entry prices running from $29 per month to enterprise contracts. All identify companies from anonymous traffic; they differ on person level data, geography, and price.

VisiLead pricing scales by identification credits: the free plan includes 10 one time credits, Starter is $29 per month for 100 credits, Growth is $79 per month for 500, Scale is $299 per month for 2,500, and annual billing saves 20 percent. A credit is spent only when a new company or a new person is revealed, so repeat visits from an already identified company cost nothing. The Warmly figure comes from their published pricing, and 6sense does not publish list prices, so the $33,500 median is Vendr's reported number. For head to head breakdowns, see the comparison pages and the pricing page.

Frequently Asked Questions

Q: How do you track which companies visit your pricing page? A: Install a visitor identification script, then create a URL rule for your pricing path. The script resolves business IP addresses to company names, and the rule marks which of those companies reached the pricing page. In VisiLead this is a conversion goal set to /pricing* plus an automatic intent signal on pricing visits.

Q: How do I set up alerting when pricing page visits spike? A: Combine a page visit alert on /pricing* with a repeat visit rule that fires when a company reaches a visit count you set, two or more. Alerts deliver to Slack, email, or a webhook, and every rule has a Send test button. There is no digest mode, so a plain page visit rule alerts once per matching visit.

Q: How do I segment pricing page visitors by source or campaign? A: Tag the links you control with UTM parameters and let the channel taxonomy classify the rest into paid, organic, social, email, referral, or direct. VisiLead also breaks out AI assistants such as ChatGPT and Perplexity as their own sources and attaches first touch and last touch attribution to each identified company.

Q: What counts as a visit to a pricing page? A: One unique session that loads any URL under your pricing path, including subpages such as /pricing/enterprise. Sessions end after 30 minutes of inactivity, so a visitor clicking between pricing tabs counts once, while a return the next day counts as a new visit and a stronger intent signal.

Q: What are the best practices to respect privacy while tracking a pricing page? A: Gate tracking behind consent where required, honor Global Privacy Control signals, identify companies rather than individual consumers, and keep government, education, residential, and webmail traffic out of lead records. Person level identification should stay narrow; VisiLead runs it on US traffic only.

Q: Can I see the individual person who visited my pricing page? A: Sometimes. Person level identification resolves a name, job title, LinkedIn URL, and business email for part of US traffic. Outside the US you see the company rather than the person, and any visitor who fills out a form can be linked to their visit history through an identify call.