Clearbit Reveal Destination

Clearbit Reveal helps customers instantly match IP addresses with company names, and see full profiles for all site visitors. It turns your anonymous web traffic into a full company profile — complete with industry, employee count, funding details, and much more. You can find a list of the different attributes you can collect with Clearbit here. This destination is maintained by Clearbit. For any issues with the destination, please reach out to their team

This document was last updated on August 29, 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!

Getting Started

The first step is to make sure Clearbit Reveal 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.

WebMobileServer
📱 Device-based
☁️ Cloud-based

Setup within Segment:

  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Clearbit Reveal” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. In your Segment Settings UI, enter your Clearbit secret API key (note: it should start with “sk_”). You can find this in the API section of your Clearbit dashboard.

Setup within Clearbit:

  1. From your Clearbit dashboard click on the Reveal product.
  2. Click on the Segment integration tile and click to ‘Enable with Segment’.
  3. Select the source that you connected Clearbit Reveal to as a destination in the above Segment Setup instructions.
  4. CLick ‘Send Data’.

To verify that the destination has been set up correctly, send a page event that includes an IP address, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing Clearbit Reveal data populate in an identify event – click on the specific event you’re interested in to see Clearbit Reveal traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit Reveal traits are prefixed with reveal_ to ensure they don’t conflict with existing traits. Clearbit will also send a track event for ‘enrichment_provider’.

Page

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

analytics.page('Home', {
  title: 'Welcome | My Website',
  url: 'https://mywebsite.com/'
});

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 send an IP address in the context of your Page calls. Our Analytics.js library collects the IP address for you, otherwise you need to manually retrieve and set it in context.ip. The Clearbit Reveal Destination is a server-side destination so 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.

Notes

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

Troubleshooting

Clearbit Enrichment data is not populating

Please double check that you have entered the secret key, not the public key Clearbit provides. Also please check that you included an IP address in your request.

Marketo not receiving enriched data

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.


If you have any questions, or see anywhere we can improve our documentation, please let us know!