Reference
Lusha glossary
Definitions of key terms, features, and concepts you'll encounter while using Lusha. Curious about a term we missed? Drop us a line and we'll add it.
The company-level filters within a Target Profile — such as industry, headcount, HQ location, and technology — that define the types of businesses to target. Paired with Persona Criteria in ICP Hub.
A Workspace feature that analyzes an existing table daily and suggests new prospects that match the patterns of contacts already in the list.
A user role with full access to account settings, credits, integrations, billing, and team management. Counts as a seat.
An AI-powered tool within Lusha Engage that generates personalized cold email sequences based on your value proposition, prospect profile, and tone of voice.
A machine-learning feature that suggests high-potential contacts and companies aligned with your ICP, updating daily based on your activity and engagement history.
Lusha's RESTful API for programmatic access to prospecting, enrichment, signals, and recommendations. Authenticated via API key and credit-based. View API documentation
A unique authentication token required for every Lusha API request, generated in account settings.
Rows in the table are called audience. A row can be either a contact or a company.
An automation that enrolls new contacts added to a list into a pre-configured email sequence without manual action.
Lusha’s proprietary repository of over 280 million verified business contacts, continuously cross-referenced across multiple sources.
The recurring period (monthly or annual) over which a Lusha subscription is charged and credits are allocated.
A user’s set of personally owned records in a connected CRM (contacts, accounts, opportunities). Referenced when scoping CRM-based filters to records owned by a specific rep.
An undelivered email returned to the sender. Lusha’s verification process minimizes bounce rates by validating addresses before surfacing them.
A Workspace list-building method where users describe their target audience in plain language and the AI generates a matching table of contacts or companies.
A Workspace/Search list-building method where users manually apply structured filters (industry, job title, revenue, etc.) to search Lusha’s database and generate a results table.
A discounted credit package available for purchase in large quantities, allowing teams to top up their credit balance beyond their standard plan allocation. Bulk credits are ideal for high-volume prospecting, enrichment, or API usage.
The ability to reveal contact details for multiple prospects simultaneously in a single action. The number of contacts that can be bulk-shown at once depends on the user’s plan.
A planned ICP Hub feature that will automatically map decision-makers at a target account based on defined personas, enabling multi-threaded prospecting within a single account.
A metric within Lusha Engage that evaluates sequence performance and surfaces actionable improvement suggestions.
A US data privacy law for California residents. Lusha is registered as a California data broker and processes data in full compliance.
A dedicated company profile page within Lusha Search that consolidates all available data on a specific account, including firmographics, employee contacts, funding history, and technology usage.
Pre-built integrations that connect Lusha’s B2B data to third-party automation platforms, enabling hands-free lead enrichment, prospecting, and CRM hygiene without manual data entry.
A business professional record in Lusha’s database, including name, job title, email, phone number, LinkedIn URL, and company data.
Lusha’s universal currency, consumed when revealing contact data, enriching records, or making API calls. Cost varies by data type.
A maximum number of credits an Admin can assign to an individual user or group, preventing them from exceeding their allocation.
The date each month or year when a user’s credit balance resets or refreshes based on their plan.
A Workspace feature allowing Salesforce data — such as Opportunity Stage, Account Owner, and Account Type — to be used as prospecting filters directly inside Lusha, scoping results to records matching your live pipeline. Currently Salesforce-only.
A visual marker in the Lusha Extension or platform showing that a contact has already been exported to your connected CRM using Lusha, preventing duplicate exports.
A visual marker in the Lusha Extension or platform showing that a contact already exists in your connected CRM, before their details were shown.
A native connection between Lusha and platforms such as Salesforce, HubSpot, Pipedrive, and Bullhorn for direct data export.
The ability to upload a contact list and have Lusha automatically append verified data—emails, phone numbers, job titles, and company details—to each record at scale.
The process of appending missing or updated information to existing contact or company records, available in real time or in bulk.
A verified phone number connecting directly to an individual professional, bypassing company switchboards.
A Workspace option that lets users refine any saved table using natural language commands, without rebuilding the list from scratch.
An email that was not delivered to the recipient. Lusha Engage tracks bounces and flags contacts to help maintain sender reputation.
A data quality signal indicating the likelihood that an email address is valid and deliverable, based on multi-source verification.
A series of pre-written, automated emails sent to a prospect over time, managed within Lusha Engage.
Lusha’s process of validating email addresses across multiple data sources before surfacing them to users.
Lusha’s built-in sales engagement module for creating, scheduling, and sending personalized email sequences via a connected Gmail or Outlook account.
Lusha API endpoints for programmatically appending contact and company data to individual or batched records. View Enrichment API docs
A browser extension for Chrome and Edge that overlays Lusha contact data on LinkedIn, Sales Navigator, Salesforce, HubSpot, and other B2B sites.
The process of matching Lusha data fields (e.g., job title, email) to the corresponding fields in your CRM, so data exports land in the right place.
An AI-powered natural language search that translates a plain-language prospect description into the relevant platform filters automatically.
The EU’s primary data privacy regulation. Lusha holds ISO 27701 certification, ePrivacyseal, and TRUSTe verification to demonstrate compliance.
A Workspace feature that generates a ready-to-use API request — in cURL, Python, or TypeScript — based on the filters and search you have built in a Table. The request stays in sync with your filters automatically, so you can validate results visually before writing any code.
A cluster of users in a Lusha account that shares a collective credit limit, set by an Admin or Manager.
The strategic approach covering sales, marketing, and revenue operations to bring a product to market. Lusha positions its platform as a GTM intelligence layer.
A description of the company or individual most likely to benefit from your product. Used to power AI Recommendations, prospecting filters, and intent-based targeting.
A numeric score assigned to each recommended lead indicating how closely it matches a user’s defined Target Profile. Displayed alongside Signal Score in the AI Recommendations feed on the Home page.
A Lusha feature for defining and managing Target Profiles — configurations that describe your ideal companies and contacts. ICP Hub powers the AI Recommendations engine, generating daily scored tables of top companies and contacts based on ICP fit and buying signals. Admins can share profiles account-wide; all users can create up to 10 personal profiles.
A security setting that automatically logs a user out of Lusha after a defined period of inactivity. Configurable by Admins.
A Workspace feature that pulls existing records from a connected CRM (currently Salesforce/Hubspot) into a Workspace table for enrichment and analysis.
Behavioral signals indicating that a company is actively researching topics related to your product. Lusha integrates third-party intent data to surface in-market accounts.
An automatic Hot/Warm/Cold rating applied to each visiting company in Website Visits, based on pages visited, visit frequency, and time spent — particularly whether the visitor viewed high-value pages such as pricing or demo pages. Distinct from the broader Intent Data term.
AI-driven account suggestions based on active research activity aligned with your ICP.
A signal notification triggered when a tracked contact changes employer or role, enabling timely outreach at a high-intent moment.
A business professional or company identified as a potential customer, not yet engaged or added to a CRM.
A saved collection of contacts organized for outreach, campaigns, CRM export, or account-based targeting.
A Lusha API endpoint that returns contacts or companies similar to a given input, based on shared firmographic and professional attributes. View Lookalike API docs
Contacts or companies surfaced by Workspace’s AI that match the patterns of a user’s past successful reveals and saved lists, based on industry, seniority, and company size.
Lusha’s learning hub with tutorials, guides, and plays for getting more from the platform.
Lusha’s opt-in, crowdsourced data program where professionals voluntarily contribute contact information to improve data accuracy across the platform.
A feature providing intelligence derived from sales call data to help teams improve prospect interactions and outreach effectiveness.
A feature of the Lusha Extension that activates on any B2B website—not just LinkedIn—overlaying available contact and company data wherever you browse.
The state of a user’s AI Recommendations feed when no Target Profile has been configured in ICP Hub. Leads are surfaced based on account history rather than a defined ICP, and labeled “Lusha generated” in the Target Profile column. Once a Target Profile is saved, the feed shifts to ICP-based scoring.
A user role (Scale plan only) with admin rights but no access to credits or the prospecting platform. Does not count as a seat.
An open standard that allows AI assistants (such as Claude Desktop or Cursor) to securely connect to external data sources like Lusha’s API, enabling natural language data enrichment without writing API calls directly.
A toggle in the Workspace filter panel that excludes contacts or companies already present in a connected Salesforce account, preventing credit spend on records you already own. The inverse of the Search in My CRM (CRM Filters) feature.
A single, non-sequenced email sent to a contact or list from Lusha Prospecting/Plugin, for ad hoc or event-driven outreach.
Lusha’s credit system model in which Website Visits identification credits are drawn from the same shared credit pool as standard prospecting and enrichment. A configurable per-domain monthly credit limit prevents a single domain from consuming the full balance.
The contact-level filters within a Target Profile — such as job title, department, seniority, and location — that define the right buyer within a target account. One Target Profile can include up to 4 Persona Criteria sets, applied with OR logic.
Dynamic variables embedded in email templates, auto-populated with each contact’s data at send time.
Lusha API endpoints for programmatic search and retrieval of contacts and companies from Lusha’s database based on ICP criteria. View Prospecting API docs
Lusha’s core web application for searching its B2B database using advanced filters including job title, seniority, industry, company size, location, and technology stack.
A cap on the number of API requests allowed within a time period. Exceeding the limit returns a 429 error.
A Salesforce configuration that classifies records (e.g., contacts, leads) by type. Lusha lets admins specify which record type to use when exporting.
The act of unlocking a contact’s verified email or phone number. Consumes one credit; previously revealed data can be re-accessed at no additional cost.
A function aligning sales, marketing, and customer success to optimize the full revenue lifecycle. Lusha Workspace is built to serve RevOps teams.
A stored set of search filters in Lusha Search that can be re-run at any time, allowing users to quickly revisit or refresh a frequently used prospecting query.
Lusha’s core prospecting interface for finding contacts and companies within its B2B database. Users apply filters—such as job title, seniority, industry, company size, location, and technology—to build targeted lists, reveal contact details, and export results to a CRM or CSV.
Structured company-level attributes such as industry, size, revenue, location, and technology stack, used as prospecting filters.
A licensed position in your Lusha account. Admins and Users each occupy a seat; Managers (Scale only) do not count as a seat.
The maximum number of emails a connected mailbox can send per day using Engage, set to protect deliverability and comply with provider guidelines.
A filter and data attribute classifying contacts by organizational level such as C-suite, VP, Director, Manager, or Individual Contributor.
See Email Sequence.
The timing configuration for an email sequence, defining the days, times, and time zones in which emails are delivered.
In the Unified Recommendations List, the act of surfacing a contact’s verified contact details (work email or phone number) after a contact row has been revealed. Costs 1 credit per email and 5 credits per phone number. Distinct from Reveal, which unblurs identifying fields such as name and LinkedIn URL.
A numeric score reflecting the volume of active buying activity surrounding a recommended lead — including signals such as a new role, promotion, hiring growth, intent, and CRM match. Displayed alongside ICP Fit Score in the Home feed.
Real-time business intelligence events—such as job changes, funding rounds, or hiring activity—used to identify timely outreach opportunities.
A Lusha API that delivers timely account and prospect change events to enrich CRM systems and automated workflows. View Signals API docs
An authentication method allowing users to log in to Lusha using their company identity provider (e.g., Okta, SAML), without a separate Lusha password.
A temporary pause of a Lusha monthly subscription for 1–2 months, available twice per year, that maintains account access without permanent cancellation.
Lusha’s term for a Workspace table—a dynamic, editable list of contacts or companies that can be enriched, filtered, sorted, and synced to a CRM, all in one place. Tables can be built from chat, filters, or CRM imports, and enriched with additional data columns.
The core configuration unit in ICP Hub. Each profile combines Account Criteria (company-level attributes) and Persona Criteria (contact-level buyer attributes) to define your ideal companies and contacts. The AI Recommendations engine uses active Target Profiles to score and surface leads daily. Users can create up to 10 profiles per account; Admins can share profiles with the entire account.
Administrative features for adding, managing, and setting permissions or credit limits for team members.
Information about a company’s technology stack, used as a prospecting filter for competitive targeting or tech-stack-based segmentation.
A lightweight JavaScript snippet installed in the <head> of a website to enable the Website Visits feature. Matches visitor IP addresses to companies in Lusha’s database. Loads in under 50ms and is managed in Settings → Website Visits.
A security method requiring users to verify their identity with a second factor (e.g., SMS code or authenticator app) in addition to their password.
Lusha’s pricing model in which a single credit balance applies across all products and use cases—prospecting, enrichment, signals, and engagement.
Dashboards tracking platform usage, credit consumption, and team activity to help admins monitor adoption and allocate credits efficiently.
A user role with access to credits and the platform but no admin rights. Counts as a seat.
AI-generated columns added to a Workspace table that surface real-time signals from the web, such as company news, recent funding, executive changes, hiring trends, competitor data, and customer sentiment. Costs 1 credit per cell.
A real-time HTTP notification sent by Lusha to a specified endpoint when a subscribed event occurs, enabling event-driven automation without API polling.
A Lusha feature that deanonymises B2B web traffic by matching visitor IP addresses to companies in Lusha’s database. Each identified company is scored Hot, Warm, or Cold based on engagement. Requires a Tracking Pixel installation. Available on Pro, Premium, and Scale plans; credits charged at 2 per identified company per month.
A way to save a LinkedIn contact whose data Lusha hasn’t yet matched, so Lusha can notify you when data becomes available.
A collaborative environment bringing together CRM data, enriched contacts, and real-time buying signals for Sales, Marketing, and RevOps teams.
Can't find a term? We're here to help.