Tag: HubSpot workflow

  • What Is a HubSpot Lifecycle Stage? Beginner’s Guide

    A HubSpot lifecycle stage is a property on every contact and company record that shows where that person or business sits in your marketing and sales process, from first-time visitor all the way to paying customer. HubSpot ships with eight default stages, and you can customize them so your whole revenue team works from the same definition of “lead” instead of arguing about it in Slack.

    If you’ve ever had marketing call someone a “qualified lead” while sales calls the same person “just a form fill,” you already know why this property exists. It’s not a fancy feature. It’s the thing that keeps everyone honest about where a contact actually stands.

    What is a HubSpot lifecycle stage, really?

    Think of it as a label that travels with a contact or company record as they move closer to becoming a customer. It’s a default property built into every HubSpot portal, sitting on both the contact and company objects.

    HubSpot’s own documentation describes it plainly: the lifecycle stage property helps you categorize contacts and companies by where they are in your marketing and sales processes, and shows how leads are handed off between teams. That handoff piece matters more than it sounds. Most of the marketing-to-sales friction we see in RevOps (revenue operations, the function that aligns marketing, sales, and customer success processes) traces back to nobody agreeing on when a contact should move to the next stage.

    Here’s the important nuance: lifecycle stage is not the same as deal stage, and it’s not the same as lead status. Mixing these three up is one of the most common configuration mistakes new HubSpot users make.

    Lifecycle stage Deal stage Lead status
    Lives on Contacts and companies Deals Contacts and companies
    Question it answers What is our overall relationship with this person or company? How far along is this specific deal? What is a rep doing with this lead right now?
    Example values Lead, MQL, Customer Demo scheduled, Contract sent, Closed won New, Attempted to Contact, Connected
    Typically updated by Rules, workflows, and sales handoffs The deal owner The rep working the lead

    What are the default HubSpot lifecycle stages?

    HubSpot’s lifecycle stage property comes with these default stages, in sequential order:

    1. Subscriber: a contact who opted in to hear from you, usually by signing up for a blog or newsletter, but hasn’t taken any higher-intent action yet.
    2. Lead: a contact or company that converted on your website or through some other interaction beyond a subscription sign-up, like filling out a contact form.
    3. Marketing Qualified Lead (MQL): a contact or company your marketing team has qualified as ready for sales. HubSpot doesn’t decide this for you. You choose the scoring or behavior criteria that earn someone the label.
    4. Sales Qualified Lead (SQL): a contact or company your sales team has qualified as a potential customer. Its sub-stages are tracked in the separate Lead Status property.
    5. Opportunity: a contact or company associated with a deal.
    6. Customer: a contact or company with at least one closed deal.
    7. Evangelist: a customer who has advocated for your organization.
    8. Other: a catch-all for anyone who doesn’t fit the buyer journey, like a vendor or a job applicant.

    A quick, honest opinion: you probably don’t need all eight from day one. A lot of smaller B2B teams get real value from Lead, Opportunity, and Customer, and skip Subscriber, MQL, SQL, and Evangelist until their volume justifies the extra granularity. Adding stages you can’t consistently define just adds noise to your reporting.

    How does lifecycle stage automation actually work?

    By default, HubSpot’s automatic updates only move a record’s lifecycle stage forward. A form submission can’t accidentally demote a Customer back to Lead. The same applies to imports, the API, the Salesforce integration, and workflows: they can set the stage forward, but to move a record backward with those tools you first have to clear its existing value. You can still set an earlier stage manually.

    In your HubSpot settings, you can choose to set lifecycle stages automatically in three ways:

    • Set a default stage for newly created records.
    • Update the stage based on a record’s associations, for example when a deal is created and linked to a contact.
    • Set a default stage for records synced in from each connected app.

    If you turn on the association-based setting, a contact sitting at Lead moves forward to Opportunity when a deal is associated with them. A contact already marked Customer isn’t pushed back to Opportunity, because the stage only moves forward. Check your settings so you know which behaviors are on, and review the property history, which shows the source of each update.

    Pro tip: don’t rely on manual updates to keep lifecycle stages accurate. Build a workflow (an automated series of actions HubSpot runs based on triggers you set, covered in What Is a HubSpot Workflow?) that moves contacts along whenever they meet your MQL or SQL criteria. Manual updates get forgotten the moment your team gets busy, and busy is every week. Note that the “Set a property value” workflow action requires a Professional or Enterprise subscription.

    The properties HubSpot creates for you

    Every lifecycle stage, default or custom, gets its own set of calculated properties. They’re what make funnel reports possible.

    Property What it shows Useful for
    Date entered [stage] When the record entered the stage Conversion rates and cohort reports
    Date exited [stage] When it left the stage Measuring how long stages take
    Latest time in [stage] Time spent in the stage since the last entry Spotting slow handoffs (Professional or Enterprise)
    Cumulative time in [stage] Total time across every entry to the stage Records that move in and out of a stage (Professional or Enterprise)

    One practical use: build a workflow that creates a task for the contact owner when a contact’s “Date entered Sales Qualified Lead” is more than five days old and nobody has followed up. One catch from HubSpot’s documentation: records won’t enroll in a workflow based on the time-in-stage properties while they’re still in that stage. For that case, trigger on “Lifecycle stage not updated in the last X days” combined with the stage you care about.

    Write one definition per stage

    HubSpot gives you the labels. Your team has to supply the meaning. Here are illustrative definitions you might adapt. They’re examples, not recommendations for every business.

    Stage Example entry criteria Who decides
    Lead Submitted a form beyond a newsletter sign-up, with a business email Marketing
    MQL Fits your ideal customer profile and reaches an agreed engagement score Marketing, with sales sign-off on the rules
    SQL A rep has spoken with them and confirmed a real need Sales
    Opportunity Associated with an open deal Set by the deal association
    Customer At least one closed-won deal Set by the deal outcome

    For help with the qualification criteria behind MQL and SQL, see our comparison of BANT and MEDDIC.

    Why does lifecycle stage matter for a growing team?

    Without a shared definition of each stage, marketing ends up nurturing people who are actually ready to buy, and sales ends up cold-calling contacts who never asked for outreach. That mismatch wastes real budget and burns trust with prospects who get the wrong message at the wrong time.

    Lifecycle stage also becomes the backbone of your funnel reporting. Here’s an illustrative month, with made-up numbers:

    Stage Records entering Conversion from previous stage
    Lead 1,000 n/a
    MQL 150 15%
    SQL 60 40%
    Opportunity 20 33%
    Customer 8 40%

    If a stage looks off, such as more SQLs than MQLs, that’s usually a sign of a data problem (records skipping stages, imports setting stages directly, or conflicting rules), not a sign your sales team is unusually persuasive. These stage dates also feed closed-loop reporting, which connects marketing sources to revenue.

    This is also where your HubSpot tier matters. Workflow-based stage updates and time-in-stage properties require Professional or Enterprise, so it’s worth checking HubSpot Free vs. Starter vs. Professional before you build a stage model you can’t yet automate.

    Common lifecycle stage mistakes

    • Treating lifecycle stage as deal stage. They answer different questions. Keep deal progress on the deal.
    • Too many stages too soon. Every stage needs a definition and an owner, or reports get noisy.
    • Several tools setting the same stage. Imports, forms, integrations, and workflows can all write to it. Decide which one is responsible for each transition.
    • Marketing defining MQL alone. If sales doesn’t agree with the rules, they’ll ignore the label.
    • Assuming a stage can slide backward. Default tools only move it forward, so a “stuck” record may need its value cleared first.
    • Never reviewing the funnel. A report nobody opens can’t catch a broken rule.

    A simple checklist for setting up lifecycle stages

    1. List the stages you actually need. Start lean; you can add more later.
    2. Write a one-sentence definition for each stage that your marketing and sales teams both sign off on.
    3. Decide which stages update automatically and which manually.
    4. Build a workflow for MQL and SQL criteria so you’re not relying on someone remembering to update a dropdown.
    5. Set up a funnel report that shows conversion rates between each stage.
    6. Review the report monthly and fix any stage where the numbers look wrong.

    Honestly, the teams that get the most value out of lifecycle stages aren’t the ones with the fanciest setup. They’re the ones who look at the funnel report every month and argue about the weird numbers instead of ignoring them.

    Summary

    A HubSpot lifecycle stage is a property on contacts and companies that shows where each one sits between first visit and paying customer. HubSpot provides eight defaults: Subscriber, Lead, MQL, SQL, Opportunity, Customer, Evangelist, and Other. It differs from deal stage, which tracks one deal, and from lead status, which tracks a rep’s activity with a lead. HubSpot doesn’t set MQL or SQL for you, so you define the criteria.

    Automatic updates only move the stage forward, and moving a record backward through tools like workflows requires clearing its value first. Each stage gets calculated date and time properties that power funnel reports. Start with only the stages you can define, write one definition each with sales and marketing agreement, automate the MQL and SQL transitions with workflows on a plan that supports them, and review the funnel monthly.

    FAQ

    Is lifecycle stage the same as deal stage in HubSpot?

    No. Lifecycle stage tracks the overall relationship a contact has with your company, from Subscriber through Customer. Deal stage tracks progress within one specific sales deal, and a single contact can be tied to multiple deals at different stages.

    Can I customize the default lifecycle stages?

    Yes. You can rename, reorder, delete, or add stages to match your sales process, and HubSpot creates the matching calculated date and time properties for each default and custom stage.

    Does HubSpot set MQL and SQL automatically?

    No. HubSpot leaves the MQL and SQL definitions up to you, so you need to build your own scoring criteria or workflow logic to move contacts into those stages.

    What happens if a contact’s lifecycle stage seems stuck?

    Check the property history to see what last changed it. A stage set manually can sit unchanged, and because default tools only move stages forward, a record stuck at an earlier stage usually means no rule, import, or workflow ever pushed it ahead.

    Do I need to use all eight default stages?

    Not at all. Plenty of B2B teams run fine using just Lead, Opportunity, and Customer, and add Subscriber, MQL, SQL, or Evangelist later if their volume and reporting needs call for it.

    Can a lifecycle stage move backward?

    You can set an earlier stage manually. Imports, forms, the API, the Salesforce integration, and workflows only move it forward unless the existing value is cleared first. Plan for that if you need records to move back, for example when a customer churns.

    Where do I turn on automatic lifecycle stage updates?

    In your HubSpot settings for the contact or company object. You can set a default stage for new records, update stages from associations, and set a default per connected app. Review what each option does before turning it on.

  • HubSpot Custom Properties vs Default: When to Add One

    A HubSpot property is just a field on a record, like Email or Deal Amount. Default properties ship with the CRM out of the box. Custom properties are ones you build yourself. The rule of thumb: use a default property if it already captures what you need, and only create a custom one when there’s a genuine gap in what HubSpot gives you.

    If you’ve ever stared at the “Create property” button in HubSpot and wondered whether you actually need it, you’re not alone. New admins tend to swing one of two ways: they either never touch properties at all, or they go overboard and build a custom field for every little thing the sales team asks for. Neither approach ends well.

    This post breaks down the actual difference between default and custom properties, gives you a simple framework for deciding when a new one is warranted, and shows you the mess that happens when teams skip that step.

    What’s the difference between a default property and a custom property?

    A property in HubSpot is a data field attached to a record, whether that’s a contact, company, deal, or ticket. Think of a contact record like a form: Name, Email, and Phone are all separate fields, and each field is a property.

    Default properties (sometimes called standard properties) are pre-built by HubSpot and come with every account. They cover the basics: contact name, email address, phone number, company name, deal stage, and so on. The contacts object alone ships with more than 160 of these built-in fields, and companies, deals, and tickets each have their own sets on top of that.

    Custom properties are fields you create yourself to store information HubSpot doesn’t already track. Say you sell industrial equipment and need to log which certification a customer’s facility holds. There’s no default field for that, so you’d build a custom property to capture it.

    Here’s the part people miss: you can’t delete or edit a default property’s core behavior. You can edit some things, like the dropdown options on a picklist, but the underlying field itself stays put. If you want a cleaner version of an existing field (say, a dropdown instead of free text), you’re usually building a custom property alongside it, not replacing the default one.

    It’s worth being specific about what “can’t edit the core behavior” actually means in practice, since it trips people up. You can rename a default property’s label, move it to a different property group, and adjust certain field-level settings. What you can’t do is change its underlying field type (turning a free-text field into a number field, for instance) or delete it outright, even if your team never uses it. That permanence is exactly why checking before you build matters so much, a custom property you regret creating is far easier to walk back than a default one you’re stuck with forever.

    Why does the distinction actually matter?

    It matters because default and custom properties don’t play the same role in your CRM. Default fields are what most of HubSpot’s native reporting, workflows, and integrations expect to see. When you build a parallel custom field instead of using the one that’s already there, you split your data across two places and nobody’s quite sure which one is “correct.”

    That’s how property sprawl happens. It’s rarely a case of teams needing more features. Most of the time, it’s someone creating a new field before checking what already exists in the portal.

    Honestly, most of the CRM messes I’ve seen in these situations aren’t a properties problem at all, they’re a “nobody checked first” problem. A rep needed to track something, didn’t know a field for it already existed, and created a duplicate. Multiply that across a sales team for a year and you’ve got a properties list nobody trusts.

    The fix isn’t more governance software. It’s a five-minute habit: search the existing property list before you build anything new.

    Property sprawl also tends to compound in a specific, predictable way, which is worth understanding so you can spot it early. The first duplicate field rarely causes any visible problem, one rep uses it, nobody else notices. The damage shows up months later, once a report or workflow was built referencing the “wrong” one of the two fields, and now half your contacts have data in the field the report ignores. Untangling that after the fact means auditing every record, deciding which field actually holds the correct data, and migrating values, a cleanup job that’s entirely avoidable if someone had just searched the property list first.

    When should you actually create a custom property?

    Here’s a simple framework. Ask these questions in order before you hit “Create property.”

    1. Does a default property already capture this? Search the property list for the object (contact, company, deal, or ticket) first. If it’s there, use it instead of duplicating it.
    2. Is the default field the wrong format, not missing entirely? If the data exists but as free text when you need a dropdown, that’s an editing job, not necessarily a new-property job. You can often adjust the field type or the picklist options on many default properties without building a duplicate.
    3. Is this data unique to how your business operates? Things like a renewal date tied to your specific contract terms, a product tier that only your company sells, or an internal lead score your team built are all fair game for a custom property.
    4. Will this field feed a report, workflow, or segmentation you actually plan to use? If you can’t name the report or automation that will use this data, you probably don’t need the field yet.
    5. Have you checked with other teams who touch this object? A field that makes sense to sales might duplicate something marketing already tracks under a different name.

    If you get through all five and there’s still a genuine gap, go ahead and build the custom property.

    Pro tip: before creating a picklist-style custom property, check whether the default version of that field already exists with different options. Editing the existing dropdown to match your business (say, trimming HubSpot’s long default industry list down to the five or six industries you actually sell into) is usually faster and cleaner than building a parallel custom field.

    Question four deserves a bit more weight than the others, since it’s the one most often skipped in practice. It’s tempting to create a field because it feels like useful information to have on hand, even without a specific report or workflow in mind yet. The problem is that “might be useful someday” fields are exactly the ones that sit empty, half-filled, or forgotten a year later, cluttering the property list for everyone else without ever earning their keep. If you genuinely can’t name what will use the data, it’s usually fine to wait until the actual need shows up.

    What are the technical limits on custom properties?

    HubSpot caps how many custom properties you can create, and the limit depends on your subscription tier. If you’re not sure which tier your company is on or should be on, it’s worth reading through a comparison of HubSpot’s Free, Starter, and Professional tiers before you commit to a properties strategy, since the tier you’re on affects what you can build.

    Free accounts are capped at a small number of custom properties, while paid Professional and Enterprise plans allow far more per object. That ceiling exists for a reason: HubSpot wants you to actually use the fields you create, not hoard them.

    Dropdown-style (enumeration) properties also have their own internal limit on how many options a single field can hold. If you’re building a picklist with thousands of options, you’ll eventually hit that ceiling too.

    These limits matter more for growing teams than they might initially seem to. A company that starts with a handful of custom fields on a Free or Starter plan can hit its ceiling surprisingly fast once multiple teams start adding properties independently, which is yet another reason the “search before you build” habit pays off, since every unnecessary duplicate field is also quietly eating into a limited, finite budget of properties you’re allowed to create.

    A quick checklist before you create a new property

    • Searched the existing property list for this object and confirmed nothing similar exists
    • Named the specific report, workflow, or segment this new field will support
    • Picked the right field type (single-line text, dropdown, number, date, etc.) instead of defaulting to free text
    • Written a short description so other users know what the field is for
    • Confirmed with any other team that touches this object that they don’t already track this somewhere else
    • Assigned the property to a logical group instead of leaving it uncategorized

    Properties feed directly into automation, so once you’ve got your fields sorted, it’s worth understanding how a HubSpot workflow actually uses that data to trigger emails, tasks, or updates. A clean property setup is what makes those workflows reliable instead of flaky.

    Worth adding to that same checklist habit: revisit your property list periodically, not just at the moment of creating something new. A quarterly pass through each object’s property group, checking for fields that have sat empty for months or clearly duplicate another field under a slightly different name, catches the sprawl that accumulates even when everyone individually followed the checklist above in the moment.

    Summary

    Default HubSpot properties ship with every account, over 160 on the contacts object alone, and can’t be deleted or have their core field type changed, though you can edit things like dropdown options. Custom properties exist to fill genuine gaps, data unique to your business that no default field captures, but creating one before checking whether a default property already covers it is the single biggest cause of property sprawl and the “messy CRM” complaints that follow.

    The five-question framework, checking for an existing default field, confirming it’s a format problem rather than a missing field, verifying the data is genuinely unique to your business, naming the specific report or workflow that will use it, and checking with other teams first, catches most unnecessary custom properties before they’re built. HubSpot’s per-tier limits on custom properties make this habit matter even more for growing teams, since every unnecessary duplicate field eats into a finite budget shared across the whole organization.

    FAQ

    Can I delete a default HubSpot property I don’t like?

    No. Default properties can’t be deleted or fundamentally changed, though you can often edit dropdown options or move them into a different property group to reduce clutter.

    How many custom properties can I create in HubSpot?

    It depends on your plan. Free accounts have a much smaller cap than paid Professional and Enterprise accounts, which allow up to 1,000 custom properties per object.

    What happens if two teams create separate custom properties for the same data?

    You end up with duplicate, half-filled fields and reports that don’t match. This is the single biggest cause of “messy CRM” complaints, and it’s almost always solved by checking existing properties before building new ones, not by adding more fields.

    Should I use a custom property or a custom object?

    A custom property adds a new field to an existing record type like contacts or deals. A custom object creates an entirely new type of record with its own properties and pipeline logic, and it requires an Enterprise-tier subscription. Most beginner use cases only need a custom property.

    Is it ever okay to create a custom property that duplicates a default one?

    Sometimes, but only when the default field’s format genuinely doesn’t work for you and can’t be edited to fit. Even then, name the custom version clearly so your team knows which field is the one to trust.

  • HubSpot Active List vs Static List: What’s the Difference?

    A HubSpot active list automatically adds or removes contacts as they meet or stop meeting your criteria, while a static list stays frozen at whatever contacts you put in it (or matched a filter) at the moment you created it. Use active lists for ongoing segmentation and automation, and static lists for one-time snapshots like event attendee rosters.

    If you’re setting up HubSpot for the first time, lists are one of the first things you’ll bump into, and one of the first things that trips people up. You go to build a list, HubSpot asks you “Active or Static?”, and if you’ve never used the tool before, that question means nothing to you.

    Here’s the good news: once you get the concept, it’s genuinely simple. The names are actually pretty literal once you know what to look for.

    What is a HubSpot list, exactly?

    A list in HubSpot is just a group of contacts, companies, deals, or other records that share something in common. That “something” could be a job title, a form they filled out, an email they opened, or a property value like lifecycle stage (if you’re unfamiliar with that term, we cover it in our post on what a HubSpot lifecycle stage is).

    Lists exist so you can talk to the right group of people without manually digging through your whole database every time. HubSpot itself frames lists as a tool for record segmentation, filtering, and grouping to serve your business needs. Once you build one, you can use it to send an email, trigger a workflow, or just check reporting on a specific segment.

    When you create a list, HubSpot makes you choose between two types: active or static. That choice matters more than it looks like it does.

    It’s worth pausing on why HubSpot forces this choice upfront rather than letting every list just quietly work however you need. The two types aren’t really variations on the same idea, they’re built to answer two different questions: “who matches this criteria right now, continuously” versus “who was in this group at one specific moment.” Trying to answer both questions with one list type is exactly what leads to the confusion new users run into.

    What is a HubSpot active list?

    An active list (sometimes people still call it a “smart list,” an older name HubSpot used) is a list that updates itself. You set the criteria, like “contact has opened an email in the last 30 days” or “company is in the software industry,” and HubSpot keeps checking the database against those rules on an ongoing basis.

    Active lists automatically update their members based on their criteria: contacts join the list when they meet the criteria and leave when they no longer meet it. So if someone visits your pricing page today, they might get added to a “pricing page visitors” active list tonight. If they haven’t visited in 90 days, HubSpot could drop them off automatically depending on how you’ve set the filter.

    Think of an active list as a living, breathing group. It’s never really “done.” That’s exactly why it’s the backbone of most ongoing email campaigns and automation: your subscriber list for a recurring newsletter is a textbook active list use case, since it automatically manages an always-changing group of subscribers.

    A few other common active list use cases worth knowing, since they show up in nearly every HubSpot setup: a “current customers” list built on deal stage or lifecycle stage, so it automatically grows as new deals close and shrinks if a customer churns and their record gets updated; an “engaged leads” list based on recent email opens or website visits, feeding a nurture workflow that only fires for people who are genuinely still active; and a “cold leads” list catching contacts who haven’t engaged in 60 or 90 days, useful for a re-engagement campaign or for flagging records that might need cleanup.

    What is a HubSpot static list?

    A static list is the opposite. It’s a snapshot, frozen at the moment you built it. Static lists are fixed and don’t update automatically; you have to add or remove contacts by hand.

    Say you export a list of everyone who registered for a webinar last month. That’s a perfect static list. The webinar happened, the registrants are the registrants, and nothing about that group needs to change tomorrow just because someone updates their job title in your CRM.

    Static lists are best for one-time emails, infrequent campaigns, and any list that doesn’t need constant refreshing. They’re also handy for reporting purposes, since you can look back at exactly who was in a group at a specific point in time, which an active list can’t give you (the membership keeps shifting).

    Other common static list scenarios: a list of attendees from a specific conference booth you’re following up with individually, a hand-picked group of accounts your sales team wants added to a targeted ABM sequence regardless of whether they match any automated criteria, or a list of contacts flagged for a one-time data cleanup task. In each of these cases, you genuinely want the group to stay exactly as you defined it, not shift because someone’s job title changed in the CRM three weeks later.

    Active list vs static list: the core differences

    Here’s the side-by-side version:

    1. Updating: Active lists refresh automatically as records meet or stop meeting criteria. Static lists only change when someone manually adds or removes a record.
    2. Best for: Active lists suit ongoing campaigns, workflows, and behavior-based targeting. Static lists suit one-time sends, event rosters, and point-in-time reporting.
    3. Editing after creation: You can add or remove filters on an active list at any time and it’ll reprocess. A static list’s membership is fixed once processed; you add or remove records one by one instead of changing filters.
    4. Use in automation: Active lists pair naturally with a HubSpot workflow because the enrollment criteria keeps working in the background. Static lists can still trigger workflows, but the group won’t grow or shrink on its own afterward.

    Honestly, most of the confusion we see with new HubSpot users isn’t about which list type is “better.” It’s that they default to static lists out of habit (because it feels safer and more controlled) when an active list would save them hours of manual list maintenance every month.

    That instinct toward static lists is understandable, since a frozen group feels predictable in a way a list that changes on its own doesn’t. In practice, the opposite is usually true: an active list you’ve configured correctly requires zero ongoing attention, while a static list you’re trying to use for ongoing segmentation requires someone to remember to update it every single time, which is exactly the kind of manual task that quietly stops happening after the first few weeks.

    Can you convert one list type to another?

    Yes, and this used to be a real pain point. HubSpot rolled out an update that lets you convert a static list to an active list (and vice versa) without losing the list ID or breaking references to it in workflows and emails. Before that, converting meant cloning the list and starting over, which broke every automation pointing at the old list.

    To convert, open the list, go to the Actions menu in the top right, and select the convert option. One catch: only static lists that were originally created with filters are eligible to convert to active, since HubSpot needs those filters to know what criteria to apply going forward.

    Pro tip: if you’re not sure which type to pick when you’re building a new list, lean active by default. It’s easier to freeze an active list’s membership later than to retroactively add dynamic rules to something you built as static.

    How to create a list in HubSpot (quick steps)

    1. Navigate to Contacts (or Companies, Deals, Tickets) and click Lists.
    2. Click Create list in the upper right.
    3. Choose the record type your list is based on.
    4. Choose Active list or Static list from the dropdown.
    5. Set your filter criteria in the left panel and click Apply filter.
    6. Name the list clearly (something like “Active – Pricing Page Visitors – Last 7 Days” beats a vague name every time).
    7. Save and let HubSpot process the list.

    That’s really the whole workflow. The hard part isn’t the clicking, it’s deciding what criteria actually reflect the audience you’re trying to reach.

    A naming convention worth adopting from day one, especially once you have more than a handful of lists: prefix every list name with its type (“Active – ” or “Static – “) the way the example above does. Six months into using HubSpot, a growing team can easily accumulate fifty or more lists, and a consistent naming pattern is the difference between finding the right one in seconds versus opening five lists to figure out which is which.

    Summary

    Active lists in HubSpot update themselves continuously based on filter criteria, contacts join and leave automatically as their properties or behavior change, which makes them the right choice for ongoing campaigns, workflows, and anything behavior-based like a newsletter or a nurture sequence. Static lists freeze at the moment of creation and only change through manual editing, which fits one-time sends, event rosters, and point-in-time reporting where you specifically want the group to stay fixed.

    The most common mistake new users make is defaulting to static lists out of habit because a frozen group feels safer, when an active list built correctly requires far less ongoing maintenance. HubSpot allows converting between the two types without breaking existing workflow or email references, so when in doubt, lean active by default, since it’s easier to freeze an active list’s membership later than to retroactively add dynamic filtering to something built as static.

    FAQ

    Is a HubSpot smart list the same as an active list?

    Yes. “Smart list” was HubSpot’s older name for what’s now called an active list. If you see the term in an old blog post or a coworker’s notes, it’s referring to the same dynamic, self-updating list type.

    Which list type should I use for a newsletter?

    Use an active list. A recurring newsletter needs a subscriber group that keeps updating as people opt in or unsubscribe, and that’s exactly what active lists are built for.

    Can I manually add contacts to an active list?

    Not directly the way you can with a static list. Active list membership is controlled entirely by the filter criteria you set, so if you want someone included, you generally need to adjust their properties or the list’s filters rather than adding them one by one.

    Do static lists update at all?

    Only if you update them yourself. A static list’s membership stays exactly as it was when you last added or removed a contact, it will not react on its own to new form fills, property changes, or behavior.

    Why does HubSpot even offer two list types instead of one?

    Because they solve different problems. You want dynamic, always-current segments for ongoing marketing and automation, but you also want frozen, reliable snapshots for reporting or documenting who was part of a specific one-time group. Trying to force one list type to do both jobs usually ends in messy data.