> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/hubs-docs/integrations-hub/integrations/clearbit.md).

# Clearbit

Enrich demo viewers data on Storylane with personal/company info from Clearbit.

The Storylane and Clearbit integration empowers you to gather personal and company data about your demo viewers, offering you valuable insights to enhance your demos. Say goodbye to unknown leads and get ready to supercharge your demos!

*(Note: you don't need a Clearbit account. You just need to have an active Storylane account)*

### **How to Integrate (Introducing Account Reveal)** 

With the Account Reveal feature, you can enrich viewers' data with company info from Clearbit, automatically, without a Clearbit account.

Therefore, enriching your demo viewers' data with Account Reveal is incredibly simple:

1. Enable Account Reveal: Activate in [Settings](https://app.storylane.io/team/settings?tab=config) for your demos with a single click.
2. Access Insights: View enriched company data about your demo viewers directly in the [Analytics Dashboard](https://app.storylane.io/analytics/activity).

{% @storylane/embed subdomain="app" linkValue="dde8dt4xnhlb" url="<https://app.storylane.io/share/dde8dt4xnhlb>" %}

{% hint style="info" %}
Have questions or need help? No problem, we'd be happy to help. Simply reach out to us - <support@storylane.io>.
{% endhint %}


---

# 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.storylane.io/hubs-docs/integrations-hub/integrations/clearbit.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.