HubSpot Segments (Formerly Lists): The Complete 2026 Guide

HubSpot renamed Lists to Segments. Most guides to HubSpot segments haven't caught up.

They still show you a menu that doesn't exist. They skip the 60-association-filter ceiling. They tell you Breeze builds lookalike audiences (it doesn't). And they have nothing to say about why your segment count says 4,812 and the record view says 3,109.

This guide covers all of it. Every limit, behaviour and quirk below is sourced to HubSpot's own documentation and verified in August 2026. Where something comes from experience instead of a published rule, I say so.

Key takeaways

• HubSpot segments are the lists tool, renamed. Same active/static types, same filter engine, same list IDs. It moved to CRM → Segments in September 2025.
• Active segments have no memory. They only know who qualifies right now — which is why you can't manually remove anyone from one.
• Two hard caps apply to every segment: 250 filters total, of which a maximum of 60 can be associated-object filters.
• Complex segments can take up to two hours to process. The size on the index page is an estimate; the number inside the segment is real.
• Breeze builds filters, not lookalike audiences. Those are a separate ads feature on a separate tier.
• Five well-named foundational segments beat fifty campaign lists. Build ICP, lifecycle, engagement, suppression and consent first.

Contents

• HubSpot segments explained (formerly lists)
• Active vs. static segments
• Segments vs. views vs. workflows
• Which objects support segments
• Limits, processing, and what actually breaks
• Filter logic that holds up
• Building segments with Breeze AI
• The B2B SaaS segmentation playbook
• Measuring and governing your segments
• Frequently asked questions

HubSpot segments explained (formerly lists)

HubSpot segments are saved groups of CRM records built from filter criteria. HubSpot renamed the lists tool to Segments in September 2025 and moved it to CRM → Segments. The functionality is identical — active and static types, the same filter engine, and every existing list kept its ID.

What is a HubSpot segment?

A segment is a saved group of records built from filter criteria. You define who belongs — contacts in Norway with a lifecycle stage of MQL who opened an email in the last 30 days — and HubSpot maintains the group for you.

From there you can email that group, enrol it in a workflow, report on it, sync it to an ad network, or use it to personalise website content.

Where did HubSpot Lists go?

They're under CRM → Segments. In some accounts you'll click More first, then navigate to CRM → Segments. The interface labels it "Segments (previously called lists)," and HubSpot's knowledge base now uses segments terminology throughout.

Here's what didn't change: nothing functional. Active and static types work identically. The filter engine is the same. Your existing lists kept their IDs, so every workflow, email and report that referenced them stayed connected. The API still exposes them under the lists endpoints.

If you've been building HubSpot lists for five years, you already know how to build segments. You just need to update your vocabulary and your bookmarks.

Why did HubSpot rename lists to segments?

Because "list" implies a fixed roll of names — and that stopped describing the tool a long time ago. A modern active segment is closer to a live query against your CRM than a mailing list. It feeds ads audiences, personalisation, lead scoring, reporting and automation, not just email sends.

"Segment" describes that better. It also lines up with how the rest of the CRM industry talks.

Note: I'll use both terms throughout this guide, because that's how your team talks in real meetings. When I say list, I mean segment.

Why segmentation is the layer everything else sits on

It's tempting to treat segmentation as a marketing chore. Build the list, send the email, move on. That underrates it badly.

Think about what depends on your segments being correct:

• Your marketing email goes to a segment
• Your workflow enrols from one segment and suppresses from another
• Your ads audience syncs from a segment
• Your dashboard filters by segment membership
• Your lifecycle reporting counts records that qualify for a segment

If the filter logic is wrong, every one of those things is wrong too. Quietly. Until someone notices the numbers don't add up.

That's why the teams who get the most out of HubSpot treat segmentation as a data-modelling exercise rather than a campaign task. They build a small number of well-named, reusable segments that describe genuine states — this is our ICP, this is a product-qualified lead, this is someone we're legally allowed to email in the EU — then compose campaign audiences from those building blocks.

The alternative is what most portals actually look like: 400 one-off lists with names like "webinar list FINAL v2," nobody sure which ones are still in use, and three competing definitions of MQL.

Active vs. static segments

An active segment updates itself continuously — records join when they meet your filter criteria and leave when they stop meeting them. A static segment is a snapshot taken when you saved it. Records are added once and never removed automatically, even if every qualifying property changes.

