Bring every customer signal
together
Connect product usage, CRM data, billing events, support history, customer calls and market signals all in one view.
Connect your data without the hassle
Get up and running quickly without giving up control over your data.
- 01
Pick the sources
Bring in the tools your team already uses.
- 02
Scope the access
Choose exactly what data Clearplane can access.
- 03
Unify the data
Bring your customer data together in one place.
Integrations
Explore every integration included in your plan.
Showing 143 integrations
CRM & billing
Where the account, its owner, its contract, and its renewal date already live.
Chargebee
Subscriptions, plan changes, and renewal terms per account.
HubSpot
Companies, owners, deals, and renewal dates, joined to each score.
Salesforce
Accounts, owners, opportunities, and renewal dates, read to join every score to its account.
Stripe
Subscriptions, invoices, and failed payments per customer.
Product analytics
Feature adoption and active use, for products whose usage lives in the app as well as the API.
Amplitude
Events and cohorts per account, through the export API.
Heap
Autocaptured events, rolled up per account.
LaunchDarkly
Flag rollouts per account, so a drop can be checked against a release.
Mixpanel
Events and group profiles, read per company.
PostHog
Events and group analytics per organisation.
Conversation intelligence
Calls with the account, read for the risks, competitors, and commitments raised on them.
Chorus
Recorded calls per account, read for the topics and objections that come up.
Fathom
Call recordings and their summaries, matched to accounts by who attended.
Fireflies.ai
Meeting transcripts matched to accounts by attendee domain, read for topics and action items.
Gong
Calls and deal activity per account, with the risks and competitors raised on them.
Granola
Meeting notes, matched to the account on the calendar event they were taken in.
Otter.ai
Meeting transcripts and summaries, matched to the account on the invite.
Support
Tickets and threads, read for volume and topic — never as a stand-in for health.
Help Scout
Conversations per customer, with first-response times.
Intercom
Conversations per company, with the topics that recur.
Zendesk
Ticket volume, priority, and topic per organisation.
Customer feedback
Surveys, scores, and feature requests, so what an account says sits beside what it does.
Canny
Feature requests and votes per company, with the status of each.
Chattermill
Feedback themes and sentiment per account, from the sources Chattermill already unifies.
Enterpret
Feedback themes per account, drawn from every channel Enterpret already reads.
Pendo Listen
Feedback and ideas per account, beside the product usage Pendo already sees.
Qualtrics
Survey responses and NPS per account, from the surveys you choose.
SurveyMonkey
Survey responses matched to accounts by respondent domain.
UserVoice
Feedback and feature requests per account, with who raised them.
Community
Where customers ask each other first, read for who is active and what keeps coming up.
Bettermode
Community posts and engagement, mapped to each member's account.
Circle
Posts and member activity, mapped to the accounts those members belong to.
Common Room
Community and social activity already matched to companies, read per account.
Discord
Community threads, mapped to the accounts whose members start them.
Discourse
Topics and replies per account, mapped from the members who post them.
Gainsight Customer Communities
Questions, ideas, and replies, mapped to the accounts whose members post them.
Higher Logic
Community participation per member, rolled up to the account.
Customer engagement
The campaigns and messages an account has already received, so a quiet account can be told apart from an unreached one.
Adobe Marketo Engage
Program membership and engagement per lead, rolled up to the account.
Braze
Canvas and campaign engagement per user, rolled up to the account.
Customer.io
Campaigns and messages sent per person, rolled up to the account they belong to.
HubSpot Marketing Hub
Email engagement and campaign touches per company, beside its deals.
Iterable
Campaign sends and engagement per user, rolled up per account.
OneSignal
Push and in-app message delivery and opens, per account.
Messaging & meetings
Where a flag goes once it is raised, and where the renewal call sits on the calendar.
Calendly
Booked calls matched to accounts by the invitee's domain.
Gmail
Flags and renewal briefs, delivered to the account owner's inbox.
Google Calendar
Renewal and review calls read off the calendar, so the brief lands that morning.
Google Meet
Account calls matched to the account on the invite.
Microsoft Outlook
Meetings on the Outlook calendar, so a brief arrives before each account call.
Microsoft Teams
Flags posted to the channel the account team works in.
Slack
Flags posted to the account owner's channel, with the metric that moved attached.
Zoom
Scheduled account calls, so the brief is attached to the meeting it is for.
Projects & docs
Where the work on an account is tracked, and where what was agreed is written down.
Airtable
Account trackers kept in a base, read table by table.
Asana
Account plans and their open tasks, per customer project.
Bitbucket
Deploys and pull requests, so a change in usage can be checked against a release.
ClickUp
Tasks tagged to an account, laid on its timeline.
Confluence
Runbooks and account notes, from the spaces you share.
GitHub
Issues and releases that name an account, laid beside its metrics.
GitLab
Deploys and issues, so a drop can be checked against what shipped.
Google Docs
Account plans and call notes, from the docs you share.
Google Drive
Contracts and QBR decks, from the folders you share.
Google Sheets
The spreadsheet a team already tracks accounts in, read as a source.
Jira
Issues per account, from the projects you select.
Linear
Issues linked to an account, so a flag shows what engineering already has open.
Notion
Account plans and QBR notes, from the pages you share.
Workflow automation
Hand a flag to a workflow your team already runs, and read back what it returns.
Make
Flags passed to the scenarios your team already runs, and their results read back.
MuleSoft
Flags published to the integration flows MuleSoft already runs.
n8n
Flags sent to your n8n workflows, and the data they return read as signals.
Tray.ai
Flags passed into your Tray workflows, and what they return read back.
Workato
Recipes triggered by a flag, and the events they send back, per account.
Zapier
Flags handed to the Zaps your team already runs, and events sent back as signals.
Customer data platforms
The identity and event streams you already route, and the audiences you already sync, taken as they are.
Fivetran Activations
Formerly Census: the audiences and syncs you already define, read per account.
Hightouch
The audiences and syncs you already model, read where Hightouch defines them.
mParticle
Event and identity data per user, attributed to accounts through their profiles.
RudderStack
Event streams and group calls, attributed to accounts by group id.
Salesforce Data 360
Formerly Data Cloud: unified profiles and calculated insights, read per account.
Segment
Track and group calls, attributed to accounts by group id.
Treasure Data
Unified customer profiles and their segments, read per account.
Warehouses & BI
Usage already modelled in tables, read by column on a schedule through a read-only role.
Amazon Redshift
Usage schemas read through a read-only user, joined on the account id.
Athena
Usage tables in your data catalogue, queried through a workgroup scoped to them.
Azure Postgres
A read-only role on the flexible server, joined on the organisation column.
Azure SQL Database
Usage tables read by a contained user with SELECT on the schemas you pick.
BigQuery
Tables and views read by a service account scoped to one dataset.
ClickHouse
Event tables aggregated per account with read-only queries.
Databricks
Delta tables read through a SQL warehouse and a scoped token.
dbt
Your modelled usage marts, read where dbt already builds them.
Google Cloud PostgreSQL
A read-only role through the Cloud SQL connector, for usage and plan tables.
Looker
Explores and saved Looks, read as per-account metrics.
Metabase
Saved questions, read on a schedule as per-account metrics.
MongoDB
Collections read per organisation id, by a read-only user.
MotherDuck
Usage tables read with a read-only token, joined on your account column.
MySQL
A read replica, for the tables that record usage and plans.
PostgreSQL
A replica or a read-only role, for usage and plan tables.
RDS PostgreSQL
A read replica and a read-only role, for usage and plan tables.
SAP HANA
Calculation views read by a technical user with SELECT on the schemas you share.
Snowflake
Usage tables read through a read-only role, joined on your account column.
SQL Server
A read-only login on a replica, for the tables that record usage and plans.
Supabase
Postgres tables read with a scoped role, joined on the organisation column.
Metrics & observability
Where the usage signal starts: call volume, error rates, latency, and quota headroom, per account.
Amazon CloudWatch
Metrics by dimension, through a cross-account role scoped to the namespaces you pick.
Datadog
Metrics and monitors by account tag, through a read-only API key.
Elasticsearch
Aggregations over log indices, grouped by the field that names the account.
Grafana
The panels your team already trusts, read as per-account signals.
New Relic
Metrics and error events by account attribute, queried with NRQL.
OpenTelemetry
Metrics and traces over OTLP, attributed by a resource attribute you already set.
PagerDuty
Incidents on the services an account depends on, laid on its timeline.
Prometheus
Counters and histograms by tenant label, queried read-only with PromQL.
Sentry
Error volume and new issues per organisation, attributed by tag.
Web frameworks
The client SDK in the app your customers use, so route and session context arrives beside the API traffic.
Angular
An injectable service that attributes routes and sessions to the signed-in account.
Astro
Middleware that labels pages and endpoints with the signed-in organisation.
Next.js
Middleware and a client provider that label pages and route handlers with the signed-in organisation.
Nuxt 3
A module that labels pages and server routes with the signed-in organisation.
React
A provider that attributes each session and route to the signed-in account.
Remix
Loaders and actions labelled with the signed-in user's account.
SolidJS
A provider that attributes routes and sessions to the signed-in account.
Static HTML
One script tag that attributes page views to the account once a visitor signs in.
SvelteKit
A server hook that labels pages and endpoints with the signed-in organisation.
TanStack Start
Middleware that labels routes and server functions with the signed-in organisation.
Vue 3
A plugin that attributes routes and sessions to the signed-in account.
Server frameworks
Where attribution does not exist yet: one middleware in the request path tags each call with the account it came from.
ASP.NET
Middleware in the ASP.NET Core pipeline that tags each request with its tenant.
Django
Middleware that tags views and API calls with the request's organisation.
Express
Middleware that labels every request with the account it came from.
FastAPI
A dependency that labels each request with the authenticated tenant.
Fastify
A plugin that labels every route with the account the request came from.
Flask
An extension that tags views and API calls with the request's organisation.
Go Gin
Middleware that labels every handler with the account the request came from.
Hono
Middleware that tags each request with its tenant, on whichever runtime serves it.
Laravel
Middleware that tags each route and API call with the authenticated team.
Phoenix
A plug that tags controller and API traffic with the current account.
Ruby on Rails
Rack middleware that tags controller traffic with the current account.
Spring
A filter that tags each request with the tenant resolved from its credentials.
API gateways & proxies
Tag requests once at the edge, and every service behind the gateway is attributed without a code change.
Apigee
API proxy analytics per developer app, joined to the account that owns the app.
AWS API Gateway
Access logs and usage plans read per API key, joined to the account that holds it.
Azure API Management
Requests per subscription, read from the gateway's analytics and joined to the account.
Envoy
Access-log fields read per tenant header, with no change to the request path.
Gravitee
API analytics per application and plan, joined to the account that subscribes.
HAProxy
Log fields captured per tenant header, where the proxy already writes them.
Kong
A plugin that tags each request with its consumer, and counts calls and rejections.
KrakenD
Telemetry per tenant header, exported by the gateway with no change to the endpoints.
NGINX
Access-log fields read per tenant header, from the proxy already in front of the API.
Traefik
Access logs and metrics read per tenant header, with no change to the routes.
Tyk
Analytics per API key, read from the gateway and joined to the account holding the key.
Serverless & edge
Where there is no long-lived process to hold a middleware, a wrapper does the same job per invocation.
AWS Lambda
Invocations and throttles per function, joined to the account that owns them.
Azure Functions
A wrapper that tags each trigger with the tenant that caused it.
Cloudflare Workers
A wrapper around the fetch handler that tags each request with its tenant.
Deno Deploy
A wrapper around the request handler that tags each call with its tenant.
Google Cloud Functions
A wrapper that tags each invocation with the account in its request.
Vercel Functions
A wrapper that labels each invocation with the signed-in organisation.
AI assistants
Ask about any account from the assistant your team already works in.
ChatGPT
The same questions from ChatGPT, answered from your book's own numbers.
Claude
Ask about an account from Claude, with the metric behind every answer.
Integration questions
Clearplane is designed to get you connected in a few hours. Connect your sources, scope the data you want to bring in, and start building your customer view. Engineering involvement is mainly needed for custom or non-standard data sources.
Absolutely. Implementation support is included. Our team works alongside yours to connect your data, configure your scores and playbooks, and make sure you're set up to get value quickly.
Clearplane connects to the systems across your customer stack, including CRM, product usage, billing, support, calls, data warehouses, and engagement tools. It also supports custom data sources, so you're not limited to what's in the integration catalog.
You choose exactly which data sources Clearplane can work with. Bring in customer records, product usage, billing, support activity, engagement, and other signals with fine-grained access.
Clearplane keeps customer data current as new activity comes in, so your scores, signals, and workflows respond to what is happening now rather than an outdated snapshot.
No. You don't need to complete a major data cleanup before getting started. Clearplane works across your existing sources and brings the available customer context together, even if your data is incomplete or inconsistent across systems.
Clearplane connects your sources, matches records from different systems to the same customer, and organizes everything into one live view.
Yes. Clearplane can work with your existing warehouse alongside your other customer systems. You don't need to replace your current data infrastructure.
Clearplane handles the ongoing connection and keeps your customer data flowing, so your team doesn't have to maintain a collection of custom pipelines and scripts.
Clearplane is currently under SOC 2 Type II observation and is built with controls around how customer data is connected, accessed, and used. Clearplane can also be self-hosted for teams that need to keep data within their own infrastructure.
Clearplane
Drive more revenue from
existing customers
Surface revenue opportunities by connecting product usage, account activity, engagement, and market signals.