> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/collect-data/reveal.md).

# Reveal

Chord Reveal connects anonymous sessions on your site to real customer identities. It matches site visitors to enriched profiles using verified third-party data sources.

{% hint style="info" %}
Chord Reveal is in private beta. To request access, email <product@chord.co>.
{% endhint %}

{% hint style="info" %}
Chord Reveal is only available for visitors located in the United States. Visitors who access your site from outside the US can't be identified.
{% endhint %}

## What you can do with it

Much of your site's traffic comes from anonymous visitors who browse, click and even add to cart without logging in or checking out. With Chord Reveal, you can:

* Identify anonymous sessions and connect them to known users
* Power retargeting and journey orchestration
* Improve campaign attribution and funnel visibility
* Enrich your CDP with more complete customer profiles

## How it works

1. **An anonymous visitor views a page.** As with standard user identification, the visitor triggers a Page View. If the visitor can't be mapped to a known user ID, Chord checks its identity graph, which is built from licensed third-party providers, for a match.
2. **Chord matches and enriches the profile.** If the visitor is found, Chord uses high-confidence probabilistic scoring and returns the enriched profile data.
3. **Enriched data is kept separate.** It's returned in its own data table, separate from your first-party customer tables.
4. **Privacy and compliance.** All data processing follows US regulatory frameworks. Consent preferences are honored, and opt-outs are suppressed and removed from enrichment immediately.

{% hint style="info" %}
De-anonymized user data isn't merged with existing user profiles. Chord Reveal adds fields to the same anonymous ID.
{% endhint %}

### Visitor states

1. A visitor browses your site anonymously.
2. If the visitor logs in to their account, they become **Self-Identified**.
3. If the visitor doesn't log in and Chord identifies them, they become **Chord Identified**.
4. If a Chord Identified visitor later logs in, they become **Self-Identified**.

### Where to find Reveal data

When a match is made, Chord updates user records and shows the enriched identities in your existing explores. A **Chord Reveal** group label appears in the **Activities** and **Sessions** explores.

## Get started

You'll need:

* Chord CDP access
* Consent collection, through your site or email capture
* Active web tracking. See the [Collect data overview](/collect-data/overview.md).

Then:

1. Request access by emailing <product@chord.co>.
2. Check that your event coverage is complete.
3. Monitor matches in the **Activities** and **Sessions** explores.

## What to expect

Once Chord Reveal is on, you'll start to see:

* More users attributed to known IDs
* Enriched session and conversion metrics
* Larger segmentation and remarketing audiences


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chord.co/collect-data/reveal.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 `automate deployments from our CI pipeline` 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.