HubSpot's documentation puts it plainly. Active segments "automatically update their members based on its criteria. Records will join the segment when they meet the criteria and leave the segment when they no longer meet the criteria." Static segments "include records that meet a set criteria at the point when the segment is saved. Static segments do not update automatically, so new records that meet the criteria will not be added to the segment."

Here's the consequence most people miss: an active segment has no memory. It doesn't know who used to be in it. It only knows who qualifies right now. Build an active segment of "contacts whose lifecycle stage is MQL," and the moment a contact progresses to SQL they're gone — and any workflow using that segment as an enrolment trigger treats them as having left.

Active vs. static: full comparison

When is a static segment the right choice?

Static segments have a reputation as the lesser option. They're not. They're the right tool whenever the fact of having qualified matters more than the current state.

Say you ran a webinar in March. Everyone who attended is a fact about March that will never change. Build that as an active segment on "registered for marketing event X" and it technically works — but you're paying continuous processing cost to re-derive something frozen. Worse, if someone merges a duplicate or an integration rewrites a property, your "who attended in March" answer can shift under you.

A static segment locks it. Same logic applies to compliance snapshots ("everyone we emailed on this date"), migration batches, and anything you'd need to defend in an audit.

How do you convert a static list to an active list?

You don't have to rebuild it. If your static segment was built with filters, open it, click Actions, then select Convert to active.

Why this matters: the segment keeps its ID. Every workflow, email and report pointing at it stays connected. Rebuilding from scratch means hunting down every dependency and re-pointing it — and that's where things break.

One limitation: conversion only works on static segments that have filters saved. A static segment built purely by manual import has no criteria to activate, so you'll need to define filters first.

How do you remove a contact from an active segment without deleting them?

This is one of the most-searched HubSpot questions, and the answer frustrates people. So let's be direct: you cannot manually remove a record from an active segment. There's no remove button. That's by design — membership is derived entirely from the filters. If the record qualifies, it's in.

You have three real options:

1. Change the data. Find the property putting them in and change it. If your segment is "lifecycle stage is MQL," moving them to SQL removes them. This is the correct fix when the record genuinely doesn't belong.

2. Add an exclusion filter. Build a static suppression segment, add the contacts manually, then add a filter to your active segment: is not a member of segment [Suppression]. Clean, and it scales — one suppression segment can be referenced by dozens of active segments.

3. Add a dedicated property. For exclusions you'll need repeatedly, create a custom checkbox property like "Exclude from nurture" and filter on it. More maintainable than a static list, because reps can set it from the record and it shows up in reporting.

Pro tip: option 2 is the one to standardise on. A single STA-CON-Suppression-Global segment referenced by every active audience gives you one place to fix a problem instead of thirty.

Getting this pattern right early saves a lot of pain later. Book a call with Superwork if you want a second pair of eyes on your segment architecture before it becomes 400 lists nobody trusts.

Segments vs. views vs. workflows

Use a view to look at records, a segment to act on them, and a workflow to do something to them. Views work on every object but can't feed email, ads, or reporting. Segments support fewer objects with far more filter power, and integrate with every activation tool in HubSpot.

Three different HubSpot features group records. Choosing wrong wastes a lot of effort.

What is a view?

A view is a saved filter on an index page. Every object with an index page supports them — contacts, companies, deals, tickets, custom objects, activities, tool assets. You filter by that object's own property values, save it, and your team gets a working list they can sort and scan.

Views are fast. They don't consume segment limits. They're the right answer for "I want my reps to see their open deals over 50k."

What views can't do: feed other tools. You cannot email a view, sync it to an ad network, use it as a workflow trigger, or build a report on its membership.

What makes a segment different?

Segments support fewer objects but far more filter power. HubSpot's own comparison: in addition to their own property values, segments let you filter "with other criteria, such as another object's property values, page views, form submissions, and email interactions."

And crucially, segments integrate with marketing emails, workflows, custom reports, ads audiences and satisfaction surveys. As the documentation puts it: "if your goal is to use the group of records in any of these tools, you should create a segment rather than a view."

Where do workflows fit?

Workflows are automation, not grouping. They enrol records, then act on them — send an email, update a property, create a task, rotate an owner.

A workflow's enrolment criteria look almost identical to segment filters, which causes real confusion. The difference is what happens next. A segment maintains a group. A workflow does something to records and moves on.

