Skip to main content

Website Visits API

Learn what data the Website Visits API returns and how to use it in your own workflows and automations.

Written by Hila

Website Visits tracks which companies are visiting your website and gives you behavioral data about those visits. Until now, this data was only available inside Lusha's platform. The API makes the same data accessible to developers and RevOps teams who want to route it directly into their own systems, automations, and workflows.

This article covers what the Website Visits API returns, who can use it, and how it fits into your existing API workflow.

Who Can Use This

The Website Visits API is available to accounts that have:

  • Website Visits already configured in their Lusha account

  • A valid Site ID

  • A paid plan

What You Can Query

Use the API to query companies that have visited your tracked domains. You can filter results by:

  • Intent score

  • Date range

  • Location

  • Pages visited

Data Returned Per Company

Each company in the response includes:

  • Number of sessions

  • Unique visitor count

  • Average session time

  • High-intent pageviews

  • Last visit date

Batch Support

You can query multiple domains in a single API call. This reduces request overhead when you are tracking more than one domain.

How It Fits Into Your API Workflow

The Website Visits API is designed to chain naturally with other Lusha API tools. A typical workflow looks like this:

  • Query Website Visits to get a list of companies visiting your site

  • Enrich those companies to get firmographic data

  • Find contacts at those companies

  • Check Signals to add more buying-intent context before outreach

šŸ’” Note: You must have Website Visits configured in your account before using this API. If you haven't set it up yet, contact your account admin to implement it on your site.

API Reference

Full endpoint documentation, request parameters, and response schemas are available at docs.lusha.com/apis/openapi/website-visits.

Now you're ready to plug real-time intent data directly into your workflows.

Did this answer your question?