How to integrate Unify with Clearbit
To integrate Unify with an existing Clearbit subscription, enter the Clearbit API key in Unify’s integration settings. Unify can then use that account for website visitor identification. Alternatively, Unify Intent supplies identification through Clearbit and other providers.[1]
- Connection
- API key
- Intent & identification
- Tool
- Clearbit
- Unify
- Data flow
- Website activity → Unify with Clearbit
- Account-specific configuration
At a glance
- Use the key from your existing Clearbit subscription
- Verify website collection independently
- Use the Unify Intent path if that matches your setup instead
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
The value of visitor identification depends on what the team does with the context. A sensible first workflow gives a rep enough information to decide whether the company is relevant. Keep collection checks, identification expectations, and outreach rules separate so that a missing signal does not lead to an unsupported assumption.
A good fit when
Teams with an existing Clearbit subscription, or teams comparing that path with the provider mix available through Unify Intent.
Reconsider the plan when
If no one owns the decision about which accounts deserve follow-up, assign that responsibility before expanding collection or automating outreach.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Identification path | Choose whether to connect the existing Clearbit account or use Unify Intent. |
| Observed context | Review collected visits and the account context available in your own workspace. |
| Follow-up rule | Define what makes an account relevant and what would exclude it from outreach. |
| Review | Check that the next action is justified by observed activity rather than an assumption about buying readiness. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Bring the existing Clearbit account
Your team has a Clearbit subscription and wants Unify to use it for visitor identification.
Start with collection, then assess identification. Do not interpret a missing visit as a provider failure until the tag is checked.
- Confirm which Clearbit account owns the key
- Connect it in Unify and inspect the website client
- Review collected visits before defining an audience
Compare with Unify Intent
The team wants website identification but has not decided to connect a separate provider account.
Choose the documented path that matches the account setup. Neither path comes with a coverage guarantee in this guide.
- Review the Unify Intent option with the account owner
- Confirm the collection method already used on the site
- Evaluate a controlled period of activity in your own account
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Unify uses the connected Clearbit account as part of website visitor identification.
Check the saved connection and the incoming site activity separately. A successful connection alone does not demonstrate that a specific visit will be identified.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Clearbit.
How do I connect Clearbit to Unify?
Enter the API key from your existing Clearbit subscription in Settings → Integrations → Clearbit. Unify then uses that account for website visitor identification.[1]
Is a separate Clearbit subscription required?
The direct API-key connection requires an existing Clearbit subscription. Unify also documents an out-of-the-box Unify Intent path powered by Clearbit and other providers.[1]
Does this connection send Unify prospect payloads to Clearbit?
The integration guide describes using Clearbit to identify website visitors. It does not describe an outbound prospect webhook or custom JSON payload for this connection.[1]
Can I set it up without changing a Play?
The documented connection is configured in Unify integration settings. It does not require adding a Webhook action to a Play.[1]
What identification rate should I expect?
The cited guide does not publish an identification-rate guarantee. Validate the connection using your own collected website activity instead of assuming every visitor will be identified.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- No coverage percentage, latency target, or provider-specific error catalog is given in the cited guide
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Clearbit workflow.
Clearbit + website tag
| Decision | What to know |
|---|---|
| Connection credential | Clearbit API key[1] |
| Subscription | An existing Clearbit subscription for the direct connection[1] |
| Use case | Website visitor identification[1] |
| Alternative path | Unify Intent includes Clearbit and other providers[1] |
The documented connection is a provider setting, not a custom payload schema. Keep the distinction between collecting visits on your site and identifying those visits through a provider.
Technical setup reference
References and requirements for the Clearbit connection.
Connection requirements and setup checklist
Before connecting
- An existing Clearbit subscription with an API key
- Access to Unify integration settings
- A working website-activity collection setup
Retrieve your existing Clearbit key
Use the API key associated with the Clearbit subscription you intend to connect.[1]
Save it in Unify
Open Settings → Integrations → Clearbit and enter the API key.[1]
Check website collection
Confirm the Unify website tag is installed once and is collecting visits. Use the website-tag guide for your installation method.[2]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
There is no website activity
Inspect the tag installation before changing the provider key. The client must be loaded and able to send requests.[2]
The key is not usable
Confirm that the key belongs to the intended Clearbit subscription. The Unify guide does not provide a provider-error reference, so escalate account-specific key issues rather than assuming a particular fix.[1]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
