> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/abm/demandbase.md).

# Demandbase

HockeyStack’s Demandbase integration ties anonymous visitors that land on your website to their companies, including company firmographics, Demandbase intent data, Demandbase stage, and Demandbase ICP fit. This data is automatically connected to any other company-related data from your CRM, marketing automation, LinkedIn Ads Impressions, and more.

***

#### Connecting to Demandbase

If you are already a Demandbase user, our tracking script can automatically leverage this so you don't need to do any additional setup to connect Demandbase.

***

#### Property List Pulled from Demandbase

* `_company_domain_`
* `_company_name_`
* `_company_annual_revenue_`
* `_company_country_`
* `_company_number_of_employees_`
* `_company_industry_`
* `_demandbase_confidence_`
* `_demandbase_stage_`
* `_demandbase_intent_score_`
* `_demandbase_profile_score_`
* `_demandbase_profile_fit_`

***

#### Reverse IP Lookup

With Demandbase’s reverse IP database, you can identify the companies visiting your website and track their journeys:

You can also segment these journeys (and all other reports) by company tiers, segments, and additional properties from Demandbase and your CRM.

***

**Pulling in Demandbase Display Data**

If you would like to pull in Display data from Demandbase into HockeyStack you can use Data Stream to push that Display data into your data warehouse.

Once that data is in your data warehouse, we can import it into HockeyStack.


---

# 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.hockeystack.com/integrations/abm/demandbase.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.