Comparison table

Pro tip: filtered index-page views are lighter than segments. If a group of records only ever needs to be looked at, make it a view. Segments cost processing, and a portal carrying thousands of active segments alongside heavy workflows runs measurably slower.

What about "smart lists"?

Same thing as an active segment. The term came from the marketing email tool, where a smart list is just an active list used as a send audience. You'll still see it in older articles and a few HubSpot screens. There's no separate feature to learn.

Which objects support segments

HubSpot segments support contacts, companies, deals, tickets, custom objects, carts, and orders. Each segment holds exactly one object type — you cannot mix contacts and companies in a single segment. You can, however, filter one object by another object's properties using association filters.

HubSpot's AI documentation confirms the list explicitly, naming "contact, company, deal, ticket, custom object, cart, and order segments."

Can a segment contain both contacts and companies?

No. A segment can only contain one object type. There's no mixed mode, no toggle, no workaround inside the segment builder. You pick an object when you create the segment and that's what it holds.

This surprises people because the filters look cross-object. In a contact segment you can absolutely filter on associated company properties. "Contacts whose associated company has more than 200 employees" is a perfectly valid contact segment. But the members are still contacts. The company properties are only criteria.

Three workarounds when you need both

Build parallel segments on shared criteria. Want "target accounts and the people at them"? Build a company segment filtered on your ICP criteria, then a contact segment filtered on associated company matching the same criteria. Two segments, one definition, kept in sync by using identical filters.

Use the custom report builder. If the goal is analysis rather than action, the report builder handles multi-object joins natively. This is almost always the right answer for "how many contacts do we have at target accounts, broken down by industry."

Use association filters as the bridge. Often you don't need both objects — you need one object filtered by facts about the other. Filter your contact segment by associated company properties and the problem disappears.

Pro tip: if you're modelling a buying committee rather than a flat contact group, segments are the wrong shape entirely. That's what buying groups are for — see the HubSpot buying groups and buying role guide.

Limits, processing, and what actually breaks

Marketing Hub allows 10 active segments on free tools, 50 on Starter, 1,200 on Professional, and 2,000 on Enterprise. Every segment is capped at 250 filters, including a maximum of 60 associated object filters. Complex segments can take up to two hours to process.

This is the chapter most guides get wrong, because the numbers change and nobody re-checks them. The limits below were verified against HubSpot's Product & Services Catalog and knowledge base in August 2026.

How many lists can you have in HubSpot?

On free tools there's an extra constraint worth knowing about. Segment criteria are "limited to form submission data, contact property information, and marketing email activity." No page views, no workflow membership, none of the behavioural filters.

Sales Hub and Service Hub tiers broadly mirror Marketing Hub.

The Business Units add-on is generally reported to grant an extra 100 active and 100 static segments per additional business unit, up to an account-wide ceiling of 5,000 total. Those two figures come from secondary sources rather than the current catalog text — treat them as directionally right and confirm with your rep before planning around them.

Verify before you commit. Tier limits change without much announcement. Check the HubSpot Product & Services Catalog before making any decision that depends on these numbers.

How many filters can a segment have?

Two hard ceilings apply to every segment, on every tier:

250 filters per segment. HubSpot's troubleshooting documentation is specific that "the limit applies to all filters, including if you're using AND and OR logic." Filter groups don't buy you extra headroom. Every individual filter across every group counts.

60 associated object filters. As HubSpot puts it: "in a contact-based segment, you can have up to 60 company property filters." Exceed it and you get an error, not a silent truncation.

The 60-association limit is the one that bites. Sophisticated ABM segments stack company firmographics — industry, employee count, revenue, region, tech stack, tier, owner. Add associated deal filters on top and you burn through 60 faster than you'd think.

When you hit it, push the logic upstream. Create a calculated or workflow-maintained property on the company record that answers the question once, then filter on that single property instead of re-deriving it in every segment.

How long do HubSpot segments take to process?

HubSpot states that "most segments will finish processing within a few minutes, but complex segments may take longer to process. Segments with complex filters, such as those related to integrations, page views, or segment memberships, can take up to two hours to process."

Two hours. Plan around that number, not the few-minutes best case. Building a segment on Friday afternoon for a Monday send is fine. Building it 20 minutes before a webinar invite goes out is a problem — and no setting will speed it up.

