Segment

LiveAPI Key

Analytics

Overview

Send ClearView company identification events directly into your Segment analytics pipeline. When ClearView identifies a company visiting your site, it automatically fires track() and identify() calls to Segment, enriching your downstream tools like Mixpanel, Amplitude, BigQuery, and hundreds of other destinations.

What Gets Synced

  • Identify calls - Company profile data (name, domain, industry, size) sent as traits
  • Track calls - Events like company identified, page views, and hot leads with full properties
  • Real-time delivery - Events are sent the moment ClearView identifies the visitor

Supported Events

EventDescription
company.identifiedFires when a new company is identified visiting your site
page_viewFires on every tracked page view with company context
lead.hotFires when a visitor is classified as a hot lead

Prerequisites

  • A Segment workspace with at least one source configured
  • A Node.js source Write Key from Segment
  • ClearView tracking script installed on your site

Setup Guide

1

Create a Node.js source in Segment

Log into your Segment workspace and navigate to Sources > Add Source. Search for "Node.js" and select it. Give the source a name like "ClearView".

2

Copy your Write Key

After creating the source, go to Settings > API Keys. Copy the Write Key displayed on the page.

Keep your Write Key secret

Your Write Key allows sending data to your Segment source. Never expose it in client-side code or public repositories.
3

Configure in ClearView

Go to ClearView Dashboard > Integrations > Segment. Paste your Write Key into the writeKey field.

4

Select your events

Choose which ClearView events should trigger Segment calls. We recommend enabling all three: company.identified, page_view, and lead.hot.

5

Test the connection

Click the Test button to send a sample event. Then check your Segment source debugger to confirm the event arrived.

Configuration Fields

FieldTypeDescription
writeKey
SecretYour Segment source Write Key. Found under Sources > [Source] > Settings > API Keys.

Data Mapping

ClearView FieldSegment PathCall Type
Company Nametraits.company.nameidentify
Domaintraits.company.domainidentify
Industrytraits.company.industryidentify
Employee Counttraits.company.employeesidentify
Lead Scoreproperties.leadScoretrack
Page URLproperties.urltrack
Visitor Countryproperties.countrytrack

Example Payloads

When a company is identified, ClearView sends both an identify and a track call to Segment:

Track Call

track_event.json
json
{
"type": "track",
"event": "Company Identified",
"userId": "company_abc123",
"properties": {
"companyName": "Acme Corp",
"domain": "acme.com",
"industry": "Technology",
"employees": 250,
"leadScore": 87,
"url": "https://yoursite.com/pricing",
"country": "US",
"source": "clearview"
},
"timestamp": "2026-03-25T14:32:00.000Z"
}

Identify Call

identify_event.json
json
{
"type": "identify",
"userId": "company_abc123",
"traits": {
"company": {
"name": "Acme Corp",
"domain": "acme.com",
"industry": "Technology",
"employees": 250,
"plan": "enterprise"
},
"leadScore": 87,
"firstSeen": "2026-03-20T08:15:00.000Z",
"lastSeen": "2026-03-25T14:32:00.000Z"
},
"timestamp": "2026-03-25T14:32:00.000Z"
}

Troubleshooting

Events not appearing in Segment debugger

Verify your Write Key is correct and the source is enabled in Segment. Check that the events you selected in ClearView match what you expect to see. Events may take up to 60 seconds to appear in the debugger.

Downstream destinations not receiving data

Ensure your Segment destinations are connected and enabled. Check for any event filtering or sampling rules that might exclude ClearView events. Verify the destination supports the event types being sent.

Duplicate identify calls

ClearView deduplicates company identifications within a session. If you see duplicates, check that you do not have multiple ClearView tracking scripts on the same page.

Need Help?

Our team is here to help you get the Segment integration running smoothly.

Contact Support