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

# Vector website visitor identification in Default

> How Default uses Vector to identify the people and companies visiting your website in batches: how the Default Pixel loads it, the People Signal trigger, the fields each identification carries, when it uses credits, and how to turn it on or off.

Default integrates with Vector to identify the people who visit your website, by name, title, and
email. The Default Pixel loads Vector on your site, and Vector sends each identified visitor to
Default in batches, about every 30 minutes. Default manages the Vector connection, so you don't need
a Vector account or API key, and there is nothing to set up on Vector's side.

## Vector in Default at a glance

| | |
| - | - |
| What it does in Default | Identifies website visitors as people, and their company when Vector can confirm it. |
| Integrations category | **Website Intent**, on the **Vector** card. |
| Where it shows up | The **People Signal** workflow trigger, the **Batched company (Vector)** trigger type, and the **De-anonymized** filter on a person's **Activity** tab. |
| What it needs | The Default [Pixel](/settings/pixel) (`index.js`) on your site, Vector turned on, and visitors who grant marketing consent. |
| When results arrive | In batches, about every 30 minutes. A person can take up to an hour to appear after the visit. |
| Where it runs | On every page the Pixel tracks, whether or not **Reveal** is on for that page. The Pixel skips pages with the `noform` meta tag and paths that contain `/login`, `/signin`, `/account`, `/checkout`, `/oauth`, or `/admin/`, so Vector does not run there. See [Turning capture off](/forms/privacy#turning-capture-off). |
| Who supplies the data | Default. No Vector account needed. |
| Credits | 3 credits for each delivery from Vector that names a person or a company. A delivery that names neither uses none. Website Intent providers are available at an additional cost. Speak to the Default Customer Success team to learn more. |

## How Vector works in Default

1. With Vector on, the Default Pixel loads Vector's script on each page it tracks, for visitors who
   grant marketing consent. Pages the Pixel skips, such as login and checkout paths, never load Vector.
2. Vector matches the visitor to a person, and to a company when it can confirm the company's domain.
3. About every 30 minutes, Vector sends Default each visitor it identified.
4. Default starts published workflows that use the **People Signal** trigger for each identified
   person, and workflows set to **Batched company (Vector)** for each identified company. A visitor
   with both a person and a company starts both kinds of workflow.
5. The identification appears on the person's record. Open the person in **People**, then the
   **Activity** tab, and filter by **De-anonymized**.

Vector sends results only for domains that are registered with Vector. If Vector is on and no People
Signal runs arrive, contact Default to check your domain.

## Vector triggers in Default workflows

Vector results start workflows through the **Website Intent Signal** trigger:

| Trigger type | How to add it | Fires when |
| - | - | - |
| **Batched person (Vector)** | Add the **People Signal** trigger. | Vector identifies the visitor as a person with an email address. |
| **Batched company (Vector)** | Add the **Account Signal** or **People Signal** trigger, then set **Trigger type** to **Batched company (Vector)**. | Vector identifies the visitor's company with a verifiable domain. |

Both trigger types take the optional **Tracked domain** and **Page URL pattern** filters. See
[Website intent signal](/workflows/triggers#website-intent-signal).

The **Account Signal** trigger's own type, **Real-time company**, uses Clearbit Reveal and
Demandbase instead. See [Clearbit](/settings/integrations/clearbit) and
[Demandbase](/settings/integrations/demandbase).

## Fields a Vector identification carries

| Group | Fields |
| - | - |
| Person | Email, first name, last name, title, LinkedIn URL, seniority, department, industry, location, and country. |
| Company | Domain, name, LinkedIn URL, and company size. |
| Visit | Page URL, page title, referrer, UTM source, medium, campaign, term, and content, first and last visit time, and the Vector segment. |

The email is the visitor's work email when Vector has one, and otherwise a personal email. Match the
person against your CRM before you create a record or route it, so a repeat visitor keeps their
existing owner.

## Turn Vector on or off

<Steps>
  <Step title="Open Integrations">
    Select **Settings** in the sidebar, then **Integrations** under **Workspace Settings**. Admin
    access is required.
  </Step>

  <Step title="Open Vector">
    Select the **Vector** card in the **Website Intent** category.
  </Step>

  <Step title="Turn it on">
    Turn on the switch next to the name. If the switch is unavailable, contact Default to turn Vector
    on for your workspace.
  </Step>

  <Step title="Build a workflow">
    Create a workflow with the **People Signal** trigger, then add steps such as a CRM match, a
    Slack alert, or a routing step. See
    [Start a workflow when a visitor is identified](/forms/reveal#start-a-workflow-when-a-visitor-is-identified).

    Once you publish the workflow, Default starts it for each visitor Vector identifies, in batches
    about every 30 minutes.
  </Step>
</Steps>

When you turn Vector off:

* The Pixel stops loading Vector's script. A browser tab that already has the Pixel open picks up the
  change within about 30 minutes.
* Any identification Vector still sends is dropped. It starts no workflow and uses no credits.

Related: [Default integrations](https://www.default.com/integrations)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.