> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How Leadpipe works

> Understand what Leadpipe identifies, what the data means, and how teams use it

## The simple version

Leadpipe helps you identify website visitors, understand which traffic matters, and move that traffic into a useful workflow.

That usually means three things happen:

1. A pixel collects the visit on the right site.
2. Leadpipe resolves that traffic into people and companies.
3. Your team filters that data and sends the right visitors into sales, ads, email, or reporting workflows.

## What Leadpipe is actually helping you answer

<Columns cols={2}>
  <Card title="Who visited?" icon="user">
    Leadpipe helps you understand which people and companies were on your site.
  </Card>

  <Card title="How strong is the signal?" icon="signal">
    Recency, landing page, repeat activity, and intent help your team prioritize what matters.
  </Card>

  <Card title="Is this our kind of traffic?" icon="filter">
    Filters, segments, and suppression help you keep the useful traffic and remove the rest.
  </Card>

  <Card title="What should happen next?" icon="route">
    Leadpipe is strongest when the data flows into a clear next step.
  </Card>
</Columns>

## What a useful Leadpipe workflow looks like

A strong Leadpipe setup usually looks like this:

* track the right site with the right pixel
* review identified visitors in **Visitor Insights**
* suppress obvious noise and bad-fit traffic
* save one focused view for the team that will use the data
* route that slice into one output such as a CRM, Slack, webhook, or export

## What to expect from the data

Some records will be richer than others. The most useful way to judge Leadpipe is by whether the traffic is actionable for your team.

Read [Understanding data quality](/guides/understanding-data-quality) for a more detailed explanation.

## Where to go next

* Read [Get started](/guides/get-started) to install your first pixel and confirm data is flowing.
* Read [What to do with identified visitors](/guides/what-to-do-with-identified-visitors) to choose the right operating play.
* Read [Trial success guide](/guides/trial-success-guide) to evaluate value quickly and cleanly.