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
- Programs and Audiences
Programs and Audiences
Build a nurture journey with an explicit audience, ordered actions, a goal and recorded approval.
OverviewMy Draft Programs×
CRM + Marketing Automation · Programs and Audiences
New
My Draft Programs
Programs
| Program number | Name | Type | Goal | Owner | Status | |
|---|---|---|---|---|---|---|
| PRG-46704 | Program 706 | Drip | GLS-3432 | Draft | ||
| PRG-10003 | Program 312 | Trigger | GLS-5033 | Draft | ||
| PRG-13427 | Program 978 | Webinar | GLS-3038 | Draft | ||
| PRG-57718 | Program 602 | Event | GLS-7308 | Draft | ||
| PRG-38871 | Program 203 | Re engagement | GLS-9912 | Draft |
6 of 6 records
Program 706Programs · PRG-46704
DripGoalGLS-3432
StatusDraft
Activated at22 Oct
What you can do
Give each program a defined job
Marketing Manager starts a nurture program with the result the team wants from a lead. A webinar follow-up might aim for a booked meeting. A drip journey might work toward an agreed score threshold. Marketing Operations turns that intent into an audience and an ordered sequence of actions, with an owner responsible for the program.
The Programs console lets the team narrow the portfolio by type, status, goal, scoring model, owner and approval. Its operational list and type distribution help the manager distinguish a running journey from work still being prepared. Keep webinar follow-up separate from an ongoing drip when the entry conditions or intended result differ. A useful program name should explain the purpose; the audience conditions decide who enters.
How the work is organized
- Entry criteria. Every audience condition must match before a lead enters. Marketing Operations can compare a field, check list membership or set a numeric range. Review the combined conditions against actual lead profiles; passing a list condition alone is insufficient when another condition also applies.
- Ordered actions. Each step has an order and an action type. An email action references its template, while a list action references its target segment. Branches identify the next step for each result. Follow both destinations during review so an unexpected result still has an understood path.
- Exit decisions. Any matching exit rule can end enrollment. The outcome distinguishes an achieved goal from suppression, disqualification, a manual exit or audience drift. Marketing Manager agrees what success means before the program starts accepting leads.
What to agree during setup
Marketing Manager agrees the goal and scoring policy. Marketing Operations sets the concurrency limit and re-entry choice, and checks what should happen when a profile stops matching. Connect the CRM profile feed with a stable lead identifier and an owner for unmatched records. Agree which source field each audience comparison uses and rehearse the comparison before opening enrollment.
Review the complete journey through program QA. The manager’s decision belongs in the approval lifecycle, with the deciding person and time retained. Check the approved content and each action reference before activation. Use Program Status Board to discuss the portfolio without confusing a program’s status with the state of an individual member.
Check the handoff on an actual case
Prepare a webinar follow-up for a chosen list, with a meeting-booked goal. Add an email using approved content, a wait and a branch with clear destinations. Test a lead on the list and another outside it. The eligible lead should start at the first step only when the program is Active. At the concurrency limit, inspect the Queued enrollment before continuing.
Now add global suppression for the eligible lead. Check that permission to re-enter does not admit that lead again. Have Marketing Operations explain the result using the audience, member and suppression records, then ask Marketing Manager to compare it with the intended contact policy.
What your team sees
- Active Programs — Approved, Active and Paused journeys with their owners, goals and member summaries.
- My Draft Programs — Preparation work owned by the current user.
- Programs Pending Approval — Journeys awaiting Marketing Manager’s decision.
Follow the work through
What it keeps track of
Data model- Programs
- A nurture program: one journey with an entry audience, an ordered step sequence, exit rules and a goal.
- 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.
- Program exit rules
- Exit criteria for a Program. A Lead exits when any Exit Rule row matches.
- Goals
- What a Program is trying to achieve. Reusable across Programs.
- Members
- A Lead x Program enrollment record. One row per Lead per active enrollment.
Who uses it
Permissions- Marketing Operations
- Builds the journey.
- Marketing Manager
- Owns its goal and decides program approval.
Set up CRM + Marketing Automation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.