Pro tip: turn on the processing-complete notification for anything time-sensitive. It's the difference between knowing your audience is ready and hoping it is.

Why doesn't my segment count match?

This is the single most-reported segment complaint. HubSpot's own explanation is more useful than the "known bug" framing you'll see elsewhere: "The size stated in the segments editor is an estimate of the number of records in the segment. Click the segment to view the actual count of records in the upper left."

So the index-page number is an estimate. The number inside the segment is the real one.

If they disagree, the segment is probably still processing. Wait and refresh — don't clone it. (Cloning forces a fresh calculation, which is why that folk remedy appears to work.)

Where this genuinely hurts is downstream. If a workflow or email fires while a segment is mid-processing, it acts on whoever is in the segment at that moment, not whoever should be. That's the mechanism behind most "why did only half my list get the email" tickets.

Build a buffer between creating a segment and using it.

Why are unexpected contacts in my segment?

Here's a behaviour that catches people every single time. Email interaction filters evaluate all historical email activity for every address ever associated with a contact. HubSpot confirms it: "if you've changed the email address of a contact, interactions from their previous email address will still count towards segment filters."

So "contacts who have never opened an email" quietly excludes someone who opened one four years ago at a previous employer's address. If your re-engagement segment looks smaller than it should, this is usually why.

Why can't I delete a segment?

Two possible reasons: the segment is being used by another tool, or it's a HubSpot default segment (personas, blog subscriptions, partner lead registration).

For the first case, open the Used in tab to see exactly what depends on it, remove those references, then delete.

Two reassurances while we're here:

• Deleting a segment does not delete the records. HubSpot is explicit: "deleting a segment does not delete the segment's records."
• You have 90 days to undo it. "You can restore a deleted segment within 90 days after it has been deleted."

Filter logic that holds up

Filters inside the same group use AND logic and narrow your results. Separate filter groups use OR logic and broaden them. You can flip either default. This gives you (A OR B) AND (C OR D) — for deeper nesting, combine sub-segments using membership filters.

HubSpot segments are only as good as their filters, and the filter builder rewards a bit of structure.

How do AND and OR logic work in HubSpot segments?

The mechanics are simple once you see them. Filters inside the same group use AND by default. Every condition must be true, so each filter you add narrows the result. Separate filter groups use OR by default. A record matching any group is included, so each group you add broadens the result.

HubSpot lets you flip either default. That gives you the shape most segments need:

(Country is Norway OR Country is Sweden) AND (Lifecycle stage is MQL OR Lifecycle stage is SQL)

What you can't do (and the workaround)

You can't nest more deeply than that. There's no way to express ((A OR B) AND C) OR ((D OR E) AND F) in a single segment. HubSpot doesn't document this as a stated limit — it falls out of how filter groups work — but it's the ceiling you'll hit on genuinely complex logic.

The workaround is composition. Build each half as its own segment. Then create a third segment with two groups: is member of segment [Half A] OR is member of segment [Half B].

Membership filters let you nest arbitrarily deep by treating segments as building blocks. More objects to maintain, but the logic becomes readable — and a segment you can explain to a colleague is a segment that survives your holiday.

What can you filter on?

Filter categories go well beyond properties:

• Object and activity properties
• Segment membership (is member of segment / is not member of segment)
• Import membership
• Workflow enrolment (Professional and above)
• Ads interactions across Google, Facebook and LinkedIn
• Buyer intent
• CTAs, custom events and documents (mostly Marketing Hub Professional and above)
• Email subscriptions, marketing emails, marketing campaigns, marketing events
• Media interactions and page views
• SMS events, SMS subscriptions, WhatsApp subscriptions
• App-specific data from integrations

Three of these deserve a closer look.

Time-based filters

Relative date filters — "is less than 30 days ago," "is more than 90 days ago" — are what make a segment genuinely self-maintaining. Absolute dates turn an active segment into a static one that just doesn't know it yet.

One quirk to watch: HubSpot's relative date windows include the full prior day plus the elapsed portion of today. So "less than 1 day ago" covers more than 24 hours. It rarely matters — but it matters at exactly the moments you'd expect, on daily sends and same-day triggers.

Behavioural filters

Page views, form submissions, CTA interactions and email engagement are where segments earn their keep. Most of them support refinements. You can filter form submissions by which form, on which page, how many times, and in what date range.

This is how you build a product-qualified lead segment, or a "read the pricing page three times this month" sales alert.

