> 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-visitors.md).

# Website visitors to outbound

Turn an identified website visitor into outbound - enrich, check fit, assign a rep, and start a sequence.

Distro's tracker identifies visitors when they give an email (a form, the scheduler, or an identify call) or when their company is revealed from their network. The **Visitor identified** trigger starts a workflow that enriches the person, checks fit, assigns a rep, and adds them to a sequence.

## Which signal to use

|                | Identified by email                | Identified by company                              |
| -------------- | ---------------------------------- | -------------------------------------------------- |
| What you know  | The person                         | The company only                                   |
| Good for       | Enrolling the person in a sequence | Alerting the account owner, reviewing new accounts |
| **Start when** | A visitor identifies by email      | A visitor's company is revealed from their network |

## Before you start

Install the tracker and add your site under **Website tracking**; see [Website tracking](/forms/website-tracking.md). You also need an enrichment chain, Salesforce or HubSpot, an outbound queue, and your sequencing tool connected.

## Build the workflow

{% stepper %}
{% step %}

### Start on identified pricing-page visitors

Choose **Visitor identified**. Set **Start when** to identify by email, **Website** to your domain, and **Page URL contains** to `/pricing`.
{% endstep %}

{% step %}

### Enrich and keep visitors who fit

Add **Enrich Lead**, then **Branch** `Fit`: the visitor's email **Is present**, and the lead company's **Headcount** is **Greater than** 200.
{% endstep %}

{% step %}

### Known people keep their owner

Add **Match Salesforce Record** on `Lead` by email. On **Matched**, **Notify in Slack** your visitors channel with the page they viewed.
{% endstep %}

{% step %}

### Assign, create, and sequence new people

On **Not matched**, **Assign from Queue** with `Outbound SDRs`, **Create Salesforce Record** a `Lead` owned by the assignee, then **Add to Outreach Sequence**.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Add to Outreach Sequence** sends from the mailbox you choose on the step, not from the assigned rep's mailbox. To send as the routed rep, use a sequence whose senders rotate in the tool, or **Enroll in HubSpot Sequence** with the earlier assignee as **Sender**. See [Routed leads to sequences](/guides/sequences.md).
{% endhint %}

## Alert account owners from company reveals

Start with **Visitor identified** set to company reveals and a **Page URL contains** filter. Then **Enrich Lead** the company, **Match Salesforce Record** on `Account` by domain, and post to your account team's channel. Create accounts only for companies that pass your fit rules.

## What to expect

Not every visitor is identified: home networks, mobile data, and VPNs often stay anonymous. Keep **Match Salesforce Record** before **Assign from Queue**, so a person identified twice isn't routed or enrolled twice.


---

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