Skip to content

List Builder

Part of: ClientVerse Core (every client). Roadmap: M1.1–M1.4.

What it is

List Builder is how the firm builds and maintains lists of people and accounts — the audiences behind campaigns, mailings, events, and targeted outreach. A list can be static (a fixed set of members you curate) or dynamic (a rule defined by SOQL/criteria that keeps itself current). Lists feed campaigns and outreach, and can be derived from other lists.

Who it's for

  • Marketing — builds mailing/event audiences and syncs them to campaigns.
  • BD — builds targeted outreach and pursuit lists.

How it works

Two Core objects, cited from objects/core-key.yaml; field-level detail is in the Data Dictionary.

List (List__c)

A curated or rule-driven set of members (20 fields), built with List Builder:

  • Static lists hold a fixed set of members you add and remove explicitly.
  • Dynamic lists are defined by SOQL / criteria — membership is evaluated from the rule, so the list stays current as data changes.

List Member (List_Member__c)

The membership of a record in a List__c (19 fields), with the metadata needed to manage and sync list/campaign membership.

Roadmap mapping (M1.1–M1.4)

List Builder is delivered as a sequence of roadmap features (asana-feature-index):

Code Capability
M1.1 Build static lists
M1.2 Build dynamic lists with SOQL
M1.3 Update lists/campaigns from existing lists
M1.4 Flexible list/campaign member management

How to use it

Building a list (marketing / BD)

  1. Create a List__c. Choose static (curate members) or dynamic (define a SOQL/criteria rule).
  2. For a dynamic list, write the criteria — often filtering on classifications (practice, industry, region) so audiences stay taxonomy-driven.
  3. Add or refine members; List_Member__c records track membership.
  4. Derive a new list from an existing one, or update a campaign from a list (M1.3).
  5. Manage members flexibly — add, remove, and sync between lists and campaigns (M1.4).

Ties to campaigns

Lists are the bridge to campaigns: members sync from a List__c into a campaign, and updates can flow from existing lists into campaigns (M1.3). This keeps the marketing audience and the campaign membership in step without manual re-entry.

Key objects

Object Fields Role
List__c 20 A static or dynamic (SOQL/criteria) set of members
List_Member__c 19 Membership of a record in a list

Configuration pointers

  • Permission sets: ListBuilder_User (build/use lists), List_Builder_Admin_Permission (admin).
  • See the Admin Guide for enabling List Builder and campaign sync, and the Data Dictionary for the field reference.

Since Core 1.1.7 there are also tiered sets for this area (_Schema_Access / _User / _Admin). The set named above still exists and still works — nothing broke on upgrade — but new access is best granted through the tier that matches the need. See Admin Guide §4.1.

Limits & known issues

  • Dynamic list freshness depends on when criteria are evaluated; a dynamic list reflects data as of its last refresh, not necessarily the instant you view it.
  • A dynamic list is only as precise as its SOQL/criteria — broad criteria can pull in unintended members, so validate the rule against a known sample before syncing to a campaign.