> ## 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.

# Visitor overlap and analytics

> Find Orbit audience members who visited your website and compare completed audience runs

Use overlap when you want to combine topic research signals with activity on your own website. Use audience analytics when you want to understand how a saved audience changes between completed runs.

## Choose the scope

| Question                                                      | Endpoint                                                                |
| ------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Which people in any of our latest audiences visited our site? | `GET /v1/intent/audiences/website-visitors`                             |
| Which members of one audience visited?                        | `GET /v1/intent/audiences/{id}/website-visitors`                        |
| Which topics matched a visitor over time?                     | `GET /v1/intent/audiences/website-visitors/{hashedEmail}/topic-history` |
| What changed since the previous completed run?                | `GET /v1/intent/audiences/{id}/dashboard`                               |
| How has the audience changed across completed runs?           | `GET /v1/intent/audiences/{id}/trends`                                  |

These operations support organization API keys. Use an audience owned by that organization.

## Retrieve website overlap

```bash theme={null}
curl --fail-with-body --silent --show-error \
  "https://api.aws53.cloud/v1/intent/audiences/website-visitors?limit=100&offset=0" \
  -H "X-API-Key: $LEADPIPE_API_KEY"
```

The organization-wide endpoint compares the latest completed audience runs with recent identified website visitors. It deduplicates people by email hash and includes their latest audience matches. This is an overlap result, not a list of every website visitor or every Orbit contact.

Read the response `state` before interpreting an empty result. `no_completed_runs` means there are no completed snapshots to compare. Inspect `lookbackDays`, `total`, `limit`, and `offset` in the generated reference when building reporting and pagination.

For one visitor's topic history, use the 64-character SHA-256 identifier required by the path and optionally scope with `audienceId`. Topic history describes matches in audience runs; it does not expose a person's full browsing history.

## Compare completed runs

The audience dashboard compares the latest completed run with the previous completed run. Trends provide chronological metrics across completed runs. Keep run dates in reports so readers know which snapshots were compared.

A preview, a current audience definition, and a completed run can describe different populations. Updating an audience config affects future runs rather than rewriting older results.

Use the generated references under **Visitor overlap and analytics** for exact parameters and response fields. See [Audience runs](/orbit-api/daily-runs) to produce a new snapshot.