> For the complete documentation index, see [llms.txt](https://docs.11x.ai/llms.txt).
> Use it to discover all available pages before exploring further.

# Website visitor tracking

Identify who visits your site in real time, resolved to individuals rather than just companies, then trigger outreach with full visit history before intent decays.


Website visitor tracking identifies who visits your site in real time and triggers outreach automatically, before intent decays. It resolves visitor activity to **specific individuals**, not just IP-to-company matches, and carries the **full visit history into every message** — so outreach can reference what they actually looked at.

<Callout kind="tip">
The behavioural detail is what makes this convert. A pricing-page visit and a homepage visit warrant completely different outreach, and treating them identically wastes the signal.
</Callout>

## What's captured

| Captured | Used for |
| --- | --- |
| **Which pages were visited** | Pricing versus homepage gets different treatment |
| **Full visit history** | Referenced directly in messaging |
| **Company firmographics and technographics** | Cross-referenced against your ICP |
| **Research context** | Company pages, press releases, professional profiles, recent news |

## From page view to outreach

<Steps>
  <Step title="Visitor identified in real time" icon="eye">
    Resolved to an individual where possible, rather than only to a company.
  </Step>
  <Step title="Cross-referenced against your ICP" icon="crosshair">
    Firmographic and technographic data checked for fit before anything happens.
  </Step>
  <Step title="Research runs" icon="search">
    Company pages, press releases, professional profiles, and recent news. See [deep research](/alice/deep-research).
  </Step>
  <Step title="Outreach triggers automatically" icon="zap">
    No manual review step, so intent doesn't decay while someone reads a dashboard.
  </Step>
</Steps>

## Behaviour-based treatment

Differentiate by what the visit actually signals:

| Visit pattern | Reasonable treatment |
| --- | --- |
| **Pricing page**, repeatedly | Highest intent — consider [Julian](/julian/speed-to-lead) for a call, not just email |
| **Comparison or competitor page** | Active evaluation — differentiation messaging |
| **Product or docs pages, deep** | Technical evaluator — route to the right persona |
| **Homepage only, once** | Low signal — nurture, don't push |
| **Careers page** | Usually a job seeker. Exclude. |

<Callout kind="alert">
Exclude your own team, your existing customers, and obvious non-buyer traffic such as careers-page visits. Without exclusions, this feature generates outreach to your own employees and candidates — which is a memorable way to lose internal trust.
</Callout>

## Privacy and compliance

Visitor tracking is subject to privacy law that varies by jurisdiction, including consent requirements in the EU and UK.

- 11x maintains a [website tracking privacy policy](https://www.11x.ai/legal/website-tracking-privacy-policy)
- 11x holds SOC 2 Type II and CASA Tier 3 — see [security and compliance](/help-center/overview/security-and-compliance)
- Your own cookie consent, privacy notice, and lawful basis for outreach remain **your responsibility**

<Callout kind="alert">
Involve whoever owns privacy compliance at your company before enabling this. Identifying individuals from web traffic and then contacting them has a different legal profile in the EU and UK than in the US, and it is not a decision to make inside a GTM team alone.
</Callout>

## Setup

Integration works through your existing infrastructure — CRM sync, enrichment tools, Slack, and API access. See [integrations](/integrations).

<Steps>
  <Step title="Install tracking on the pages that matter" icon="code">
    Pricing, product, comparison, and docs pages carry the most signal.
  </Step>
  <Step title="Confirm your consent mechanism" icon="scale">
    Per jurisdiction, with sign-off from whoever owns privacy.
  </Step>
  <Step title="Set exclusions" icon="ban">
    Internal traffic, existing customers, open opportunities, owned accounts, careers-page visitors.
  </Step>
  <Step title="Define ICP cross-referencing" icon="crosshair">
    So only in-profile visitors trigger anything.
  </Step>
  <Step title="Map visit patterns to plays" icon="git-branch">
    Pricing-page repeat visits and a single homepage visit should not run the same motion.
  </Step>
  <Step title="Route high intent to Julian" icon="phone">
    A repeat pricing-page visitor is worth a call, not just an email.
  </Step>
</Steps>

## Frequently Asked Questions

<Expandable title="Why are our own employees being contacted?">
Internal traffic isn't excluded. Add your own domains and office IP ranges.
</Expandable>

<Expandable title="Why are job applicants being contacted?">
Careers-page traffic isn't excluded. Exclude those paths explicitly.
</Expandable>

<Expandable title="Why are visitors resolved to companies but not individuals?">
Individual resolution isn't always possible. Treat company-level identification as the baseline and individual resolution as the upside.
</Expandable>

<Expandable title="Why is visitor volume very high and mostly irrelevant?">
ICP cross-referencing isn't tight enough. Most site traffic is not in your ICP — filter hard.
</Expandable>

<Expandable title="How do I reference a page visit without sounding intrusive?">
Reference the topic, not the surveillance. "Saw you were looking at our pricing page at 14:32" is unsettling; framing the message around the problem that page addresses is not.
</Expandable>

## Next steps

<Columns cols={2}>
  <Card title="Signals and triggers" icon="radar" href="/data/signals-and-triggers" horizontal>
    Combine visits with third-party signals.
  </Card>
  <Card title="Company and lead database" icon="database" href="/data/company-and-lead-database" horizontal>
    The firmographic layer behind identification.
  </Card>
  <Card title="Speed to lead" icon="zap" href="/julian/speed-to-lead" horizontal>
    Routing high-intent visits to a call.
  </Card>
  <Card title="Analytics overview" icon="chart-line" href="/analytics/overview" horizontal>
    Known and anonymous visitor reporting.
  </Card>
</Columns>