LeadJaw Glossary

When a business visits your website, their internet connection routes through a registered corporate network. LeadJaw matches that IP address against commercial IP intelligence databases to identify the company name behind the visit, without the visitor filling in a form or accepting a cookie.

Not all visitors can be identified. Consumer broadband connections, mobile networks and some smaller businesses do not have registered IP ranges. These appear as unidentified in LeadJaw. ISP-flagged visitors, those routing through internet service provider networks rather than a registered company, are separated from genuine company visits so they do not inflate your identified count.

IP geo-location resolves a visitor's IP address to a physical location: typically country, region and city. LeadJaw captures this for every visitor, identified or not, so you can see where your traffic is coming from even when the company cannot be identified.

Geo-location accuracy varies. Country is reliable. City-level accuracy depends on the IP range and is approximate, particularly for mobile connections.

Search engine crawlers, ad verification tools and other automated bots visit websites constantly. Left unfiltered, they inflate visitor counts and distort your data. LeadJaw automatically detects and separates bots from human visitors using IP reputation data, user agent signals and behavioural patterns.

Filtered bots are hidden from your main dashboard by default but can be viewed separately in Search using the bots-only filter. Ad verification crawlers, which visit to confirm your ads are displaying correctly, are identified and labelled separately.

An ISP (Internet Service Provider) visitor is one whose IP address resolves to a broadband or mobile network rather than a registered business. These visits come from real people but cannot be matched to a specific company. They may be employees working from home, individuals browsing on a personal connection, or small businesses sharing a residential IP range.

LeadJaw flags ISP visitors separately so they do not appear as identified companies. You can manually reclassify a visitor if you know their company from other context, such as a form fill submitted during the same session.

After a visitor is identified, LeadJaw enriches the record with additional company data pulled from commercial intelligence databases. Enrichment typically adds industry classification, employee count, estimated revenue, company logo and headquarters location.

Enrichment runs automatically in the background within a few minutes of identification. Enriched data appears in the visitor profile, the dashboard, and in any active streams or alert rules that reference industry or firmographic filters.

Each LeadJaw plan includes a monthly allowance of company identifications. This counts the number of unique companies successfully matched from IP addresses in a calendar month, not the number of visits. A company that visits your site 10 times in a month counts as one identification.

The allowance resets at the start of each billing month. Usage is shown on your dashboard and in account settings. Starter plans include 150 identifications per month, Growth plans 750 and Pro plans 3,000.

The LeadJaw dashboard shows your identified company visitors in real time. Each row displays the company name, industry, location, pages viewed, time on site and lead source. Visitors active on your site right now are highlighted with a live indicator.

The dashboard updates continuously without a page reload. You can filter by date range, lead stage, source type and industry directly from the dashboard view, or save any combination of filters as a stream for one-click access later.

LeadJaw captures where each visitor came from: the referring domain, search engine, social network, email campaign or direct entry. Source is recorded at the start of each session and displayed alongside the visitor record so you can see which channels are driving your most valuable traffic.

Source types are grouped into categories: organic search, paid search, social, email, referral and direct. These map to the channel labels shown in your dashboard and reports.

UTM parameters are tags appended to a URL to identify the source, medium and campaign name of a link. LeadJaw captures and stores UTM data for every visitor who arrives via a tagged link, so you can see exactly which campaign, ad or email drove a specific company to visit your site.

LeadJaw includes a UTM link builder in Settings to help you create correctly formatted tracking links without manual URL editing.

The Sales Funnel view gives you a top-down breakdown of your visitor traffic by stage, from all visitors through to identified companies, form fills, leads and opportunities. Each level is clickable, drilling into the visitors that make up that segment.

The funnel is designed to answer the question: of all the traffic coming to my site, how much of it is turning into identifiable business interest? It also supports PDF export for sharing with sales or management teams.

