Clearbit Enrichment Destination

Clearbit Enrichment 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.

This document was last updated on April 20th, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Use Cases

Getting Started

The first step is to make sure Clearbit Enrichment supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

📱 Device-based
☁️ Cloud-based
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Clearbit Enrichment” within the Destinations Catalog and confirm the Source you’d like to connect 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.

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.


If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('pixar123', {
  email: ""

When you call identify with a userId and email trait - the latter must be present for Clearbit Enrichment to function properly - we’ll send the Segment spec to Clearbit so that they can enrich your data. Once Clearbit enriches your data, they will send back a new identify call to your Segment source (Clearbit will have 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.


Clearbit Enrichment data is not populating

Please double check that you have entered the secret key, not the public key Clearbit provides.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.


Enter your secret key (prepended with sk_) associated with your Clearbit account.

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!