These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- CRM + Marketing Automation
- Features
- Lists and Memberships
Lists and Memberships
Define named lead segments and preserve how each membership was added or removed.
OverviewLists Catalog×
CRM + Marketing Automation · Lists and Memberships
New
Lists Catalog
Lists
| List code | Name | Type | Dynamic query | Owner | Member count | |
|---|---|---|---|---|---|---|
| LC-243 | List 350 | Static | DQ-995 | 23 | ||
| LC-276 | List 185 | Dynamic | DQ-925 | 37 | ||
| LC-313 | List 693 | Static | DQ-257 | 33 | ||
| LC-524 | List 667 | Dynamic | DQ-754 | 38 | ||
| LC-117 | List 980 | Static | DQ-579 | 5 |
6 of 6 records
LC-243Lists · LST-53968
StaticNameList 350
Dynamic queryDQ-995
Member count23
ActiveYes
What you can do
Give each audience a definition the team can inspect
A list is a named lead segment used by program entry conditions and scoring rules. Its code, name, description and owner explain why it exists. The type distinguishes a static segment from a dynamic definition, while the active setting identifies the lists available for current work. Marketing Manager agrees the segment’s meaning before another journey relies on it.
Membership records show who belongs and how participation changed. They preserve the lead, list, addition time, source of the addition and any removal time. The local lead link helps reconcile a source identifier with the person the team recognizes. Keep this context when investigating why a lead entered a program, especially when the segment has changed since enrollment.
How the work is organized
- Define the segment. Marketing Manager owns the list definition. For a static list, agree who supplies its members. For a dynamic list, review the stored query and agree refresh behavior during setup. Inspect the resulting population before using the segment in a journey.
- Inspect participation. Compare active memberships with the list’s member summary. Review whether an addition came from an import, a manual action, a workflow or a dynamic refresh. Preserve the dates and removal context when explaining earlier participation.
- Use the reference. Audience conditions can check a target list, program steps can add or remove a lead, and scoring rules can refer to list membership. Check the referenced segment itself before opening the program. Similar list names should not cause a journey to use the wrong audience.
What to agree during setup
Decide who imports memberships and who reviews corrections. Marketing Manager owns the segment definition; Marketing Operations checks the references used by the journey. Assign the maintenance permissions needed for each task and rehearse with those actual accounts. Agree how source lead identifiers map to local records before loading the audience.
Review what active participation means for the pilot and retain addition and removal dates during changes. Rehearse list actions against known leads and inspect their execution history. Compare the member summary with the participation records before another program uses the segment. If the population is unexpected, resolve the definition or import issue before expanding the audience.
Check the handoff on an actual case
Prepare a static webinar-follow-up list and import a known lead through the authorized operating account. Inspect the recorded import source, addition time and active membership. Link that list to an audience condition, then compare the known lead with a lead outside the segment. The program’s other audience conditions still apply to both.
Rehearse a remove-from-list action and inspect the resulting membership state and execution history. Keep the earlier participation trace available when discussing the original enrollment. Finally, suppress a lead that remains on the list and attempt another email or program entry. Confirm that continued list membership does not override the global restriction. Marketing Operations should explain audience eligibility and suppression together before the team resumes nurture work.
What your team sees
- Lists Catalog — Segment purpose, type, owner and member summary.
- Active List Memberships — Active participation with addition source and membership dates.
- Active Programs — Operating journeys whose audience references need review.
Follow the work through
What it keeps track of
Data model- Lists
- Named segments of Leads, used as audience filters and scoring inputs.
- List memberships
- Per-Lead membership in a List.
- Program audiences
- Entry criteria for a Program. A Lead enters when all Audience rows match.
- Program steps
- Ordered steps inside a Program. One row per step.
- Scoring rules
- Per-rule scoring deltas. One row per rule.
- Leads
- Local lead identity and scoring, linked to existing marketing lead references. Unknown contact details remain blank.
Who uses it
Permissions- Marketing Manager
- Owns segment definitions and reviews memberships.
- Marketing Operations
- Builds program references under the agreed permissions.
- Sales Manager
- Reads the list context.
Set up CRM + Marketing Automation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.