LeadJaw visualises your visitor locations on an interactive 3D globe and a flat world atlas. Each visit is plotted as a point on the map, giving you an at-a-glance picture of where your site traffic originates geographically. The globe rotates in real time and is filterable by date range.

This view is particularly useful for understanding international reach and identifying untapped markets where companies are visiting but few leads are converting.

Lead scoring assigns a value to each visitor or company based on how closely they match your ideal customer profile and how engaged their behaviour has been. LeadJaw scores visitors as hot, warm or cold based on a combination of visit frequency, pages viewed, time on site and whether they have visited high-intent pages such as pricing or contact.

Hot visitors, those showing strong buying signals, are surfaced at the top of the dashboard and flagged with a hot badge. Scores update automatically as new visit data comes in.

An Ideal Customer Profile (ICP) is a description of the type of company most likely to buy from you and get the most value from your product. In LeadJaw, you define your ICP by setting target industries, countries and company size ranges. Visitors that match your ICP receive a higher lead score automatically.

Defining an ICP helps surface the most relevant visitors from your traffic, particularly useful when you are tracking a high volume of companies and need to prioritise outreach.

A stream is a saved set of visitor filters that you can return to in one click. Instead of re-applying the same combination of industry, source type and date range each time you log in, you save it as a stream and it appears in your dashboard sidebar as a persistent view.

Streams can also be set up to send you a scheduled email digest showing the latest visitors that match the stream criteria, useful for sharing a focused view with a sales team member or tracking a specific campaign audience over time.

Alert rules send you a notification by email or Slack when a visitor matching specific criteria lands on your site. You can trigger an alert when a named company visits, when any visitor views a particular page such as your pricing or contact page, or when a combination of conditions is met.

Alerts are designed for high-value target accounts. If you are waiting for a specific prospect to return to your site, an alert rule means you hear about it the moment it happens rather than discovering it during a routine dashboard check.

LeadJaw's reporting suite covers attribution, top referrers, top companies, form fill summaries and 404 broken link detection. Reports are date-range filterable and designed to answer the questions a sales or marketing team most commonly asks: where is our traffic coming from, which companies keep returning, and which campaigns are driving the most valuable visits.

Attribution reporting in particular helps connect marketing spend to identified company visits, giving you a clearer picture of which channels are generating real business interest rather than just traffic volume.

LeadJaw records every page a visitor views during their session: the URL, the order of pages viewed and the time spent on each. This page-level data is visible in each visitor's profile and can be used to filter visitors who viewed a specific page using the URL filter in Search.

Page tracking is what allows you to set up alert rules that trigger when a visitor views your pricing or contact page, and what powers the high-value page signals in your ICP configuration.

When a visitor submits a form on your site, such as a contact form, demo request or newsletter signup. LeadJaw captures the submission and ties it to the visitor's session. This links the contact data to the company visit record, so you can see which company the form submitter works for, what pages they viewed before submitting and how they found your site.

Form fill capture works with most standard WordPress form plugins including Contact Form 7, WPForms and Gravity Forms, as well as Calendly bookings and custom HTML forms.

When a form fill is captured, LeadJaw extracts the contact's name and email address from the submission and stores them against the visitor record. These details are searchable from the Search page and can be exported via CSV on Growth and Pro plans.

Contact data captured via form fills is processed in accordance with LeadJaw's GDPR-compliant data handling policy. The contact's details are linked only to their own visit session and are not merged with other visitor records.

Lead stage is a classification assigned to a visitor or form fill contact to indicate where they are in your sales process. LeadJaw uses the standard stages: TBC, Subscriber, Lead, MQL (Marketing Qualified Lead), SQL (Sales Qualified Lead), Client, Other and SPAM.

Stages can be set manually on any visitor or contact record and used as a filter in Search and Streams. When a form fill is submitted, the stage is set based on the form type and can be updated as the lead progresses through your pipeline.

