HubSpot active vs static lists: which one you actually want
An active list updates continuously, adding and removing contacts as they start or stop matching its criteria. A static list is a snapshot fixed at the moment you created it. Use active for ongoing segments and suppression, and static when you need the exact same audience every time.
By HubReven
The difference sounds trivial and it causes real mistakes, because the failure is silent and arrives weeks later.
What each one does
Active list. Criteria based and self updating. A contact who starts matching joins automatically. A contact who stops matching leaves automatically. The size changes on its own, without anyone touching it.
Static list. A set of contacts fixed at creation. Nothing joins or leaves unless a person or a workflow adds or removes them. The membership is a snapshot.
That automatic removal is the whole story. It is the reason to use an active list and the reason they surprise people.
When to use an active list
Ongoing segments. "All contacts in manufacturing with over 200 employees." You want this to be true tomorrow without maintenance.
Suppression lists. The most valuable use. One active list of contacts to exclude, covering open deals, current customers and unsubscribes, referenced from every marketing workflow. When someone opens a deal they leave your marketing audience the same day, automatically.
Anything feeding a workflow enrolment. Because you want new qualifying contacts to enter without someone remembering to add them.
Dashboards and counts. A number that maintains itself.
When to use a static list
A specific campaign send. Everyone who registered for the March webinar. That membership should never change retroactively, because next month you want to email the people who actually registered, not the people who currently match a criterion.
Imports. Tag the batch you just imported so you can find it, fix it or roll it back.
Handing a list to a person. Sales gets a list of 40 accounts to work this quarter. It should not shrink because someone's job title changed.
Anything you need to reproduce later. Audits, reports, compliance.
The three mistakes
1. Using an active list for a campaign audience.
You build "contacts who downloaded the guide", send email one, and it goes to 500 people. Between email one and email two, 60 of them become customers and your criteria exclude customers. Email two goes to 440, and your sequence reporting is now comparing two different populations.
Use a static list for a fixed sequence audience. Use an active list to find the people, then copy them into a static one.
2. Using a static list for suppression.
A static do not email list was accurate the day it was built. Everyone who unsubscribed since is not on it. This one has real consequences.
Suppression is always active.
3. Assuming a static list is a backup.
A static list holds references to contacts, not copies of them. If a contact is deleted, it leaves the list too. If you need a real snapshot of the data, export it.
Converting between them
Active to static is the common one, and it is the right move before a send: build the active list, check the count, then copy the current members into a static list. HubSpot supports this directly from the list actions.
Static to active is not a conversion. You rebuild it as criteria, which is only possible if the original membership followed a rule. A list assembled by hand cannot become active.
Lists and performance
Very complex active lists with many criteria across several objects take time to process, and recalculate whenever relevant properties change. A portal with hundreds of them, most unused, is doing constant work for nothing.
Worth auditing periodically: which lists are referenced by a workflow, an email or a report, and which are orphans from a campaign two years ago. Deleting the orphans is free and it is one of the items that shows up in a portal review.
The other thing that makes lists unreliable is upstream of lists entirely. If the segmentation criteria depend on properties nobody fills in consistently, the list is accurate and useless, which is a data problem, not a list problem.
Frequently asked questions
Does an active list remove contacts automatically?
Yes. A contact who stops matching the criteria leaves the list without anyone doing anything. That is the main practical difference from a static list and the reason active lists are correct for suppression.
Can I convert an active list to a static list?
Yes, by copying the current members into a new static list from the list actions menu. Going the other way is not a conversion, because you have to express the membership as criteria.
Which list type should I use for an email campaign?
Static, if the sequence has more than one send. It keeps the audience identical across sends so your reporting compares the same population rather than two different ones.
Do static lists keep a copy of the contact data?
No. They reference contacts, so deleting a contact removes it from the list. For a genuine snapshot of the data, export the list to a file.
Get the next one