---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/clearbit-enrichment#article
headline: Clearbit Enrichment Destination
description: Connect the Segment Clearbit Enrichment destination to append real-time company and person data to Identify calls using an email or domain.
url: https://www.twilio.com/docs/segment/connections/destinations/catalog/clearbit-enrichment
inLanguage: en
dateModified: 2026-07-15T17:40:17.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Clearbit Enrichment Destination

## Destination Info

* Accepts [Identify](/docs/segment/connections/spec/identify) calls.
* In Cloud-mode, refer to it as **Clearbit Enrichment**, **Clearbit** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)

### Components

* Server

## Connection Modes

[Learn more about connection modes.](/docs/segment/connections/destinations/#connection-modes)

### Device-Mode

* web: no
* mobile: no
* server: no

### Cloud-Mode

* web: yes
* mobile: yes
* server: yes

[Clearbit Enrichment](https://clearbit.com/segment) helps customers enrich and append real-time data to an email or domain, driving growth or powering your product with social data, location, job title, company size and technology.

## Getting started

> \[!WARNING]
>
> This destination is not supported with EU Workspaces.

To set up the Clearbit Enrichment destination, follow these steps:

1. From the Segment web app, click **Catalog**.
2. Search for "Clearbit Enrichment" in the Catalog, select it, and choose which of your sources to connect the destination to.
3. In your Segment UI's destination settings, enter your Clearbit **secret** API key (note: it should start with "sk\_"). You can find this in the API section of your [Clearbit dashboard](https://dashboard.clearbit.com/api).

To verify that the destination has been set up correctly, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing Clearbit Enrichment data populate in the `identify` events – click on the specific event you're interested in to see Clearbit Enrichment traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit Enrichment traits are prefixed with `clearbit_` to ensure they don't conflict with existing traits.

## Identify

If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/segment/connections/spec/identify/) does. An example call would look like:

```js
analytics.identify('pixar123', {
  email: "carl.fredricksen@example.com"
});
```

When you call `identify` with a `userId` and `email` trait - **the latter must be present for Clearbit Enrichment to function properly** - Segment sends the Segment spec to Clearbit so that Clearbit can enrich your data. Once Clearbit enriches your data, it sends back a new `identify` call to your Segment source (Clearbit has access to your `writeKey`) with additional traits.

You can find details on what traits Clearbit Enrichment adds and exactly what will be in the enriched `identify` call on [Clearbit's site](https://segment.clearbit.com/mapping).

## Troubleshooting

### Clearbit Enrichment data is not populating

Double check that you have entered **the *secret key***, not the *public key* Clearbit provides.

## Engage

You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

## Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

| Field   | Description                                                                            | Required | Type   |
| ------- | -------------------------------------------------------------------------------------- | -------- | ------ |
| API Key | Enter your secret key (prepended with \`sk\_\`) associated with your Clearbit account. | Yes      | string |