Core Concepts
Audiences, Lists, and Segments
Forge uses three words for groups of people. They are different things, so it helps to know which one you are looking at.
| Term | What it is | Where you meet it |
|---|---|---|
| Audience | A saved definition of who should be in a group (a source such as event attendees, a Salesforce list view, a campaign or a contact query, plus filters). Forge syncs it from Salesforce and keeps a cached size. | Audiences in the left sidebar. |
| Snapshot | An audience captured at one moment. Its membership does not change until you choose Rebuild. Shown as Snapshot on the Audiences list (internally a static list). | Audiences list, send history. |
| Segment | The internal name for a live (Dynamic) audience. Some screens and the event feature Audience Segments use the word. A segment is not a smaller piece of an audience. | Audience Segments in event creation, and some URLs. |
The old Lists page no longer exists: /lists redirects to Audiences.
What an audience is
An audience is a saved definition, not a pile of contacts. Forge stores the definition plus, once synced, only Salesforce record references (an Id, an auto-number and a link) and a cached count. Names and emails are read live from Salesforce when you preview, so they are never copied into Forge.
| Property | Values | What it means for you |
|---|---|---|
| Kind | Live (Dynamic) or Snapshot. | Live audiences change when you edit their criteria or resync, and can be copied with Duplicate (named "… (copy)"). Snapshots stay fixed until Rebuild and cannot be duplicated. |
| Source | Event attendees, Salesforce list view, Campaign members, Contact query. Form Answers and Salesforce Report are available only when an admin switches them on. | The source decides which Salesforce object is searched (Attendee, Contact, Lead, Campaign Member). |
| Scope | Global or Event-specific. | Event attendee audiences are always tied to one event. Sources that read Contacts, Leads or campaigns can be Global, so they do not need an event to send. |
| Status | Draft, Syncing, Ready, Failed (Done also shows after a completed sync). | Only Ready audiences can be sent to. Failed shows the reason. |
| Size | A cached number with an age. | It is a count at the last refresh, not a live total. Use Refresh size or Resync before a big send. |
How filters behave
- Event attendee audiences filter on Registration status and Attendance status (the two fields are independent: someone can be Registered and still Attendance Pending), ticket type and field conditions.
- Selecting several ticket types combines them with AND: an attendee must hold all of them.
- Contact query filters are all combined with AND. Field filters in the attendee builder can be grouped; each field offers the operators suited to its type, such as is any of, contains, between or is empty.
- A list view or campaign source uses exactly the people that list view or campaign contains in Salesforce; Forge adds no filters of its own except an optional campaign member status.
- Very large audiences are refused for inline use: a contact query stops at 50,000 rows and asks you to narrow the filters.
Using an audience in a send
- Wait until the audience status is Ready.
- From the Audiences list choose Send, pick the event if prompted (only event attendee audiences require one) and optionally a template.
- Forge continues into the Communications compose flow for that event, where you review, schedule or send.
- An audience used by a scheduled send cannot be deleted until that send is cancelled or finished.
A Snapshot is the safe choice for a one-off send to a fixed group, such as last year's attendees. A Live audience is the better choice for reminders where the group keeps changing.
Anyone who has unsubscribed or is on the suppression list is excluded at send time, whatever the audience says. See Email Settings under Admin.
Audience definitions are stored in Forge's database. Members are resolved through Salesforce using the signed-in user's access: Attendee (conference360__Attendee__c), Contact, Lead and CampaignMember.