> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.default.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Demandbase website visitor identification in Default

> How Default uses Demandbase to identify the company behind a website visit in real time: how it runs with Reveal and Clearbit Reveal, the fields it returns, when it uses credits, and how to turn it on.

Default integrates with Demandbase for website visitor identification. When someone opens a page
with **Reveal** turned on, Default can ask Demandbase which company owns the visitor's IP address
and start a workflow when it finds one. Default manages access to Demandbase, so you don't need a
Demandbase account or API key.

## Demandbase in Default at a glance

| | |
| - | - |
| What it does in Default | Identifies the company behind a website visit from the visitor's IP address, in real time. |
| Integrations category | **Website Intent**, on the **Demandbase** card. |
| Where it shows up | [Reveal](/forms/reveal) on the pages you choose in **Signals**, and the **Account Signal** workflow trigger. |
| What it needs | The Default [Pixel](/settings/pixel) on your site, **Reveal** turned on for the page, and a visit from a public IPv4 address. |
| Who supplies the data | Default. No Demandbase account needed. |
| Credits | 2 credits each time Default calls Demandbase and it identifies a company. Visits from internet service providers or home networks, and visits with no match, use no Demandbase credits. Website Intent providers are available at an additional cost. Speak to the Default Customer Success team to learn more. |

## How Demandbase works with Reveal in Default

1. A visitor opens a page where **Reveal** is on, and the Pixel reports the visit.
2. If the visitor granted analytics consent, Default looks up the visitor's IP address with every
   Website Intent provider you have on for real-time lookups: **Clearbit Reveal**, **Demandbase**,
   or both.
3. When both return a company, Default uses **Clearbit Reveal**'s result. When only Demandbase
   returns a company, Default uses Demandbase's.
4. Default starts each published workflow that uses the **Account Signal** trigger. The same
   workflow starts at most once per hour for the same company.

See [Visitor De-anonymization](/forms/reveal) for the full Reveal setup.

## Fields Demandbase returns

| Group | Fields |
| - | - |
| Company | Company name, marketing alias, website domain, industry and sub-industry, employee count and range, annual revenue and revenue range, street address, city, state, postal code, country, phone number, LinkedIn URL, and primary NAICS and SIC codes. |
| IP location | City, region, country, country code, latitude, and longitude from the IP address's registration. These describe where the IP address is registered, which can differ from the company's headquarters. |

The **Account Signal** trigger passes these fields to later workflow steps, along with the IP
address and page URL of the visit. When Clearbit Reveal's result is used instead, the fields come
from Clearbit Reveal. See [Clearbit](/settings/integrations/clearbit#fields-clearbit-reveal-returns).

## Turn on Demandbase

<Steps>
  <Step title="Open Integrations">
    Select **Settings** in the sidebar, then **Integrations** under **Workspace Settings**. Admin
    access is required.
  </Step>

  <Step title="Open Demandbase">
    Select the **Demandbase** card in the **Website Intent** category.
  </Step>

  <Step title="Turn it on">
    Turn on the switch next to the name. If the switch is unavailable, contact Default to turn
    Demandbase on for your workspace.
  </Step>

  <Step title="Turn on Reveal for your pages">
    In **Signals**, turn on **Reveal** for the pages where a visit shows intent, such as pricing or
    demo pages. See [Turn on Reveal for a page](/forms/reveal#turn-on-reveal-for-a-page).
  </Step>

  <Step title="Build a workflow">
    Create a workflow with the **Account Signal** trigger, then add steps such as a Slack alert or a
    routing step. See [Start a workflow when a visitor is identified](/forms/reveal#start-a-workflow-when-a-visitor-is-identified).

    Once you publish the workflow, Default starts it when a company is identified on those pages.
  </Step>
</Steps>

## Turn off Demandbase

Turn the switch off, and Reveal stops calling Demandbase from the next visit. Those visits use no
Demandbase credits. If Clearbit Reveal is still on, Reveal keeps identifying companies with Clearbit
Reveal alone.

Related: [Default integrations](https://www.default.com/integrations)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.