Association filters

Filtering by associated-object properties is what lets a contact segment know about companies and deals.

The default behaviour is worth understanding: HubSpot matches on any associated record. A contact associated with five companies is included if any one of them matches.

On Professional and Enterprise you can narrow this by association label, or restrict to the primary company — which usually gives you what you actually meant.

One documented gap: there's no "is none of" operator for association labels. To exclude records by label, build a segment of everything carrying that label, then filter your main segment on is not a member of that segment.

Building segments with Breeze AI

Breeze generates segment filters from a plain-English description on Starter, Professional, and Enterprise tiers. It supports object properties, associated object properties, and segment memberships, plus form submissions and page views for contacts. It does not generate lookalike audiences — that's a separate ads feature.

Breeze can build your filters from a plain-English description, and it's genuinely quicker than clicking through the builder for anything moderately complex. It's available on Marketing Hub, Sales Hub, Service Hub and Data Hub at Starter, Professional and Enterprise. It works on contact, company, deal, ticket, custom object, cart and order segments.

Two settings you need on first

Before Breeze will do anything:

1. Go to Settings → AI → Access and enable "Give users access to generative AI tools and features."
2. Turn on the CRM Data switch as well.

HubSpot recommends the second one "to generate outputs relevant to your company." Without it, Breeze doesn't know your property names — which is most of what makes it useful.

Breeze prompts that actually work

The pattern that works is naming the objects and properties you want, not just the outcome. Compare:

Weak: "Contacts who are good leads."

Better: "Contacts whose lifecycle stage is MQL, whose associated company has more than 100 employees, and who submitted a form in the last 60 days."

Better still: "Contacts in Norway, Sweden or Denmark whose associated company industry is Software, who are not members of the Suppression segment, and who opened a marketing email in the last 30 days."

Breeze builds the filters, then hands them to you to review. Always review. It's good at translating a clear description into the right filter structure. It's less good at guessing which of your four similarly-named custom properties you meant.

What Breeze can and can't do

It can: generate segment filters from a prompt, and generate a segment description from filters you've already built.

That second one sounds minor. It's quietly the most useful part — it means every segment can carry a plain-English explanation of what it contains without anyone having to write one.

Supported filter types are a subset, not everything. Breeze handles current object properties, associated object properties and segment memberships across all object types. For contact segments it also handles form submissions (excluding refinements), ad interactions, email subscriptions, marketing emails and page views (excluding refinements).

Anything outside that list — custom events, integration data, most behavioural refinements — you build by hand.

One correction to something you'll see repeated everywhere: Breeze does not generate lookalike audiences. Lookalikes are an ads feature, available on Marketing Hub Starter and above, built from an existing audience inside the ads tool. They have nothing to do with the AI assistant in segments. The two get conflated constantly.

Deciding where AI actually fits in your HubSpot setup? Book a call with Superwork — we spend a lot of time separating the parts that genuinely save hours from the parts that just demo well.

The B2B SaaS segmentation playbook

Build a foundation of reusable segments before campaign lists: ICP tiers, lifecycle stages, engagement recency, suppression, and consent status. Compose campaign audiences from those building blocks. Five well-named foundational segments do more for pipeline reporting and deliverability than fifty one-off campaign lists.

Everything above is mechanics. This is the part that decides whether your segments are worth having.

Most portals accumulate segments campaign by campaign. That produces hundreds of overlapping one-offs and zero shared definitions. Here's the foundation I'd build instead, for a B2B SaaS or mid-market company selling in Europe.

Layer 1: Who they are

ICP tiers. Company segments for Tier 1, Tier 2 and Tier 3 accounts using firmographics — industry, employee count, revenue, region, and whatever technographic signal matters in your category. Then matching contact segments filtered on associated company.

This single pair of definitions ends more internal arguments than any other segment you'll build. "Is this account a fit" stops being a matter of opinion.

Persona and seniority. Contact segments by job function and seniority, built on properties your forms actually populate. If you're inferring seniority from free-text job titles, fix the data before you build the segment. A segment built on unreliable input produces confidently wrong audiences.

Region and language. Non-negotiable if you sell across Europe. You need these for compliance and for basic courtesy in messaging.

Layer 2: Where they are

Lifecycle stages. Active segments per stage, built strictly on the lifecycle stage property — not re-derived with filters. Why? Because if your MQL segment and your MQL lifecycle stage can disagree, you have two definitions of MQL. You'll spend the next quarter reconciling reports.

