> 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/integrations/visitor-reveal.md). # Clearbit Reveal and Demandbase Use an IP-to-company provider to identify companies visiting your website. ## Connect a provider An admin opens **Settings → Integrations → Clearbit Reveal** or **Demandbase** and enters the appropriate API key. Clearbit Reveal is separate from legacy Clearbit person/company enrichment. Saving performs a sample public IP lookup. Reveal verification can use provider credit. Check your provider account's entitlement and usage. ## Enable website identification Install [Website tracking](/forms/website-tracking.md) on an allowed site and configure the identification source. Create a workflow with **Visitor identified** and the conditions you need. A company identification is not proof of a particular person's identity. Anonymous company visits and identified email visits have different available fields. ## Route intent Use visit context and a company match before sending an alert. See [Website intent recipe](/guides/website-intent.md) for a measured workflow that separates company signals from person follow-up. ## Troubleshoot Check allowed domains, tracker loading, consent behavior, provider connection and whether the IP has a useful company result. Mobile networks, VPNs and shared networks can return incomplete or unsuitable data. Treat No match as an expected outcome. Do not create a named person or send a personal sequence based only on an anonymous company lookup. --- # 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/integrations/visitor-reveal.md?ask=&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.