> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/guides/website-intent.md).

# Turn website intent into an owner alert

Use visitor identification to alert the team about relevant activity without inventing a person's identity.

## Prepare

Install the tracker on allowed sites and connect the supported identification provider. Define the pages and signals that matter, such as a pricing visit from an existing target account.

## Build

1. Start with **Visitor identified**.
2. Inspect whether the event identifies a person email, a company or both.
3. Match the company or person to the CRM.
4. Apply the owner or territory policy.
5. Check meaningful visit context.
6. Notify the owner with the company, page and known identity context.

An anonymous company identification should follow a company-alert path. Start personal follow-up only when you have a usable person identity and the appropriate audience decision.

## Handle No match

Send unknown companies to a measured review path or end the run. Do not automatically create a named person from an IP-to-company result.

## Test

Use a known company, a person-identification event, a no-match visit and a provider failure. Check allowed domains and consent behavior in the actual website environment.

Inspect the source payload and delivered alert in a controlled live test. A provider connection alone does not prove that visitors are being identified.

See [Visitor reveal](/integrations/visitor-reveal.md), [Vector](/integrations/vector.md) and [Tracker privacy](/forms/privacy.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 dynamically by asking a question.

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

```
GET https://docs.distro.so/guides/website-intent.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 `build a script that syncs our docs to a CMS` 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.