Products & Profiles
A profile is linked to a class or course through a journey: a role in the product's context that carries the profile's lifecycle state there, such as applicant::submitted in "MBA 2026". A profile can have journeys in many products at once, at different states. See Lifecycle & Journeys for states, transitions, and withdrawal.
Each journey records:
| Detail | Meaning |
|---|---|
| State | The state::substate position in the lifecycle |
| Owner | The staff member responsible for the profile in that product |
| Campus | The campus the profile is linked to in that product |
| Potential | The lead-scoring rating (unknown, low, medium, high) |
| Withdrawn | Whether the profile has withdrawn from the product, with reasons |
Adding a Profile to a Product
Journeys are created in several ways:
- By staff — on the profile, Add to class (needs
core.institutions.profile_classes_change) or Add to course (needscore.institutions.profile_courses_change). Staff choose the product, and the campus when the product has several. The new journey starts asprospect::new. - By an application — a product field set to add applicants to the products they choose (see Applications)
- By automation — actions that add a profile to a product
- By import or the API
Add to class and Add to course only offer products the profile is not already in. Staff profiles cannot be added to classes, except as lecturers.
The same permissions let staff change a journey's state, withdraw a profile, and delete a journey.
Products in Forms and Applications
Application templates and forms offer products through a product field. In the field's options, staff pick the classes or courses applicants can choose, grouped by programme or subject.
Tick Auto-select future intakes on a programme or subject in the field's options to add every class or course created later under it to the field automatically. This keeps the field current when next year's intake is created.
When an application template has capacity automation on, fully booked products cannot be chosen (see Capacity & Pricing).
Products in Emails
Email templates can show the product an application is for, taken from the application's primary choice:
| Merge tag | Shows |
|---|---|
{{product_name}} |
Programme and class name, or subject and course name |
{{product_opens_on}}, {{product_closes_on}}, {{product_starts_on}}, {{product_ends_on}} |
The product's dates, in long form |
{{product_starts_on_as_yyyymmdd}}, {{product_starts_on_as_ddmmyyyy}} |
The same dates as YYYY/MM/DD or DD/MM/YYYY (also for the other dates) |
{{product_starts_on_datetime}} |
The date and time (also for the other dates) |
{{class_name}}, {{course_name}}, {{class_name_or_course_name}} |
The class or course name |
{{programme_name}}, {{programme_name_or_subject_name}} |
The programme name, or the subject's |
{{subject_name}}, {{subject_code}} |
The course's subject |
See Communications for how email templates work. For letters, see Merge Fields.
Products in Reports and Segments
Products are the context of most lists, segments, and reports:
- Segment rules can match profiles by the products they are in and their state there (see Segments).
- Archived products are left out of the product performance report (see Reports & Analytics).