Clearbit Reveal Destination

Segment makes it easy to send your data to Clearbit Reveal (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Clearbit Reveal in the format they understand. Learn more about how to use Clearbit Reveal with Segment.

Our Clearbit Reveal destination code is open-source on GitHub if you want to check it out.

This destination is maintained by Clearbit. You can contact with questions.

Getting Started

All you need to turn on the Clearbit Reveal destination in Segment is your Clearbit Secret Key. This can be found in the Clearbit dashboard.


When you call page event from analytics.js, Clearbit Reveal will send back an enriched identify call from their servers. For this to work you must be using Segment’s analytics.js client-side library to make your page calls. The Clearbit Reveal back to Segment destination is a server-side destination and you will need to use your secret key. This enriched identify call will only arrive in downstream destinations that are configured to receive server-side identify events.

You can find details on what traits Clearbit adds and exactly what will be in the enriched identify call on Clearbit’s site. and full documentation on the reveal API in the docs here.

Note Clearbit Reveal attributes will not populate on every single identify event as Reveal will not have 100% match rates for your traffic. Enriched identify events will only be sent back after the first page call per visitor, not with every subsequent page call.

Troubleshooting/ FAQ

Secret Key

To set up the destination, you must enter the secret key, not the public key Clearbit provides.

How do I know if it’s working?

Check the Debugger view in your Segment Source. Assuming everything has been set up correctly, you should start seeing Clearbit data populate in the identify events – click on the specific event you’re interested in to see Clearbit traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit traits are prefixed with clearbit_ to ensure they don’t conflict with existing traits.


By default, Clearbit Reveal information will not be sent to Marketo. If you are interested in passing Clearbit data to Marketo, please reach out to Clearbit Support and Segment Success teams.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


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


Enter your API Key associated with your Clearbit Reveal account.


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!