> 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/forms/website-tracking.md).

# Website tracking

Use Website tracking to collect configured website activity, review detected forms, and identify visitors through your connected sources.

**Open Website tracking.** Review the domains and pages you want to track before installing the snippet.

## Install the tracker

Copy the **Tracker snippet** from your workspace and install it before `</body>` on the intended pages.

Add your **Allowed domains**. The tracker allows subdomains of a listed domain. This differs from external form connections, which use exact approved origins.

Add **Paths never tracked** for pages you want excluded.

## Review behavior

| Setting                                          | What it controls                                                                         |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------- |
| **Tracker enabled**                              | Whether the installed snippet collects activity.                                         |
| **Review new forms before they start workflows** | Whether newly detected forms require review.                                             |
| **Open scheduler automatically**                 | Whether a returned scheduler opens over the page.                                        |
| **Enrich before submit**                         | Pre-submit matching and enrichment for a known email using the configured primary chain. |
| **Reveal companies behind anonymous visitors**   | Company identification through the connected Clearbit Reveal source.                     |

Review the configured behavior and your site's consent integration with the person who owns your website tracking setup.

## Review detected forms

Open the detected-forms view. Accept forms intended for your process, ignore unrelated forms, and review changed field names before accepting a new reference.

Use the re-scan controls when you need to discover forms on additional pages. Check page restrictions and **Rename captured fields** when a website field needs a consistent lead-field name.

Detecting a form does not by itself finish a routed scheduling setup. Confirm that the intended workflow is published, the captured fields match its trigger, and the returned response is handled.

Use an explicit [external form connection](/forms/existing-forms.md) when you need a reviewed field contract and confirmed original-submission handoff.

## Identify a known visitor

After the visitor identifies through your own site, use the supported call:

```javascript
window.distro.tracker.identify("alex@example.com");
```

Call it only with the visitor's known email. Visitor identified workflows depend on the selected identity conditions.

Company reveal needs its provider connection. **Person reveal (Vector)** has a separate receiving URL and provider setup shown in the workspace.

## Changing the tracker key

**Rotate key** retires the old snippet and receiving credentials. Update the installed snippet and connected receiving URLs afterward.

Review recent visits and workflow Logs to confirm the intended activity is arriving.

## Provider forms, consent and early enrichment

Use the dedicated guides for [HubSpot forms](/forms/hubspot.md), [Marketo forms](/forms/marketo.md) and [Pardot or other embeds](/forms/pardot.md).

Review [Consent and capture exclusions](/forms/privacy.md), [Browser storage](/forms/storage.md) and [Pre-submit enrichment](/data-and-integrations/pre-submit.md). The tracker’s analytics/marketing consent API controls a combined state; it is not two independent category gates.

For missing captures or scheduling, see [Form troubleshooting](/forms/troubleshooting.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/forms/website-tracking.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.