Search results in LeadJaw can be exported as a CSV file on Growth and Pro plans. The export includes company name, contact name, email, IP address, country, city, source, pages viewed, lead stage and first and last seen dates. Filters applied in Search carry through to the export, so you can export only the visitors matching a specific campaign, date range or industry.

Custom form tags let you create your own classification labels for form fill submissions, in addition to the built-in types (Demo, General, Support, Lead Gen). Up to 5 custom tags can be added per account and applied to any form fill to categorise submissions in a way that matches your own sales process.

LeadJaw sends a scheduled email digest summarising your most recent visitor activity. You can choose daily, weekly or both. Each digest includes your top identified companies, top lead sources, form fill summaries and any 404 broken link alerts detected during the period.

Digests are configurable per team member, with each user able to set their own digest schedule independently. Stream-based digests can also be set up to send a focused view of visitors matching specific criteria to individual team members.

Alert rules are automated notifications that fire when a visitor matching your criteria lands on your site. You can trigger alerts by company name, to be notified the moment a target account visits, or by page URL to know when any visitor reaches a high-intent page such as your pricing or demo request page.

Alerts are delivered by email or Slack, or both. Each rule can have its own delivery channel, so pricing page visits might go to a sales Slack channel while named company alerts go to a specific account manager by email.

LeadJaw tracks 404 errors, specifically pages that visitors try to reach but do not exist on your site. These are surfaced in your digest emails so you can identify broken links, outdated URLs in campaigns or external sites linking to pages you have deleted or moved.

404 detection is passive and runs automatically as part of standard page tracking with no additional configuration needed.

Visitor counters let you display live visitor numbers anywhere on your website: visitors on site right now, total visitors in the last 7 days and your all-time daily visitor record. Each counter pulls from your live LeadJaw data and updates automatically without a page reload.

Counters are added with a single line of HTML or a shortcode and work on any platform, including WordPress, Webflow, Squarespace, Wix or custom HTML. They are commonly used on landing pages and pricing pages as social proof, showing prospective customers that your site is actively visited by businesses like theirs.

Content personalisation shows different content to different visitors based on the industry of the company they work for, without them filling in a form. LeadJaw identifies the visitor's industry from their IP address and uses that to reveal tailored content blocks on the page.

A law firm visiting your site sees a section written specifically for legal teams. A technology company sees content for software businesses. A financial services company sees content relevant to their sector. Visitors whose industry cannot be identified see a default content block instead.

Personalisation is set up by adding a CSS class to any HTML element on your page. It works in any page builder, including Divi, Elementor and Beaver Builder, and on any platform. No coding experience is required.

Industry matching is the process LeadJaw uses to identify the sector a visiting company operates in, using enrichment data from IP intelligence databases. The industry value, such as "legal services", "financial services" or "information technology and services" is stored against the visitor record and used to drive content personalisation.

Your LeadJaw settings page shows you the exact industry names seen from your real visitors over the last 30 days, with a copy button to paste the value directly into your personalisation blocks.

A default content block is a fallback section shown to visitors whose industry cannot be identified, including first-time visitors not yet enriched, ISP visitors, or companies outside your enrichment data. It ensures every visitor sees something relevant rather than a blank space.

The default block is added by applying the class lj-default to any HTML element. It is hidden when a matching industry block is found and shown in all other cases.

A widget token is a read-only public key generated by LeadJaw that allows your website's front end to fetch visitor stats and personalisation data from the LeadJaw API. It is separate from your Account Token and has no access to your full visitor data and can only return aggregate counts and industry information.

The widget token is embedded in the install snippet automatically. It cannot be used to access, modify or delete your LeadJaw account data.

The consent gate is an optional feature that suppresses personalised content blocks until a visitor has accepted cookies via your site's cookie consent banner. It is activated by adding the class lj-consent-only to any personalisation block.

The consent gate lets you offer personalisation to consenting visitors while respecting the preferences of those who decline.