Product-qualified leads. For product-led motions, this is the highest-value segment you'll build: contacts at accounts hitting meaningful usage thresholds. It usually depends on getting product usage data into HubSpot as properties first — a data-engineering problem more than a segmentation one. But once the properties exist, the segment is trivial and the pipeline impact is not.

Engagement recency. An active segment of contacts who've opened, clicked, visited or submitted in the last 90 days. Combine it with your ICP tiers and you get the matrix that should drive your whole nurture strategy:

Layer 3: Who you must not email

Suppression segments protect your deliverability. They're also the ones nobody builds until something goes wrong. At minimum, build these four:

Competitors and internal domains. A segment filtered on email domain, referenced as an exclusion in every send. It's embarrassing to nurture your own sales team.

Unengaged contacts. Anyone who hasn't opened or clicked in 6–12 months. Continuing to email them costs you inbox placement with everyone else. (Remember the historical-email-address behaviour from the limits chapter. Verify this segment is the size you expect before you act on it.)

Hard bounces and unsubscribes. HubSpot handles unsubscribes automatically for marketing email, but you want them visible as a segment for reporting and for setting contacts as non-marketing.

Open opportunities and existing customers. Nothing undermines a sales conversation like a top-of-funnel nurture email arriving mid-negotiation. Build it as a contact segment filtered on associated deal stage.

Layer 4: Consent and GDPR segments

If you sell into the EU or UK, this layer isn't optional — and it isn't only a legal concern. It's operational, because getting it wrong is expensive in a way other segmentation mistakes aren't.

HubSpot tracks two things you should be segmenting on: lawful basis to process and lawful basis to communicate, alongside subscription types with statuses of opted in, not specified, and opted out.

Build active segments for each meaningful combination — opted in by subscription type, not specified, opted out — crossed with region. The safe default most European teams land on is "no consent, no communication."

Legitimate interest can apply to B2B communication in many jurisdictions. Whether it applies to your communication, to your audience, in your market is a question for your legal counsel, not a blog post. What segmentation gives you is the ability to act on whatever answer they give you — and to prove you acted on it.

The same applies to ads. When you sync an audience to Google, HubSpot asks you to confirm: "I understand that if I'm targeting contacts in the European Economic Area or the U.K., I'm required to collect their consent for advertising and comply with Google's EU User Consent Policy." That checkbox is not decorative.

This is general information about how HubSpot's tooling works, not legal advice. Get your consent model reviewed by someone qualified. We've covered the wider GDPR picture in our HubSpot GDPR and Schrems II guide.

Layer 5: Marketing contacts and your bill

One segmentation decision has a direct line to your invoice. Only marketing contacts count toward your billable tier. HubSpot states that "non-marketing contacts don't count toward your marketing contact tier, and you aren't billed for them."

Non-marketing contacts are still stored, still searchable, still usable by sales and service. They just can't receive marketing email or sync to ad audiences.

Active segments are the right tool for finding candidates: unengaged contacts, hard bounces, unsubscribes, and anyone outside your ICP who arrived through a content download three years ago. HubSpot's manage-marketing-contacts flow lets you select contacts by segment membership directly.

Two things to know about timing. Setting a contact to non-marketing "won't take effect until after the next update date" — typically the first of the following month. So this is housekeeping you do in advance of a renewal, not the week of. And if you exceed your tier, HubSpot upgrades you automatically and prorates it. You can't come back down until renewal.

Pro tip: a quarterly marketing-contact audit built on three saved segments takes an hour and pays for itself immediately.

Where segments stop and buying groups start

For complex, multi-stakeholder deals — the tender-driven procurement cycles common in European enterprise B2B — a flat contact segment doesn't model reality. You need to know who the champion is, who signs, who can block you, and whether you're single-threaded into an account.

That's what buying groups do, and it's a different data structure from a segment. Covered properly in the HubSpot buying groups guide.

Measuring and governing your segments

Every segment has a Performance tab showing size over time, contact engagement, and record breakdowns. Segment comparison covers up to three segments; the account-wide Segment Overlap report covers five. Audit quarterly using the Unused segments tab and name segments so they're readable in dropdowns.

Two things separate a portal that stays useful from one that becomes archaeology: knowing whether your HubSpot segments work, and stopping them from multiplying.

