---
title: "Account Identification for Web Visitors"
source_url: https://help.chilipiper.com/hc/en-us/articles/49793334740499-Account-Identification-for-Web-Visitors
article_id: 49793334740499
updated_at: 2026-04-23T12:27:44Z
---

## Who can use this feature?

Available on All Products or Experiences

Available to Only Admins

[Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub)

Account Identification makes your Chili Piper Chat experience account-aware. By connecting a supported de-anonymization provider such as **6sense** , **Bombora** , or **Leadfeeder** , you can identify the company behind anonymous website visitors and personalize their chat experience in real time.

This allows you to route high-value accounts to premium booking experiences while showing different journeys to smaller companies — without waiting for visitors to fill out a form.

* * *

## Table of Contents

  * Prerequisites
  * Enable Account Identification
  * Configure De-anonymized Company Fields
  * Use Account Identification in Chat Journeys
  * Limitations



* * *

## Prerequisites

Before enabling Account Identification, confirm the following requirements:

  * You have one of the following:
    * An active **6sense** or **Bombora** subscription with company identification enabled, with the provider's web tag installed on pages where **Chili Piper Chat** runs
    * A **Leadfeeder** account with an API key (bring-your-own), **or** access to **Leadfeeder through Chili Piper** (Limited Beta)
  * Chili Piper Chat is already deployed on your website



**Note:** The de-anonymization logic is embedded in the Chili Piper Chat script. For **6sense** and **Bombora** , no additional code changes are required once your provider's tag is installed. **Leadfeeder** does not require a web tag — it connects via API key (bring-your-own) or directly through Chili Piper.

* * *

## Enable Account Identification

  1. Navigate to **Command Center** and select **Integrations** from the left menu. 
  2. Open the **Built-In** tab and scroll to the **Deanonymization Data Provider** section.
  3. Locate your provider (**6sense** , **Bombora** , or **Leadfeeder**) and click **Enable.**
     * For **Leadfeeder** , you will see two options:
       * **Connect your own Leadfeeder account** — paste the **API key** from your **Leadfeeder** account and click **Connect**. Usage is billed by **Leadfeeder** according to your contract with them.
       * **Use Leadfeeder through Chili Piper** — available in Limited Beta; no separate account or API key is required.  
![image \(19\).png](https://help.chilipiper.com/hc/article_attachments/51042150721427)



Once enabled, Chili Piper can begin populating **De-anonymized Company fields**. Make sure the provider’s script is installed on your website so visitor data can be captured.

**Note:** Integrations are disabled by default. You can enable any combination of the supported providers (**6sense** , **Bombora** , and/or **Leadfeeder**) at the same time.

* * *

## Configure De-anonymized Company Fields

After enabling a provider, navigate to:

**Command Center → Data Fields → De-anonymized Company**

This section allows you to manage the company data captured from your provider.

![image \(16\).png](https://help.chilipiper.com/hc/article_attachments/49793708137491)

Chili Piper includes several pre-mapped fields out of the box, such as:

Field | Description  
---|---  
Name | Identified company name  
Website | Company domain  
Industry | Industry classification  
Employee Count | Estimated company size  
Annual Revenue | Estimated company revenue  
Country | Company headquarters location  
  
Additional fields may be available depending on your provider.

### Set the Waterfall Sequence

If multiple providers are enabled, you can control which provider takes priority for each field.

  1. Select a field in the **De-anonymized Company** tab
  2. Under **Waterfall Sequence** , click **Add Deanonymization Data Source**
  3. Select the provider
  4. Drag providers to reorder priority

![image \(20\).png](https://help.chilipiper.com/hc/article_attachments/51042136387091)

Chili Piper uses the value from the highest-priority provider that returns data.

* * *

## Use Account Identification in Chat Journeys

After configuration, De-anonymized Company data can be used in **Chat Journey Audience Rules** to deliver different experiences based on company attributes.

  1. Open the Chat journey you want to configure
  2. Click **Trigger**
  3. Select **Show to a specific audience**
  4. Create or select a rule using **De-anonymized Company fields**

![Screenshot 2026-04-21 at 11.51.02.png](https://help.chilipiper.com/hc/article_attachments/51042150725651)![image \(17\).png](https://help.chilipiper.com/hc/article_attachments/49793708149395)

**Note:** If no provider is enabled, the option to target de-anonymized visitors will not appear. You’ll see a link to enable a supported provider directly from the Journey builder.

**Example use cases:**

  * Route enterprise visitors to an immediate meeting booking flow
  * Show localized journeys based on visitor country
  * Prioritize high-value target accounts with personalized messaging



* * *

## Limitations

  * Account Identification for Chat is currently in **Beta**
  * Requires one of the following: an active **6sense** or **Bombora** subscription, a **Leadfeeder** account (connected via API key), or access to **Leadfeeder through Chili Piper** (Limited Beta)
  * Identification relies on IP-based de-anonymization; industry match rates average around **30%**
  * Currently supported only for **Chat**
  * Support for **Distro, Concierge, and Orchestrator** is planned for future releases