Target Audience Controls - Article
Summary
Audience controls help you make a shared learning catalog relevant to different people. A customer, partner technician and employee can receive useful collections and messages without maintaining a separate Storefront for every group. The value comes from a clear audience model and dependable profile data, not from making the rules as complex as possible.
Storefront targeting determines which sections a person sees and can also influence what training they discover. It must be coordinated with activity availability, subscription entitlements and enrollment requirements. Previewing an audience helps you design the experience, but it is not the same as testing a real person's permissions or saving a section restriction.
Use this article to:
- Choose supported audience criteria and maintain their source data
- Configure organization, subscription, profile and Skill rules
- Combine Any, Exclude and AND/OR without unintended audiences
- Work safely in an audience preview context
- Verify Storefront, search and direct-link outcomes separately
Start with a useful audience model
Identify whose task differs and what should change for them. A service engineer might need product maintenance training; a sales partner may need positioning and demonstration skills. A regional customer may need different delivery languages or regulatory information. These differences can justify distinct sections within the same registered Storefront.
Treat business classifications and system permission roles separately. “Technical specialist” is typically a profile tag or job function, not a system role such as Course administrator. Audience criteria use the fields actually enabled on your platform; do not assume every organizational label is automatically an available rule.
| Illustrative audience | Useful presentation | Dependency to maintain |
|---|---|---|
| Product service technicians | Maintenance and troubleshooting collections for relevant product families | Current job-function and product-relevance profile data |
| Clinicians or healthcare professionals | Relevant device training and clinical-update collections | Appropriate professional classification and any separately configured eligibility rules |
| Regional customers or resellers | Local delivery options and suitable language messages | Organization hierarchy, country and language information |
| Subscription members | Thematic collections that make an included library easier to navigate | Active subscription status and correct subscription content |
| People ready for advanced practice | An advanced collection for a defined Skill or level | Skills enabled and a dependable record of the required Skill |
A practical planning model is organization and region + responsibilities and product relevance + supported Skill level. This is a design aid, not a formula you must enter into Eurekos. Start with the smallest set of dependable criteria that explains the business difference, and retain a useful general route where specialized information is missing.
Keep profile enrichment purposeful
Profile information can come from provisioning, identity, HR or customer systems, as well as authorized manual maintenance. Where questionnaire-to-profile updates are configured, a questionnaire can also collect relevant information and update supported profile fields.
Decide which system owns each value and who corrects it when the person's responsibilities change. Collect information because it improves a defined journey, rather than requiring a complete profile merely to make the catalog look personalized. Incorrect source data produces incorrect targeting even when the logical rule is configured perfectly.
For example, a partner technician who moves to a new product team may need an updated job-function or product tag. Adding a second duplicate Storefront section to compensate for the stale profile would hide the underlying maintenance problem.
Use relevance to support different business relationships
Audience controls let one maintained portfolio serve several practical and commercial purposes. A clinician can receive device-specific learning, a reseller can discover suitable regional offerings, and a service technician can see maintenance updates rather than sales material. Reuse shared activities where appropriate; vary the collection and explanation when the audience's task genuinely differs.
A particularly useful pattern is to change the message with the relationship. Present the value of a subscription to eligible non-members, then show topic-based member collections to subscribers. A customer who already has access needs help using it, not repeated sales prompts. A relevant advanced workshop can remain visible as a separate paid next step when it is not part of the subscription. Make that distinction explicit rather than implying that all visible training is included.
Build a small reference model before multiplying rules—for example, customer organization and region, responsibility and product relevance, then an appropriate Skill distinction. Agree who maintains each value. Where supported questionnaire-to-profile updates are configured, asking a useful question can improve later relevance; an ordinary questionnaire response does not automatically become an audience criterion.
This approach can reduce parallel catalog maintenance as new customer groups or product lines are introduced. It depends on reliable profile data and deliberate access design. Audience relevance is not proof of regulatory eligibility, nor does a profile tag create a commercial agreement. Keep those decisions in their appropriate enrollment, organization and subscription controls.
Worked audience examples for one shared portfolio
Translate the audience model into a few recognizable people before multiplying rules. In this example, Customer or Partner describes the business relationship and Service or Sales describes responsibility; they are not assumed to be system permission roles.
| Illustrative person | Useful presentation to design | Important boundary |
|---|---|---|
| A public visitor researching the academy | An introductory collection and a clear explanation of relevant training or subscription offers | Browsing does not establish a customer agreement, a user account or participation |
| A registered customer using the solar product family | Product-specific getting-started training and appropriate scheduled follow-up offers | Reliable supported profile values are needed; a product label in the page text does not create a targeting rule |
| A regional partner technician | Relevant regional and delivery-language collections, with installation and maintenance rather than sales-first guidance | Combine the intended criteria deliberately; region and organization are not automatically the same thing |
| A member of the service subscription | Useful included topic collections, with separate advanced workshops clearly identified where appropriate | Member presentation does not add a workshop to the subscription or waive its enrollment conditions |
| A new learner whose product information is missing | A deliberately maintained general introduction and a supported way to provide the missing information | A fallback experience must be designed; an unmatched profile does not automatically receive the right specialist collection |
Agree who maintains each value and when it should change. An identity integration may supply organization data, while a configured questionnaire-to-profile update can collect an appropriate product interest or responsibility. Ask only for information that will be used. Test the same person before and after a relevant profile change, as well as somebody who should not match the specialist section.
Define the audience on the section
Open Settings → Storefront → Registered users or Unregistered users, according to the visitor journey you are changing. Locate the specific row, text, banner, carousel or Search section and select Define target audience on that section's toolbar. This opens the section's audience-rule dialog, not the page-header Target audience preview control.