What the Performance tab shows you

Every segment has one, and it's available across all products and plans.

Segment size over time — the number of records across a chosen period, with the option to see how edits to the segment changed its size. If a segment suddenly doubled, this tells you when, and you can line it up against what changed.

Contact engagement — for contact segments, activity over the past 30 days across opened an email, clicked in an email, converted on a form, submitted an NPS survey, and visited your website. This is how you tell whether a segment is an audience or just a pile of records.

Contacts breakdown — distribution by source, country, or lifecycle stage. Useful for sanity-checking that a segment contains who you think it contains.

Any of these can be saved to a dashboard. Worth doing for your core ICP and lifecycle segments, so drift becomes visible rather than something you discover during a QBR.

Comparison vs. overlap (two features people mix up)

Segment comparison lives on the Performance tab. It compares up to three segments side by side — size, how often each is used, seven-day change, email sends, open rates, click-through rates, and size trend graphs. You can push the comparison into the custom report builder for more.

Segment overlap lives in the account-wide Analyze tab. It visualises how up to five contact segments intersect, showing shared records at each overlap point.

Run the overlap report before any multi-segment campaign. It tells you exactly who's about to receive three variations of the same email.

The Analyze tab also shows how segments are used across your account, organised by activation goal — Personalization, Communication, Automation, Analytics and Segmentation — with each card showing how many segments feed the tools in that group.

And on Marketing Hub or Content Hub Professional and Enterprise, the Segment Journey report tracks how members of a contact segment progress through website visits, form submissions and deal milestones, with conversion rates and average completion times.

Naming conventions that survive contact with reality

Folders help. Names do more work. A segment lives in exactly one folder, and folders are invisible in most of the places you actually pick a segment — the workflow builder, the email send dialog, the ads audience picker. In those dropdowns, all you see is the name.

The pattern I'd use:

[TYPE]-[OBJECT]-[PURPOSE]-[YYYY-MM]

• ACT or STA for active or static
• CON, COM, DEAL or TIC for the object
• A purpose that means something to someone who wasn't in the meeting
• A date for anything campaign-bound

So:

• ACT-CON-ICP-Tier1-Nordics
• STA-CON-Webinar-RevOps-2026-03
• ACT-COM-Target-Accounts-Enterprise
• ACT-CON-Consent-OptedIn-EU

Then organise folders by function rather than by campaign — Lifecycle, ICP & ABM, Suppression, Campaigns, Ops, Compliance. Deleting a folder doesn't delete the segments inside it, which is a small mercy.

The 15-minute quarterly audit

The segments index page has an Unused segments tab. That's your audit. Here's the process:

1. Open the Unused segments tab
2. For each segment, decide: still needed, or gone?
3. Rename anything you're keeping but that's clearly stale with a _DEPRECATED prefix, so it sorts together and nobody picks it by accident
4. Delete the rest
5. Spot-check five active segments against their descriptions to catch drift

Remember: deleting a segment never deletes records, and you have 90 days to undo it.

Give one person ownership of this. Segmentation sprawl is a governance problem, not a tooling problem, and it only gets solved when someone's name is on it. In most teams that's whoever owns RevOps. In smaller teams it's whoever cares most.

If your portal is already past the point where a quarterly audit feels manageable, that's usually a sign the underlying data model needs work rather than the segments themselves. Book a call with Superwork and we'll look at what you've got.

Frequently asked questions

Are HubSpot lists the same as segments?

Yes. HubSpot renamed the lists tool to Segments in September 2025. The functionality is identical — active and static types, the same filter engine, the same list IDs — and every existing list carried over untouched. Only the name and the menu location changed. The tool now sits under CRM → Segments.

What is the difference between an active and a static segment in HubSpot?

An active segment updates continuously: records join when they meet the filter criteria and leave when they no longer do. A static segment is a snapshot from when it was saved — records are added once, manually or by import or workflow, and are never removed automatically. Use active for ongoing audiences and static for point-in-time records.

Can you convert a static list to an active list in HubSpot?

Yes, if the static segment was built with filters. Open it, click Actions, then select Convert to active. The segment keeps its ID, so any workflow, email or report referencing it stays connected — no rebuilding required. Static segments built purely by manual import have no filters to activate.

How do I remove a contact from an active list without deleting them from the CRM?

