Overview
A Segment is a reusable group of learners defined by a rule, such as "aged 55 or older" or "member of an affiliation". You use Segments to limit a price to one group of learners. Learners who match the rule see that price; others don't.
You build a Segment once and use it on as many sections as you like. To add prices that use a Segment, see Price Options (Managing Price Segments) - Genius CE & Enterprise.
How Segments Work
Each Segment has one rule. A learner belongs to the Segment when the rule is true for them.
Genius checks the rule when the learner views the catalog. Age is calculated from today's date.
A Segment is shared. Changing its rule changes who qualifies for every price that uses it, on every section.
Segments can be archived but not deleted.
Note: To see the Segments page, your role needs the Segments permission.
Segment Criteria
Criterion | How the rule reads | Notes |
Affiliation | is equal to an affiliation | Matches learners who are members of that affiliation. |
Age | a number, then Or Older or Or Younger | Calculated from a learner custom field of type DateTime, such as a date of birth field. If your organization has no such field, create one first. |
Zip Code | is equal to a value | Uses a learner custom field of type TextBox. The learner's address isn't used. |
Learner Custom Fields | For Text and Yes/No fields: is equal to a value | Each learner custom field is listed with its type (Text, List, Yes/No, Date). |
Primary Affiliation's Custom Fields | Pick an affiliation custom field | Uses the custom fields of the learner's primary affiliation. |
Create a Segment
Navigation: Administration → System Setup → Segments
The Segments page lists each Segment with its Name, Criterion, Rule and Status.
Image 12: The Segments page.
Click Create Segment.
Enter a Name.
Under Membership Rule, choose a criterion and complete the rule (see Segment criteria above).
Click Create Segment.
Image 13: Create Segment with an Age rule: 55 Or Older, using a date of birth custom field.
In the list, the rule appears in plain words, for example "If cf_birthdate is greater than or equal to 55", where cf_birthdate is the name of the custom field the rule uses.
Edit a Segment
Click Manage next to the Segment.
Change the Name or Membership Rule.
Click Update Segment.
⚠ Warning: A Segment is shared. Changing its rule changes who qualifies for every Price Segment that uses it, on every section.
Archive a Segment
Click Manage next to the Segment.
Click Archive.
Click Yes, Archive.
Image 14: Archive confirmation.
⚠ Warning: Archiving a Segment removes every Price Segment tied to it, on every section. This can't be undone. If a section is left with no Price Segment set to None, Learners outside its remaining Segments can no longer buy it.
The Segments list shows active Segments by default. To see archived Segments, change the Status filter to Archived. Archived Segments can't be chosen for new Price Segments.
Troubleshooting
Issue | Possible cause | Resolution |
Segments isn't in the System Setup menu | Your role doesn't have the Segments permission, or Segments isn't turned on for your organization. | Ask an administrator to add the Segments permission to your role. If that doesn't help, contact your Customer Success representative. |
Age isn't offered, or no field can be chosen | Your organization has no learner custom field of type DateTime. | Create a learner date of birth custom field, then create the Segment. |
A learner should qualify but doesn't see the price | The custom field the rule uses is empty or different on the learner's record. | Open the learner's record and check the field the rule uses. |
A Zip Code Segment matches nobody | The rule uses a custom field, not the learner's address. | Make sure learners fill in the custom field the rule uses. |
Best Practices
Name Segments for who they include, for example "Seniors 55+" or "ATSSA Members", so they're easy to find when adding prices.
Build each Segment once and reuse it. Don't create a copy for each section.
Check the custom field first. Age, Zip Code and custom field rules depend on learners having that field filled in.
Archive with care. Archiving removes every Price Segment that uses the Segment.