> For the complete documentation index, see [llms.txt](https://docs.guideflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guideflow.com/help/analytics/ai-account-reveal.md).

# AI Account Reveal

Identify anonymous visitors on your interactive demos!

Guideflow's integration with Clearbit AI B2B data empowers you to gather detailed personal and company data about your demo viewers, offering essential insights to enhance your demo presentations.

Say goodbye to unidentified leads, and get ready to elevate your demos!

{% hint style="info" %}
You don't need a Clearbit account to reveal your viewer's data and identify your lead with our account reveal feature.
{% endhint %}

Here’s how to seamlessly integrate with Guideflow’s Account Reveal feature, which enriches viewers' data with Clearbit's company information automatically:

{% @guideflow/guideflow-embed requestedUrl="<https://app.guideflow.com/player/lpx9076t4p>" %}

* Activate account reveal with the Clearbit integration: enable this feature in your integration tab with just one click.
* Open your analytics tab: explore enriched company data about your demo viewers directly through the Analytics Dashboard.


---

# 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.guideflow.com/help/analytics/ai-account-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.