You can't remove them manually — membership in an active segment is derived entirely from the filters. Either change the property that qualifies them, add an exclusion filter using a static suppression segment (is not a member of segment), or create a dedicated exclusion property and filter on it.

Does deleting a list in HubSpot delete the contacts?

No. HubSpot states explicitly that "deleting a segment does not delete the segment's records." The contacts stay in your CRM. To remove the records themselves you'd need to bulk delete them separately.

How do I restore a deleted HubSpot list?

You can restore a deleted segment within 90 days of deletion from the segments index page. After 90 days the deletion is permanent and the segment cannot be recovered.

How many lists can I have in HubSpot?

Free tools allow 10 active and 1,000 static segments. Marketing Hub Starter allows 50 active and 1,000 static; Professional allows 1,200 of each; Enterprise allows 2,000 of each. Sales and Service Hub broadly mirror these. Verify current numbers against HubSpot's Product & Services Catalog, as tier limits change.

How many filters can a HubSpot segment have?

Up to 250 filters per segment, including a maximum of 60 associated object filters. The 250 limit applies to all filters across all filter groups, whether you're using AND or OR logic — grouping doesn't give you extra headroom.

Why is my HubSpot list not updating or showing the wrong count?

The size shown in the segments editor is an estimate — click into the segment to see the actual count. If they disagree, the segment is probably still processing. Most finish within minutes, but segments with integration, page view or membership filters can take up to two hours.

Can a HubSpot segment contain both contacts and companies?

No. Each segment holds exactly one object type. To work across objects, build parallel segments on shared criteria, use association filters to bring the other object's properties in as criteria, or use the custom report builder for analysis that spans both.

What is the difference between AND and OR logic in HubSpot segments?

Filters within the same filter group use AND logic by default, so each one narrows the result. Separate filter groups use OR logic by default, so each one broadens it. You can flip either default, giving you (A OR B) AND (C OR D) logic. Deeper nesting requires combining sub-segments with membership filters.

Can I create a HubSpot segment of companies or deals?

Yes. HubSpot segments support contacts, companies, deals, tickets, custom objects, carts and orders. Company segments are useful for ABM target account lists, and deal segments for pipeline hygiene and forecasting workflows.

How do I segment anonymous website visitors in HubSpot?

You can't put anonymous visitors in a segment — a segment requires CRM records. Anonymous traffic appears in traffic analytics and the prospects tool. Once someone identifies themselves through a form, chat or a tracked email click, their prior page views become available as segment filters.

Do static lists update in HubSpot?

No, not automatically. Records can be added to a static segment manually, by import, or by a workflow action, and removed manually. Nothing happens on its own — that's the entire point of a static segment.

Why is my ads audience smaller than my HubSpot segment?

Two likely reasons. Non-marketing contacts don't sync to ad networks at all. And each network matches on its own data, so some contacts simply won't be found. Sync also takes up to 24–48 hours, so check timing before assuming records are missing.

What's the difference between a HubSpot view and a segment?

A view is a saved filter on an index page — fast, available on every object, but it can't feed marketing email, ads audiences, workflows or reports. A segment supports fewer objects but offers far more filter power and integrates with every activation tool in HubSpot.

Where to go from here

You now have the whole picture. What changed in the rename. How active and static segments genuinely differ. When a view or a workflow is the better tool. The object rules and the limits that catch people. How filter logic composes. What Breeze will and won't build. A segmentation foundation for B2B SaaS in Europe. And the governance to keep it from sprawling.

The thing worth acting on first isn't a feature. It's the foundation layer — ICP tiers, lifecycle, engagement recency, suppression, consent. Five or six well-named segments everyone agrees on will do more for your pipeline reporting and your deliverability than another fifty campaign lists.

Build those. Name them properly. Put one person in charge of the quarterly audit. The rest gets easier.

If your HubSpot segments have already outgrown what one person can hold in their head — or you're setting up a new portal and want the data model right the first time — book a call with Superwork. We work with B2B SaaS and mid-market teams across Europe on exactly this, and we'd rather help you build it properly than help you untangle it later.

Sources

HubSpot Knowledge Base — Create segments · Troubleshoot segments · Determine filter criteria · Use AI assistants in segments · Analyze segment performance · Analyze segments · Edit or delete segments · Views vs segments · Create ads audiences · Set contacts as non-marketing · HubSpot Product & Services Catalog

All limits and behaviours verified August 2026.