Select the criteria, review their combination and save the dialog. A defined-audience indicator identifies the restricted section. Complete the overall Storefront page save after your layout changes, then reopen the saved rule to confirm it.
With no section audience rule, the section is not restricted by that rule. This does not mean every activity in it becomes available to everyone: activity state, self-enrollment, organization filtering, subscriptions and other applicable configuration can still determine the content and available action.
Choose criteria supported by the visitor context
Registered users have profile and participation information that is unavailable before sign-in. An anonymous visitor has a more limited context.
| Criterion | Registered users | What to consider |
|---|---|---|
| Language | Profile language from the platform's enabled languages | A language rule selects an audience; it does not translate the content |
| Country | The enabled profile country field | Maintain it consistently and do not assume it is the visitor's current physical location |
| Organizations and suborganizations | Membership in the configured organizational structure | Choose parent and nested scope deliberately |
| Profile vocabularies and tags | Enabled fields such as Job function, Department or Interests | Interests uses Category; available labels depend on the enabled profile configuration |
| Subscriptions | The relevant subscription status | Use for a subscriber experience or an excluded promotional audience, not to create an entitlement |
| Skills | Supported Skills and levels where enabled | A presentation rule is not an enrollment prerequisite unless that is separately configured |
For unregistered visitors, language comes from browser context. Organization context can come from an organization-specific custom URL and its stored browser context until sign-in. There is no signed-in profile to supply job function, Skills or subscription status. Test that actual anonymous route instead of selecting an apparently similar registered profile.
Available profile criteria depend on feature activation and the relevant Settings → Forms → Profile and Settings → Tags configuration. If a criterion is absent, first check whether it is supported and enabled for the profile rather than assuming that activity tags automatically become profile criteria.
Include organizational branches deliberately
Choose the relevant parent organization and, where appropriate, specific suborganizations. Include all nested suborganizations supports a branch that should include its deeper levels and future descendants without maintaining a separate manual entry for each one.
Use the available Any of option when membership in any selected organization is sufficient. Without that choice, multiple selected values can require a match to all of them. Exclude organization / suborganization reverses the selected organization condition; it does not independently override every other condition in the rule.
Illustrative example: A customer academy wants a support collection for a parent customer organization and every regional service office beneath it. Including all nested suborganizations is easier to maintain than enumerating the existing offices, provided future offices should genuinely receive the same experience. If one branch needs a different service offer, design and test that exception explicitly.
Do not use a section's organization label as a substitute for activity-level organization governance. Some platforms apply additional organization filtering, and some privileged administrative roles can see more than an ordinary participant. Test with the relevant audience rather than using the administrator's own catalog as proof. Organization Visibility and Audience Targeting explains the Training Activity's organization layer.
Combine values and conditions carefully
There are two separate questions: how selected values within a criterion match, and how different criteria combine.
For criteria offering multiple values, the default can require all selected values. Enabling Any changes this to a match against at least one selected value. Exclude reverses that criterion's match. The available AND/OR controls then determine how the separate criterion results combine.
| Business intention | Appropriate logic | Outcome to verify |
|---|---|---|
| Serve either of two partner organizations | Organizations A and B with Any enabled | A member of either organization matches without needing both memberships |
| Serve engineers in one customer organization | Organization A AND the Engineer profile classification | A person must match both the customer context and the business classification |
| Serve either a professional group or a subscriber group | The relevant profile criterion OR the subscription criterion | Either route is intentionally sufficient; people matching only one are expected to qualify |
| Exclude a country while requiring an eligible job function | Excluded country condition AND the job-function condition | Matching the job function cannot defeat the country exclusion |
Do not treat Exclude as a global veto. In a rule equivalent to “Not Country A OR Engineer,” an engineer in Country A can still match the Engineer side. If exclusion from Country A is mandatory for this section, the country exclusion must remain a required condition—for example “Not Country A AND Engineer.” This distinction matters when a business or regulatory boundary is intended, not just a relevance preference.
Test people matching all conditions, only one condition, an explicitly excluded value and no relevant profile values. “The expected user can see the section” is not enough evidence that the exclusion works.
Use Skills and subscriptions for a meaningful next step
Where Skills are enabled, choose the relevant Skill and minimum level where that configuration is supported. Level-based Skills can use separate entries for the required selections. If Skill levels are later disabled, a level-based condition no longer provides the same level distinction; review the rule rather than assuming the earlier threshold still applies.
A useful example is an advanced maintenance collection for people with an introductory Skill, alongside a foundation collection for those who do not yet hold it. If the advanced activity must not accept enrollment until a qualification is held, configure the Training Activity's self-enrollment requirements as well. Hiding or showing the section alone is not the complete prerequisite mechanism. Self-enrollment Eligibility and Requirements explains how to configure those requirements.
Subscription criteria can reduce repeated sales messages to existing members and expose more helpful member collections. They do not change subscription ownership or grant access. Content from a specific-activity subscription can remain discoverable through that entitlement even when ordinary Storefront presentation is more restricted. An “all available Storefront training” subscription has a different relationship to Storefront visibility; do not assume every subscription uses identical content rules.
Separate presentation, discovery and permission to act
A section's audience is one layer in the journey. Search results and direct links introduce additional questions that a layout preview cannot answer on its own.
| Layer | What it controls | Important boundary |
|---|---|---|
| Section audience and row selection | Which sections and collections are presented to the visitor | Another section may expose the same activity |
| Storefront visibility and discovery | Which available offers can be returned through Storefront search, Global search and the Catalog API under the platform's configuration | Registered users can also have discovery routes through the public Storefront and active subscriptions |
| Direct-link enrollment | Whether someone with a direct activity link can proceed | A separate optional visibility-based enrollment block can extend Storefront visibility to this route |
| Activity enrollment and content access | Whether requirements are met and when the participant can start learning | Prerequisites, approval, payment, schedules and access restrictions remain distinct from section presentation |
Filter catalog trainings by Storefront visibility aligns discovery with intentionally exposed Storefront content and is normally enabled. Block enrollment by Storefront visibility is a separate optional platform setting and is normally disabled. Contact Eurekos Support when this platform-level behavior needs review; these are not switches on each section's audience dialog.
Consequently, removing an activity from one visible row may not remove it from search if another eligible section or entitlement still exposes it. Conversely, hiding it from ordinary discovery does not necessarily prevent a person with a direct link from enrolling. Existing participation can also provide a legitimate route through Global search or My overview.
Some platforms deliberately allow Custom rows or carousels to ignore ordinary Storefront filters. That exception can affect organization-related filtering as well as presentation. If the observed result contradicts an otherwise correct audience design, ask Support to review the platform configuration before treating a curated row as a secure restriction. Activity state and delivery availability still matter.
Preview an audience without mistaking it for a sandbox
The Target audience control in the Storefront page header opens Set a target audience. It selects an audience context for designing and reviewing the Storefront; the shield-style control on a section defines that section's saved restriction. They have different jobs.
Save pending Storefront changes before changing the header's audience context. After selecting the context, its active indicator and Reset identify that you are viewing a filtered design context. Reset clears that context; it is not a command to remove all saved audience rules from your sections.
The audience context is not read-only. New or edited sections can be saved with restrictions inherited from the active context. This is useful when building several sections for one audience, but it can also accidentally narrow a general section. Before editing, check the active context; afterward, inspect each affected section's actual saved audience rule.
Preview is also not masquerading as a particular account. For example, linked language alternatives can behave differently in the actual learner Storefront than in an administrative audience preview. Use representative account checks for the resulting discovery and enrollment journey, not only for the arrangement of sections.
Verify the audience journey
Use representative, authorized test profiles for the relevant organizations, languages, classifications, Skills and subscription states. Where permitted, account masquerade can help verify the actual user experience, but it is separate from the Storefront's audience preview. Include a genuinely anonymous route when the public Storefront is part of the design.
| Check | Expected result or evidence |
|---|---|
| Reopen the saved section rule | The intended criteria, Any/Exclude choices and cross-field logic are retained |
| Compare a matching user with a non-matching user | The section appears only where intended, with a useful alternative route where appropriate |
| Test each OR branch independently | A person matching only one branch is included only when that is the intended design |
| Test an excluded value combined with another positive condition | The rule's AND/OR behavior does not accidentally defeat the exclusion |
| Check a nested organization and a sibling outside the branch | The selected hierarchy scope includes and excludes the intended memberships |
| Check a subscriber and a non-subscriber | Member presentation and subscription-content entitlement are understood separately |
| Compare preview with the actual profile and delivery language | The end-user catalog and linked language alternatives behave appropriately |
| Search for the same activity and inspect other visible collections | Discoverability follows all relevant presentation routes, entitlements and platform settings |
| Follow an authorized direct activity link | Visibility-based enrollment restrictions and activity requirements produce the intended result |
| Check the real anonymous organization or browser-language route | The result reflects anonymous context rather than a simulated registered profile |
Visibility can be cached for up to five minutes after a change. Allow the cache to refresh and confirm the saved configuration before making repeated rule changes. A successful configuration save proves persistence, not the complete enrollment or access outcome.
Troubleshooting
| Problem | What to check |
|---|---|
| A criterion is missing | Check enabled features, profile-form fields and vocabularies; anonymous visitors have fewer supported criteria |
| A section matches nobody | Check actual profile values, default all-values matching, cross-field AND conditions, Skill levels and organization scope |
| An excluded person still matches | Check whether another OR branch makes the combined rule true; Exclude is not a universal veto |
| A new suborganization is omitted | Check whether Include all nested suborganizations is enabled rather than only selecting earlier descendants manually |
| A general section became narrowly targeted | Check whether it was created or edited while a header audience context was active |
| Target audience cannot be changed in the header | Complete or cancel pending Storefront edits and save the page before switching context |
| Reset did not remove a section's restriction | Reset clears the preview context; edit the section's saved audience rule separately |
| A hidden activity appears in search | Check other visible sections, the public catalog, existing participation, subscription entitlements and platform discovery settings |
| A direct link still allows enrollment | Check the separate optional visibility-based enrollment block and the activity's actual enrollment requirements |
| A curated item appears despite normal filters | Ask Support to review the Custom row/carousel filter exception and organization-related configuration |
| The administrator's view differs from the learner's | Check elevated permissions, actual profile and subscription data, language alternatives and the difference between preview and account context |
| A saved change is not yet visible | Allow for the visibility cache, then reopen the rule and test the correct visitor context |
FAQ
-
Is Target audience preview a read-only sandbox?
No. The header audience context supports editing as well as preview, and new or edited sections can inherit restrictions from that context when saved. Check the active context and inspect each affected section's saved audience rule.
-
Does Exclude always override the other audience conditions?
No. Exclude reverses its criterion, while AND/OR still determines the combined result. In a rule equivalent to Not Country A OR Engineer, an engineer in Country A can still match. Use a required exclusion condition, such as Not Country A AND Engineer, when that is the intended boundary.
-
How soon should a saved audience change affect visibility?
Storefront visibility can be cached for up to five minutes. Reopen the saved rule, allow the cache to refresh and test the intended visitor context before making further changes. Another visible section or subscription entitlement can also explain continued discovery.