# Deanonymization

Deanonymization identifies anonymous visitors interacting with Spara by resolving their identity through a third-party data vendor (currently Vector). When a visitor lands on a page where Spara's JS snippet is installed, Vector attempts to match them to a known person or company using privacy-safe data sources — giving your chat agent context before the first message is sent.

Important: Deanonymization works at the chat-widget level by default. It is not a site-wide visitor tracking tool unless your organization is configured for “All Site Traffic” mode.

### How it works

1. A visitor lands on a page where Spara is active.
2. Spara sends visitor data to Vector’s identity resolution API via a lightweight pixel.
3. Vector attempts to match the visitor to a known contact or company in its dataset.
4. If matched, the agent can reference those details (name, company, job title, etc.) in its prompt context.

The visitor’s experience is unchanged — but the agent now has a head start on who it’s talking to.

### Trigger modes

Deanonymization can be configured at the organization level by a Spara admin:

| Mode                    | When it runs                                        | Notes                                                           |
| ----------------------- | --------------------------------------------------- | --------------------------------------------------------------- |
| Off                     | Never runs                                          | <p><br></p>                                                     |
| On engagement (default) | When a visitor sends at least one message in chat   | Default for all organizations                                   |
| All Site Traffic        | On every page visit, regardless of chat interaction | Additional charge. Coordinate with your Spara point of contact. |

### What data is returned

When a match is found, the following fields may be populated on the lead record. Not all fields are guaranteed — availability depends on Vector’s coverage for that visitor.

| Field                    | Location             | Notes                                                      |
| ------------------------ | -------------------- | ---------------------------------------------------------- |
| first\_name / last\_name | Lead page header     | May reflect a contact match, not just the company          |
| email                    | Lead Information tab | Work email if available — not always populated             |
| company\_name            | Lead Information tab | Matched from company-level resolution                      |
| job\_title               | Lead Information tab | From contact record when matched at person level           |
| linkedin\_url            | Enrichment section   | When available in Vector’s dataset                         |
| industry                 | Enrichment section   | Company-level field; may reference domain rather than name |

Additional information on Spara's data model can be found on the [Data Model](/platform/data-model.md) page.

On the Leads detail page, the right-hand panel distinguishes between visitor-provided data (gathered in chat) and deanonymized/enriched data (vendor-sourced).

### Status icons on the lead header

A small icon next to the lead’s name signals the confidence level of their identity data:

* Green checkmark — Verified identity. The visitor provided their email directly in chat. First-party, confirmed match.
* Yellow warning triangle — Unverified. Identity came from deanonymization, not from the visitor. Tooltip: “Unverified information may be inaccurate.”
* No icon — Anonymous. No identity data available from either source.

### Accuracy and limitations

Deanonymization is probabilistic — it is not always accurate. A few things to keep in mind:

* Contact-level match rates typically range from 15–30% of US-based traffic. Company-level matches are higher. Rates depend on your visitor base and Vector’s coverage of that audience.
* Vector operates only in the United States. International visitors will not be matched. Vector is geofenced to comply with US privacy regulations.
* Email is rarely returned. Vector’s dataset does not reliably include email addresses. Collecting email through the chat conversation remains the most reliable path to email capture.
* Company-level ≠ person-level. Corporate IPs and shared networks often resolve to the company but not a specific person — name and title fields may be blank even when company is present.

### Privacy and compliance

Vector uses privacy-safe data sources and does not rely on third-party cookies. Vector is SOC 2 Type 2, GDPR, and CCPA compliant. Spara passes Vector’s data to the lead record as-is, without additional cleansing or validation.

Note: Vector requires customers to update their Privacy Policy and Consent Management Platform (CMP) to disclose the use of third-party data partners. Confirm with your Spara point of contact if you have not already done so.

### FAQ

**Can I filter leads by whether they were deanonymized?**

Yes. The Leads page includes an “Identification” filter with two options: Self-identified (visitor provided details in chat) and Deanonymized by IP address (details from Vector). Useful for segmenting outreach or evaluating hit rate quality.

**Does deanonymization work for non-chat visitors?**

Only in “All Site Traffic” mode. In the default “On engagement” mode, a visitor must send at least one message before deanonymization runs. Contact your Spara point of contact to enable this.

**Can I use deanonymized data to trigger a workflow?**

Yes. Once a lead is deanonymized, you can reference deanonymized fields in workflow conditions — for example, enrolling a visitor from a target account in an email workflow when they're identified, even if they never chatted.

**What vendor powers deanonymization?**

Spara currently uses Vector.

**What’s the difference between deanonymization and enrichment?**

Deanonymization identifies anonymous visitors using vendor data — no email required. [Lead Enrichment](/agents/chat-agents/lead-enrichment.md) takes a lead whose email is already known and layers on additional company and contact data. Deanonymization is the first guess at who someone is; enrichment fills in the full picture once you have a confirmed identity.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://docs.spara.com/agents/chat-agents/deanonymization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.