The LeadJaw tracking script is a small piece of JavaScript added to your website that records visitor sessions as they happen. It captures the page URL, referrer, session start time and basic browser environment data, then sends that information to LeadJaw for processing.

The script is lightweight, loads asynchronously so it does not affect your page speed, and works on any website that allows custom JavaScript. It is the only piece of code you need to add to your site to activate LeadJaw.

The LeadJaw WordPress plugin installs the tracking script automatically across your WordPress site with no theme editing required. Once connected with your Tracking ID and Account Token, it also adds a LeadJaw dashboard to your WordPress admin showing your top visited pages, live visitor stats, plan usage and quick links to your full LeadJaw account.

The plugin also enables visitor counters and website personalisation on WordPress sites, managed through the plugin's settings page. It is available free from the WordPress plugin directory.

The Webflow integration connects your Webflow workspace to LeadJaw and adds the tracking script to your published site automatically, with no manual code pasting or site republishing required. The integration is managed from LeadJaw's integrations settings page and uses Webflow's OAuth connection for secure authorisation.

The Calendly integration connects LeadJaw to your Calendly account and captures booking data as form fills. When a prospect books a meeting via Calendly, LeadJaw ties that booking to their visitor session, giving you a complete picture of their journey from first visit to booked call.

The integration supports both free Calendly accounts via Personal Access Token polling, and paid Calendly accounts via webhook. Both methods run automatically once connected, with no manual steps needed per booking.

The Slack integration sends visitor alert notifications directly to a Slack channel of your choice. When an alert rule fires, because a named company visited or a high-intent page was viewed, the notification arrives in Slack in real time, keeping your sales team informed without them needing to log in to LeadJaw.

The HubSpot integration pushes identified company visits and form fill contacts from LeadJaw into your HubSpot CRM automatically. When LeadJaw identifies a company visiting your site, it creates or updates the corresponding company record in HubSpot. When a form fill is captured, the contact is pushed to HubSpot and linked to the company.

The integration uses HubSpot OAuth for secure connection and runs as part of LeadJaw's background processing cycle, pushing new data every few minutes.

LeadJaw's REST API gives Pro plan users programmatic access to their visitor data. The API returns visitor records, company data, form fills, lead stages and session data in JSON format, allowing you to pull LeadJaw data into your own CRM, data warehouse, reporting tool or custom application.

The API uses Bearer token authentication. API keys are generated and managed from your LeadJaw account settings. Full endpoint documentation is available in the integrations section of your account.

A session is a single continuous visit to your site by one visitor. LeadJaw records a new session each time a visitor arrives at your site. If the same company visits on two separate occasions, that counts as two sessions. Sessions contain the pages viewed, time spent, source and any form fills submitted during that visit.

Your Account Token is a private authentication key used to connect third-party tools such as the WordPress plugin to your LeadJaw account. It allows those tools to retrieve summary data from your account, such as your top visited pages and plan usage, without exposing your full visitor data.

Your Account Token should be kept private. It is different from your Tracking ID, which is a public identifier used only to attribute page views to your account.

Your Tracking ID is a unique identifier that links your website's tracking script to your LeadJaw account. It appears in your tracking snippet and is passed with every page view your site records. Unlike your Account Token, the Tracking ID is safe to include in public-facing code as it has no authentication capabilities.

User seats control how many team members can access a LeadJaw account. Each seat is assigned to one person with their own login. The number of seats available depends on your plan. Additional seats are available on Growth and Pro plans.

LeadJaw uses three access roles to control what each team member can do. The Owner role has full access including billing, user management and all settings. The Admin role can access and change settings but cannot manage billing or users. The Viewer role can see visitor data and reports but cannot change any settings.

Roles allow you to give sales team members access to visitor data without exposing billing details, and to bring in external contractors with restricted access that cannot affect your account configuration.

Each team member can configure their own digest email schedule independently. One user might receive a daily digest while another prefers weekly only. Digest preferences are set per-user in account settings and do not affect other team members' notification preferences.