> 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/integrations/vector.md).

# Vector visitor identification

Connect Vector identification events to a workflow when your Vector setup supports the Distro receiving endpoint.

## Configure the connection

Create a workflow using **Visitor identified** and obtain the receiving details from the Distro setup. Configure the corresponding Distro destination in Vector using the workspace-specific details supplied to you.

The provider's website pixel and identification configuration are managed in Vector. Use Vector's setup instructions or support for your account.

## Map the event

Inspect a real sample event and map its person, company and visit fields. An email is a person identifier; an identified company alone should follow a company-intent path.

Match the lead to your CRM before routing by owner or starting follow-up. Define No match and missing-email branches.

## Verify

Make a controlled visitor-identification test and confirm that a run appears in Distro. Review the source, identifiers, attribution and deduplication behavior in Logs.

If no run starts, check the destination details, authorization, workspace activation and provider delivery. A configured pixel does not prove that a receiving workflow is On.

See [Website intent](/guides/website-intent.md) and [Inbound webhook secret](/settings/inbound-secret.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/integrations/vector.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.