> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/use-cases/visitor-identification.md).

# Visitor identification

Identify the companies and people behind your website visits and email engagement, so you can follow up on real interest.

### Website visitor identification

Identify your Website Traffic and never miss a sales opportunity again.

Let’s face it, the B2B sales process has changed. Companies have had to adapt and find new ways to reach their customers and get heard through the noise. How much of your website traffic are potential clients looking at your products? Is your sales team looking for new channels to tap into? Then LeadBoxer just might be the perfect tool to identify your website visitors.

Using Leadboxer, we enable you to identify the businesses AND individuals visiting your website using our unique multi step or layered approach.

### Email Click-through Identification

Track Email Opens or Reads.

**Identify your email recipients on your site** and see their website behaviour. See what your readers are doing AFTER they click on a link in your email. Once identified, we can see their past and future visits as well!

**What are the benefits of email tracking?**

* Identify (more) individual users on your website
* Learn what your audience does after they click and land on your website
* Understand your email marketing campaigns better than ever.
* Get insights and notifications when your audience is Ready-to-buy!

### Contacts and form Identification

Automatically (or manually) track all form submissions and see the complete customer journey from entry to conversion. We do not only track forms, also integrate with Chatbots, newsletter signups, portal logins, intranets, etc.

LeadBoxer has a flexible input layer, meaning we can capture data through various methods and techniques like our advanced javascript library, URL submissions, Zapier or any of our native integrations like Hubspot or Marketo. We also have a public API to get and push data to.

### Identify Companies AND Individuals

LeadBoxer identifies both companies and individuals visiting your website. Identification of companies and organisations happens out of the box based on IP addresses, form fields, email and other touch-points.\
\
Identifying individuals on your website can be achieved by utilising one or multiple of our integrations that capture individual data.

***

See also [Visitor identification on leadboxer.com](https://www.leadboxer.com/app/visitor-identification) and [ICP & persona matching](/leadboxer/use-cases/icp-and-persona-matching.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.leadboxer.com/leadboxer/use-cases/visitor-identification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
