Back to the guides

PRACTICAL SOFTWARE GUIDE

HubSpot active vs static segments: changing rules or fixed membership?

For teams deciding whether a CRM group should update continuously or preserve a reviewed snapshot.

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose membership behavior deliberately

HubSpot's current documentation calls these groups segments. Active segments update membership as records start or stop meeting their criteria. Static segments capture qualifying membership when saved and do not automatically add later matches, although records can be added or removed manually. Select the behavior that matches the business decision rather than assuming every saved group is a permanent snapshot.

Our recommendation is to write whether the group means “eligible now” or “reviewed at this point in time.” Those are different questions even if they initially contain the same records.

A fictional renewal review

Assume a team reviews customers whose renewal date falls within its next review window. It needs a continuously changing work queue and a separate record of which customers were assigned to a particular review meeting. The changing queue and the meeting cohort have different purposes.

For this example, an active segment can represent current eligibility, while a static cohort can represent the reviewed meeting selection. That is a proposed design choice, not a guarantee that either group is an immutable audit log.

Test membership over time

Synthetic changeQuestion to verify
Record begins meeting criteriaDoes it join the active group after processing?
Record stops meeting criteriaDoes it leave the active group?
New matching record after static group creationDoes the static cohort remain unchanged automatically?
Manual membership editWho owns the change and its explanation?

Make the criteria inspectable

  1. Choose the object being grouped and define the business purpose.
  2. Write the conditions, including handling for missing dates or classifications.
  3. Choose active or static membership deliberately.
  4. Use known synthetic records just inside and outside each boundary.
  5. Wait for the saved segment to finish processing before reconciling membership.
  6. Inspect record IDs rather than relying only on a matching total.

Beware of relationship filters

Our data-model advice is to ask which related record supplies each condition. A customer can have several deals or company relationships. A rule that finds any qualifying associated record may answer a different question from a rule intended for a specific primary relationship. Inspect the actual association filter options and verify a multi-association sample.

Also define the timezone and date-window convention used in the review. A group based on dates can change even if nobody manually edits the underlying business record that day.

A segment is not permission to contact

Membership describes a group under chosen rules. Our recommendation is to review communication eligibility, subscription preferences and the intended action separately before using it for outreach. This guide does not send messages or establish a legal basis for contact.

If the purpose is an audit trail, preserve the reviewed IDs, criteria and timestamp in an authorized process. Do not assume a manually editable static group proves that its membership has never changed.

Acceptance criteria

Accept the segment when its changing or fixed behavior matches the declared purpose, boundary records behave as expected and a second operator can explain the inclusion of a specific ID. This is a proposed validation exercise, not a completed account test or a claim about exact processing speed.

Sources and verification

Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.

Continue your evaluation

Practical guides for this topic

Put your tools to work.

Need help choosing or setting up your tools? Tell Koldia what you want to improve.

Discuss your project