HubSpot data enrichment fills blank contact and company fields automatically, so your reps stop researching and start selling. You’ve got three routes: HubSpot’s native Breeze Intelligence, a third-party app from the marketplace, or an API or batch enrichment feed. This guide walks each one step by step.
It also covers the custom properties, workflows, overwrite rules, and credit costs you set up first. Let’s make your CRM data actually usable.
| Approach | Typical cost | Control / overwrite governance | Coverage / best for |
|---|---|---|---|
| Native Breeze Intelligence | Standard enrichment is now free for Core Seat users on paid portals; advanced credit-metered features reset monthly | Built into HubSpot settings plus workflows; HubSpot’s overwrite logic | 40+ attributes from HubSpot’s dataset; needs business email; best for HubSpot-first teams |
| Third-party marketplace app | Per-seat or per-credit subscription | App-dependent; map fields and overwrite rules yourself | Coverage varies by vendor and region; best for specialty data or wider coverage |
| API / batch enrichment | Pay-as-you-go or volume contract | Full control; you own field mapping, overwrite, and timing | Best for bulk hygiene, custom fields, and high-volume pipelines; needs dev or ops setup |
I’ve spent about five years building these workflows on live portals, so this guide reflects what actually breaks and how to fix it. Let’s start with the basics.
What is HubSpot data enrichment?
HubSpot data enrichment is the process of filling missing or stale contact and company fields in your CRM with external data. So instead of a rep manually Googling a prospect’s job title, the record fills itself. The data falls into four types, and each one answers a different question about your buyer.
Firmographic data describes the company. It covers industry, employee count, revenue, and location. So a thin company record becomes a profile you can actually qualify against.
Demographic data describes the person, such as job title, seniority, and role. Technographic data lists the tools a company runs, like its CRM or cloud provider. Intent data flags buying behavior, such as repeat visits to your pricing page.
Each type feeds a different play. Firmographics drive routing and scoring. Demographics drive personalization.
Technographics drive fit. Intent drives timing.
So you rarely enrich all four for every record. Instead, you enrich the ones your next action needs.
A quick example of data enrichment
A lead fills out your demo form with just a name and a work email. Enrichment then appends their job title, company size, industry, and headquarters location automatically.
So within seconds, a near-empty record becomes one your team can route and score. That’s the whole point: less manual research, more selling.
Why does this matter for data quality? Because a half-empty record can’t be scored, routed, or personalized. When I audited a SaaS portal in 2022, nearly 40% of contacts had no job title.
Our routing rules silently dropped them. Then enrichment closed that gap in one batch run.
Here’s the part teams underestimate. Bad data doesn’t just sit there quietly. It actively misroutes leads, skews reports, and wastes rep hours.
So enrichment is really a data quality program wearing a different hat.
“Sales reps spend only around 28% of their week actually selling, with admin and data work eating much of the rest.” Source: Salesforce, State of Sales Report (2024)
So enrichment isn’t a nice-to-have. It buys back selling time. Next, does HubSpot do this natively, or do you need an app?
Does HubSpot have native enrichment? Meet Breeze Intelligence
Yes, HubSpot has native enrichment, and it’s called Breeze Intelligence. This is the successor to Clearbit, not a separate live integration.
HubSpot acquired Clearbit in December 2023. Then it rebranded the product as Breeze Intelligence at INBOUND 2024.
So the old standalone Clearbit integration no longer exists inside HubSpot. Breeze Intelligence replaced it.
Now it pulls from HubSpot’s commercial dataset to fill blank fields. On its data enrichment product page, HubSpot states it fills 40+ contact and company attributes.
🧠 Fun Fact: Most enrichment blogs still tell readers to "install Clearbit" in HubSpot. That advice is two years stale. Clearbit became Breeze Intelligence, and the standalone Clearbit APIs were deprecated for new accounts.
Breeze Intelligence does three jobs. First, data enrichment fills company size, industry, location, revenue, and job title.
Second, buyer intent de-anonymizes site visitors. Third, form shortening auto-fills fields a known contact has already given you.
Here’s why the three-job design matters to you. All three pull from the same underlying engine and, for the metered features, the same credit pool.
So how you use one affects what’s left for the others. I’ll break that down in the cost section.
For now, the headline is simple. Breeze is built for HubSpot-first teams who want enrichment inside their existing CRM.
You can read HubSpot’s own overview in its understand Breeze guide. Now let’s turn it on.
How to enable and use Breeze Intelligence (step-by-step)
To enable Breeze Intelligence, an admin grants enrichment access in settings, then you enrich records manually, in bulk, or through automation. HubSpot’s KB on how to enrich your contact and company data mirrors these steps. Here’s the order that works on a live portal.
- Check permissions. In Users & Teams, an admin toggles data enrichment access for the right seats.
- Open settings. Go to Data Management, then Data Enrichment.
- Choose auto or manual. Auto-enrichment updates new and existing records; manual lets you control timing.
- Enrich a single record. Open a contact, then use the enrich action to fill blanks on demand.
- Bulk-enrich a list. Select a list or saved view, then run enrichment across all records at once.
- Review enrichment history. Check the record timeline to see which fields filled and when.
💡 Pro Tip: Don't flip on auto-enrichment for every record on day one. Start manual, watch which fields actually fill, then automate once you trust the match quality.
The business email constraint that tanks match rates
Note the business email constraint. Breeze only matches contacts that carry a verified business email.
So free Gmail and Yahoo addresses usually return nothing. When our team tested Breeze on a German SMB list in 2024, the business-email rule cut our match rate hard because so many contacts used personal webmail.
There’s a subtler trap in the bulk step too. Bulk-enriching a huge list at once feels efficient.
But it also means you commit to whatever overwrite rule is set before you’ve checked a sample. So I always enrich a small test batch first, eyeball the results, then scale.
One more habit worth building: review enrichment history regularly, not just once. The timeline tells you which fields filled, which stayed blank, and where your match rate is weakest. That signal tells you whether native alone is enough or whether you need a second source.
HubSpot’s get started with data enrichment page walks the same setup with screenshots. But native isn’t your only option. What if you need data Breeze doesn’t carry?
Third-party enrichment apps in the HubSpot App Marketplace
Third-party apps in the App Marketplace add coverage that native Breeze Intelligence doesn’t, such as deeper phone data or region-specific firmographics. So they’re worth a look when Breeze leaves gaps. Here’s a neutral survey of common options.
ZoomInfo brings broad firmographic and contact depth, especially for North American accounts. Apollo.io pairs enrichment with sequencing and has a generous free tier. Clay runs a waterfall across many providers, which can lift aggregate fill rates.
Hublead focuses on LinkedIn-to-HubSpot enrichment, which helps if your prospecting starts in LinkedIn Sales Navigator. BuiltWith specializes in technographic data, mapping the tech stack a company runs. So each tool has a clear strength rather than a universal edge.
You can also feed an API enrichment source into HubSpot for bulk or custom work. CUFinder is one such third-party option you can pipe in through its contact enrichment service, though coverage and match rates vary by region and vertical, so test on a sample first.
The same caution applies to every vendor here. None of them wins on every list.
On a UK fintech portal, I once ran the same 500 accounts through native Breeze and a third-party app. Breeze filled industry and size cleanly.
The app filled more direct dials. So we kept both, with a clear priority order.
When does a third-party app beat native? When you need specialty data, wider regional coverage, or contact-level detail that HubSpot’s dataset thins out on.
There’s also the non-HubSpot angle. If your enrichment needs to feed tools beyond HubSpot, an app or API gives you portability that native locks away.
For a broader survey, see this roundup of CRM data enrichment tools. It compares vendors on coverage, pricing, and fit. So how do you actually choose between the three routes?
Native Breeze vs third-party app vs API enrichment: how to choose
Choose your route by cost model, control, coverage, and volume, in that order. So the decision isn’t “which tool is best” but “which fits this job.” Here’s how I weigh each criterion.
Cost model matters first. Native Breeze handles standard enrichment without extra credit spend for Core Seat users now.
Meanwhile apps and APIs carry their own subscriptions. So the cheapest standard option today is often native.
Control comes next. An API gives you full ownership of field mapping and timing.
Native gives you HubSpot’s built-in logic instead. So pick by how much governance you need to own yourself.
Coverage is the third lever. Test each option against your own ICP, not a vendor’s headline contact count.
A tool with 200 million contacts can still miss your niche vertical. So a small sample test beats any marketing claim.
Volume decides the rest. For a quarterly hygiene pass on 50,000 records, batch enrichment through an API usually beats clicking through native screens. For a trickle of new MQLs, native real-time fits better.
🔍 Did You Know? A common practitioner move is waterfall enrichment, where you stack providers so a second source fills what the first one missed. Teams report aggregate fill-rate gains of roughly 15 to 30% versus any single provider.
My rule of thumb is plain. Start native if you’re HubSpot-first and need standard fields. Add an app for specialty or regional gaps.
Reach for an API when volume and custom fields dominate.
Whichever route you pick, the plumbing stays the same. You still need custom properties to hold the data and workflows to move it.
So the choice of source doesn’t change the foundation underneath it. That foundation is also where your data quality either holds up or quietly breaks. Now let’s build it: properties and a workflow.
Set up custom properties and an enrichment workflow
Before any enrichment runs, create the custom properties that hold the data, then build a workflow to fill them. So the data has somewhere to land and a trigger to arrive. Here are the build steps.
- Create custom properties. In settings, add fields for any data native objects don’t already cover, such as a normalized industry tier.
- Build a workflow. Start a contact-based workflow with clear enrollment triggers, like “lifecycle stage becomes MQL.”
- Add the enrich action. Drop HubSpot’s enrich record action into the workflow so qualifying contacts fill automatically.
- Map fields. Match each incoming attribute to the right property so nothing lands in the wrong place.
- Add branching. Branch on data presence, so already-complete records skip enrichment and save effort.
- Set a re-enrichment cadence. Schedule periodic refreshes rather than enriching the same record endlessly.
It pays to branch early on “is this field already filled?” That keeps your workflow from re-touching clean records and protects your budget.
Why bother with custom properties at all? Because HubSpot’s default fields rarely match your exact scoring or routing model. So you create custom properties for things like account tier, region group, or a normalized industry value.
Those custom properties give your workflows clean targets to fill. So the enrichment data lands somewhere your scoring and routing can actually read it.
Tighten enrollment triggers and field mapping
A word on enrollment triggers. Vague triggers cause the most pain.
“Any contact created” enrolls everything, including junk. So I tighten triggers to real intent, like “became an MQL” or “form submitted on a key page.” That keeps enrichment focused on records that matter.
Field mapping deserves the same care. One mismatched mapping can pour company revenue into a contact field.
Then your reports break quietly. So I map fields one at a time and test with a single record before the workflow goes live.
This same workflow pattern is how you auto-fill missing CRM fields without manual data entry. HubSpot workflows and Operations Hub (now Data Hub) give you the branching and field mapping to do it cleanly.
But should every record enrich in real time? Not even close.
Manual vs automated vs API/batch enrichment (when to use each)
Match the enrichment method to the moment: real-time for fresh leads, batch for hygiene, manual for edge cases. So you don’t burn effort enriching everything the same way. Each method has a clear home.
Real-time enrichment fits new MQLs and form fills, where a rep needs context now. Batch enrichment fits the quarterly hygiene pass, where you refresh thousands of aging records at once. Manual enrichment fits edge cases, like a strategic account you want to verify by hand.
A mistake I made early on was enrolling every new contact into real-time enrichment. We burned through our enrichment budget in nine days.
Then we had nothing left for the quarterly cleanup. So now I split the two on purpose.
Real-time enrichment has a hidden cost beyond budget. It also adds a small delay to record creation while the enrichment call runs.
So for high-volume form fills, I sometimes enrich just-in-time at the routing step rather than at creation. That keeps forms snappy.
Batch enrichment has its own rhythm. I run it monthly or quarterly, off-hours, against a list of records older than a set age.
So the hygiene pass never competes with live lead flow. Manual enrichment stays reserved for the handful of accounts worth a human look.
So plan your methods together, not in isolation. Real-time and batch compete for the same resources, whether that’s credits or API volume. Speaking of conflicts, here’s the governance question that protects your best data.
Overwrite rules and your source-of-truth hierarchy
Overwrite rules decide whether enrichment fills only blank fields or replaces existing values. Get this wrong and you’ll destroy good data. So set it before you run anything at scale.
The safest default is “fill blanks only.” It adds data where you have none and leaves verified entries untouched. The riskier setting is “overwrite existing,” which replaces current values with the enrichment source. Use it only when you trust the source more than your own records.
📌 Example: When I rebuilt a HubSpot portal for a SaaS client in 2023, our enrichment workflow overwrote 4,000 hand-verified job titles. We'd left the rule on "overwrite." So setting it to "fill blanks only" stopped the bleeding, but the cleanup cost us a week.
This is where a source of truth hierarchy earns its keep. Rank your data by trust: manual entry beats native enrichment, which beats third-party, which beats inferred. So when two sources conflict, the higher-trust value wins.
Both native Breeze and most apps let you encode this through field-level overwrite settings and provenance tracking. The trick is to write the hierarchy down before you build, not after a bad overwrite. So treat it as a config decision, not an afterthought.
One more nuance: some fields deserve “overwrite” while others demand “fill blanks only.” Company employee count changes often, so refreshing it makes sense. A hand-verified job title does not.
So set overwrite per field where your tool allows it. Now the question every ops lead asks: what does this cost?
What does HubSpot data enrichment cost? Is it free?
Honest answer: standard enrichment is now free for Core Seat users, but the broader feature set is not unlimited. So “is HubSpot enrichment free?” has a yes-and-no answer in 2026.
Here’s the current picture. As of September 2025, HubSpot made standard contact and company enrichment free for Core Seat users on paid portals.
No credits are consumed for it. So that’s a real change from the earlier credit-metered model.
What the credit pool still covers
But advanced features still cost. Buyer intent, AI agents, and other Breeze capabilities draw from a shared monthly credits pool.
That pool resets each month with no rollover. So unused credits simply vanish at the reset.
HubSpot publishes a 100-credit pack at roughly $45 a month (annual). Higher tiers like 1,000 or 10,000 credits are widely cited around $450 and $4,500 a month, though HubSpot doesn’t always publish them. So budget the metered features deliberately, because the bill scales fast.
🔍 Did You Know? One documented case saw a team leave auto-enrichment on by default under the old model and rack up roughly $11,000 in a single billing cycle. So budget governance isn't optional.
Here’s how I budget credits in practice. The metered features compete for the same pool, so I cap each one.
Then I leave headroom for the quarterly hygiene pass rather than spending every credit on real-time fills. That way a busy month of buyer-intent activity never starves the cleanup work.
For the concept behind all this, see what contact enrichment actually means as a discipline. Third-party apps and APIs price separately, usually per seat or per credit. So your true cost is native plus any apps plus API volume.
Poor data quality carries a cost too, even when enrichment looks free. Gartner has estimated it costs organizations around $12.9 million a year on average. So the real question isn’t “is enrichment free” but “what does bad data cost me to ignore.” Once data is enriched, what do you do with it?
Put enriched data to work (lead scoring, routing, segmentation, reporting)
Enriched data only pays off when it drives action: scoring, routing, segmentation, and reporting. So don’t enrich for its own sake. Each filled field should feed a downstream decision.
Use firmographic fields for lead scoring, so a 500-person company outranks a solo freelancer. For routing, those same fields send enterprise leads to senior reps.
Then segmentation builds lists by industry or region. Finally, reporting reflects reality instead of blanks.
Most of these plays run through workflows too. So once a record is enriched, workflows can auto-assign an owner, set a score, or add it to a sequence. That turns clean data into action without a human touching it.
After we enriched company size on a stale list, our routing finally worked. Enterprise MQLs reached senior reps within minutes instead of sitting unassigned. So win rate on that segment climbed noticeably the next quarter.
There’s a sequencing lesson here. The use case should drive the enrichment, not the reverse. Pick the GTM goal first, then enrich only the fields that goal needs.
So a scoring project enriches employee count and industry, not every attribute on offer. But enriched data also carries obligations. Let’s talk compliance and decay.
Data quality, decay, and GDPR/CCPA compliance
Enriched data decays fast and carries legal duties, so plan for both. Data decay is constant. Industry figures put B2B data loss at roughly 30 to 35% a year as people change jobs and companies merge.
So a one-time enrichment isn’t enough. You need a refresh cadence, or your clean data rots within months. This is why the batch hygiene pass matters as much as real-time fills.
How do you watch data quality over time? HubSpot’s Data Quality Command Center surfaces gaps, duplicates, and formatting issues in one view. So you can spot where enrichment is failing before it skews a report.
For high-volume pipelines, some teams push enriched data through reverse ETL from a warehouse back into HubSpot. So your CRM and your central data store stay in sync. That keeps data quality consistent across every tool, not just inside HubSpot.
Compliance is the other duty. Under GDPR Article 14, when you collect personal data indirectly, you owe the person transparency.
Enrichment vendor data counts as indirect collection. So you generally need to tell people you hold it and why.
The CCPA sets parallel rules for California residents. So track provenance: know where each enriched field came from and on what lawful basis. That record is your defense if anyone asks.
🔍 Did You Know? Data-driven organizations are reportedly around 23 times more likely to acquire customers, per McKinsey. But that edge only holds if the data is both accurate and lawfully sourced.
So treat enrichment as an ongoing program with a compliance layer, not a one-off import. The legal exposure is real, and provenance tracking is cheap insurance. Next, the mistakes I see teams make again and again.
Best practices and common mistakes
Strong enrichment comes down to discipline, and most failures trace to skipping one of these steps. Before you scale, walk through a data enrichment checklist so nothing slips. Here are the practices that matter most.
- Set overwrite rules before your first run. “Fill blanks only” protects hand-verified data by default.
- Test on a sample first. Run 100 to 200 of your own records, then check match rate and accuracy.
- Budget real-time and batch separately. Don’t let new-lead enrichment starve the hygiene pass.
- Enrich to the use case. Fill only the fields your scoring, routing, or segmentation actually needs.
- Branch on data presence. Skip records that are already complete to save budget.
- Track provenance. Know each field’s source so conflicts resolve cleanly.
- Refresh on a cadence. Data decays yearly, so schedule periodic re-enrichment.
- Watch the business-email constraint. Personal webmail tanks native match rates on SMB and EU lists.
💡 Pro Tip: The single most expensive mistake is leaving overwrite on "replace existing" without realizing it. Check that setting first, every time, on every workflow.
So discipline beats volume every time. A small, well-governed enrichment program outperforms a sloppy one that touches everything. Let’s answer the questions teams ask most.
FAQ
Does HubSpot have data enrichment?
Yes, HubSpot has native data enrichment through Breeze Intelligence. It fills blank contact and company fields from HubSpot’s commercial dataset, covering 40+ attributes like industry, size, and job title. You enable it in settings, then enrich records manually, in bulk, or through a workflow.
Is HubSpot enrichment free?
Partly. As of September 2025, standard contact and company enrichment is free for Core Seat users on paid portals, with no credits consumed. But advanced features like buyer intent and AI agents still draw from a metered monthly credit pool, and third-party apps cost extra.
What is Breeze Intelligence in HubSpot?
Breeze Intelligence is HubSpot’s native AI enrichment engine and the successor to Clearbit. HubSpot acquired Clearbit in 2023 and rebranded it Breeze Intelligence in 2024. It handles three jobs: data enrichment, buyer intent, and form shortening, all inside HubSpot.
How do you use Breeze AI in HubSpot?
First, an admin grants enrichment access in Users and Teams. Then you turn on auto or manual enrichment in Data Management settings. From there, enrich a single record, bulk-enrich a list, or add the enrich action to a workflow so qualifying contacts fill automatically.
How much does HubSpot Breeze cost?
Standard enrichment is now free for Core Seat users. Advanced Breeze features use credits, with a 100-credit pack around $45 a month (annual) and higher tiers cited near $450 for 1,000 credits. Credits reset monthly with no rollover, so budget carefully.
What is an example of data enrichment?
A simple example: a lead fills a form with just name and email. Enrichment then adds their job title, company size, industry, and location from an external dataset. So a near-empty record becomes a scorable, routable contact without any manual research.
Why is my HubSpot enrichment not working?
The most common cause is the business-email requirement. Breeze won’t match contacts using free Gmail or Yahoo addresses. Other causes include enrichment access not being toggled on for your seat, or an overwrite rule set to skip fields that already hold a value.
The bottom line
HubSpot data enrichment comes down to three routes and one discipline. Pick native Breeze Intelligence if you’re HubSpot-first and need standard fields, which are now free for Core Seat users.
Add a marketplace app for specialty or regional coverage. Reach for an API or batch enrichment when volume and custom fields dominate.
But the route matters less than the governance. Set your overwrite rules to “fill blanks only” before your first run. Build a source of truth hierarchy so conflicts resolve cleanly.
Then enrich to your GTM use case, not to maximum fill. Do that, and your CRM data finally earns its keep. So start with one workflow, test it on a sample, and grow from there.
Bad
Okay
Good
Amazing
