Setting Up Incentives - Article
Summary
Incentives configuration turns a learning-engagement goal into a program people can understand and trust. Choose who participates, which actions earn points, how achievements are recognized and whether balances should expire.
Use this article to:
- Configure eligibility, shop and leaderboard visibility
- Choose meaningful earning rules and sustainable point values
- Manage points-based and rule-based badges safely
- Plan expiry and verify the learner and operational outcomes
How Incentives Configuration Fits Together
This article guides administrators through setting up Incentives with both technical steps and business context, helping you understand not just how to configure incentives—but why you might choose one setup over another.
Incentives can support very different goals: partner enablement, customer loyalty, internal motivation, or campaign-based engagement. The configuration choices you make directly affect learner behavior, operational effort, and how meaningful rewards feel over time.
For this reason, the guide follows a recommended configuration sequence, explaining not only how to set up each element but why it matters and what outcomes to expect.
The first steps focus on four foundational areas:
- General settings define who can participate and how visible incentives are across the platform
- Rules determine which behaviors are rewarded and at what scale
- Badges convert accumulated effort into visible recognition and milestones
- Expiry schedules introduce urgency, seasonality, and long-term balance control
Each decision builds on the previous one. Starting with a clear use case—rather than configuring features in isolation—leads to incentive programs that are coherent, fair, and effective for both learners and administrators.

Step 1 — Enable Incentives in General Settings
Go to Settings → General and locate the Incentives configuration. Enabling Incentives unlocks the core controls that define who the incentive program is for and how it is experienced across the platform. Together, these choices answer a fundamental design question: “Who participates in this incentive program, and how visible and transactional should it be?”
These initial settings establish the foundation of your incentive strategy:
| Control | Decision and practical use |
|---|---|
| Scope | Choose platform-level or organization-based availability. Then check the separate earning rules, product visibility and recognition controls rather than assuming that availability creates independent local programs |
| Leaderboard | Decide whether a leaderboard is available and who can see it (e.g. participants, instructors, or specific roles). Leaderboards introduce visibility and competition and should be enabled only when comparison is meaningful and appropriate for the audience |
| Shop | Control whether the Incentives shop is available and which roles can access it. The shop defines where points are redeemed and should align with whether rewards are intended for learners, partners, or internal roles |

Platform-level Incentives
When Incentives are enabled at the platform level, all eligible users participate in a single, shared incentive economy. Points, badges, and rewards are earned and interpreted consistently across the entire audience.
This model works best when:
- The target audience is relatively homogeneous in role, access, and expectations
- Rewards represent brand value, recognition, or loyalty, rather than localized performance
- Consistency and visibility matter more than regional or organizational variation
In these scenarios, points function as a shared currency and badges become globally meaningful indicators of engagement, achievement, or expertise.
The trade-off is reduced flexibility. Administrators must design rules carefully to ensure that differences in role, access to content, or training volume do not create unintended advantages. In return, platform-level incentives offer simpler governance and stronger brand alignment.
Organization-level Incentives
Organization-level availability lets you restrict participation to users connected to organizations where Incentives is enabled. Open the relevant organization, then use More → Settings → Incentives to review its configuration. This can support a staged partner rollout or a program limited to an agreed audience.
Eligibility, product visibility, leaderboard scope and earning configuration are related but separate. Do not assume that enabling several organizations creates independent point values, badges or wallets for each one. The platform’s earning rules remain the configuration to inspect, while products and expiry schedules can have their own audience conditions.
For a pilot, identify the exact eligible organization and representative user profiles, then verify earning, visibility and redemption within that scope. Users with administrative Settings access may still manage the feature even when their own learner-facing shop access is excluded.

Leaderboards — Competition, Context, and Privacy
Leaderboards introduce visibility and comparison, making incentives social and competitive by nature. When used thoughtfully, they can significantly increase engagement—but they also raise privacy and perception considerations, especially in mixed or external audiences.
Enable leaderboards when:
- Friendly competition is culturally accepted and encouraged
- Visibility of achievement supports motivation and recognition
- Participants are comfortable being compared within a known peer group
Use caution or restrict leaderboards when:
- Audiences span multiple organizations, regions, or roles with different expectations
- Public comparison could be perceived as unfair, sensitive, or intrusive
- Privacy considerations outweigh the benefits of public ranking
Applying organizational restrictions addresses both engagement and privacy concerns. Limiting leaderboards to the user’s own organization ensures that participants are only compared with peers they are likely to know and relate to. This reduces hesitation, avoids unintended exposure across customer or partner boundaries, and aligns better with common organizational privacy expectations.
In practice, organization-scoped leaderboards strike a balance: they preserve the motivational benefits of competition while remaining acceptable from a governance, privacy, and brand perspective—making leaderboards far less prohibitive for many organizations.
Role Exclusions and Trust
Check the access controls separately for the Leaderboard and Shop. Where Exclude for roles is shown, the selected roles lose that access; the selection is not a list of roles you are granting access to.
This helps keep a program relevant when administrators, testers or instructors interact with learning differently from its intended audience. Excluding a learner-facing component does not necessarily remove the person’s administrative Settings permissions. Check both the feature experience and the management responsibility before concluding that a missing shop means the whole Incentives module is unavailable.
The Shop — Recognition vs. Rewards
The native shop turns points into tangible value. Enabling it is less a technical choice and more a strategic one: what kind of motivation are you designing for?
Incentives can work perfectly well without a shop. Points and badges alone can drive behavior when recognition, visibility, or status matter more than material rewards. In this setup, users still earn points, appear on leaderboards, and collect badges—but there is nothing to redeem.
Enable the shop when:
- You offer physical, digital, or voucher-based rewards
- You are prepared to manage fulfillment (shipping, codes, follow-up)
- Rewards are a clear part of the value proposition for the audience
Avoid enabling the shop when:
- Incentives are primarily symbolic or reputation-based
- Points are used to unlock status, access, or recognition
- You want to keep operational overhead to a minimum
Choosing whether to enable the shop defines whether your incentive program is about recognition, rewards, or a deliberate combination of both.

Step 2 — Defining What Is Rewarded (Rules)
With the scope defined, the next step is deciding what actions earn points. Rules are the backbone of the incentive system. They translate abstract business goals into concrete, repeatable behaviors and each rule should answer a simple but essential question: “What do we want participants to prioritize?”
Go to Settings → Incentives → Rules (the rules page assigns points to predefined platform actions).
Enter the intended point values and select Save on the Rules page. Reopen the rules to check the retained configuration, then use a representative learning action to verify its award. Saving values and processing an award are separate steps.
Incentive Rules and Point Logic — How Points Are Earned
Incentive rules define which participant actions are rewarded with points. Each rule represents a meaningful learning or engagement milestone—such as completing training, earning a certificate, or submitting feedback.
Rules are global: once enabled, they apply across the entire platform for all eligible users and content. This makes them powerful, but also important to calibrate carefully. The number of points assigned to each rule should reflect:
- The effort required to trigger it
- The volume of content users have access to
- The business importance of the behavior you want to encourage
Rules define the points awarded when the relevant learning action is processed. Use the point values to express effort and business importance, and verify the actual trigger before promising an award. Do not assume that changing a value recalculates past actions or that every repeat attempt earns another award. You can adapt the displayed terminology through platform translations to fit your program, while keeping the distinction from training virtual credits clear.
Terminology note: “Points” can be renamed using platform translations (e.g. coins, credits, tokens) to better match your business or brand language.

Incentive Rules — Actions and Triggers
The table below shows when each rule is triggered, helping administrators select the right rules without unintentionally inflating points or overlapping outcomes.
| Rule | Triggered When |
|---|---|
| Completed training | The Training Activity reaches its configured completion outcome |
| Completed course module | The course module reaches its configured completion outcome |
| Completed event module | The event module reaches its configured completion outcome |
| Completed assignment module | The assignment module reaches its configured completion outcome |
| Earned certificate | A certificate is earned under its configured issuance rules |
| Played a video | The video passes the configured viewing threshold |
| Completed test | A test that generates a score is completed; completion and passing are different outcomes |
| Passed SCORM | The package reports the passed outcome used by the rule |
| Attended an event | The participant’s attendance is recorded |
| Submitted questionnaire | The questionnaire submission is recorded |
Design Guidance: Avoid Point Inflation
Because rules apply across all content, assigning points is not just about importance—it’s about scale.
For example:
- If users have access to many videos, assigning points to video plays should be modest
- Certificates or completed trainings often justify higher point values, as they represent aggregated effort
- Questionnaires and attendance rewards should align with whether feedback and presence are core behaviors or secondary signals
Well-balanced rules ensure that:
- Points feel earned, not automatic
- Rewards remain aspirational, not guaranteed
- Incentives support engagement without distorting learning priorities
Keep the rules easy to explain and the potential point volume deliberate. An action you choose not to reward should not promise points to learners. The Rules interface describes leaving criteria blank to exclude them and may display zero values; review the saved value and verify the intended behavior rather than treating a blank or zero as a reward amount.
Budget the possible earning, not only the attractive reward
For example, 100 eligible learners who can each earn 100 points create a possible 10,000-point exposure. Compare that earning opportunity with product quantities and realistic redemption. These are illustrative planning figures, not a platform calculation or an observed result.
Also check overlapping milestones. A learning journey can include training, module, certificate and assessment events; decide which of those outcomes your program should reward. Do not announce a total based on adding every possible rule without testing the actual journey and repeat behavior.
Make the Incentive Program Explicit for Learners
Incentive programs only work if participants understand that they exist, how they work, and why they should care. You cannot assume learners will discover this on their own—especially when incentives are layered on top of learning activities rather than being the learning itself.
A common and effective approach is to introduce the incentive program explicitly at login, particularly for the target audience it applies to.
Recommended Practice: Simple Program Introduction
One of the most effective ways to onboard users is a short explainer video or message shown when learners first log in (or when a campaign starts). This introduction should clearly cover:
- What the incentive program is for
- How points are earned (at a high level, not every rule)
- What points can be redeemed for—or what badges represent
- Where users can see their points, rewards, and progress
- Any key conditions (time limits, expirations, eligibility)
This sets expectations early and prevents confusion later—especially around why points appear, reset, or expire.
Keep It Simple — for You and for Them
From both a learning and operational perspective, simplicity wins:
- Learners will not intuitively understand complex rule combinations
- Overly granular point logic is difficult to explain and harder to trust
- Clear, predictable rewards reinforce motivation better than clever mechanics
Design incentive programs that are:
- Easy to explain in under a minute
- Aligned with a small number of meaningful actions
- Tailored to the specific audience and program goals
If a learner cannot quickly answer “What do I need to do, and what do I get?”, the program is likely too complex. Well-designed incentives feel intuitive, transparent, and purposeful—supporting engagement without distracting from learning.
How Users Experience Points
Users receive on-screen notifications when they earn points, including what action triggered the reward. This immediate feedback is an important part of the incentive experience.
Notifications are delivered asynchronously and may appear after a short delay or in a later session. Eligible users can review the available balance and notification record. Header, profile, shop and leaderboard availability still depends on the configured experience.
Step 3 — Adding Recognition Through Badges
Badges shift motivation from “earning more” to “reaching something.” They represent accumulated achievements and are especially effective for marking milestones and long-term progress. When designed intentionally, badges help learners understand where they are in a journey, not just how many points they have collected.
To configure badges, go to Settings → Incentives → Badges and click Create. Once multiple badges are set up, they can be managed from the Badge Overview, which provides a clear list of badge titles and types for easy administration.
When creating a badge, administrators define:
| Control | What it changes | Decision or limitation |
|---|---|---|
| Title | Names the achievement shown to learners | Use a title that explains the milestone |
| Select badge / Badge image | Chooses the badge illustration or your own square SVG/PNG | Use a recognizable image with a suitable background |
| Type | Chooses Points-based or Rule-based | The type is fixed after creation |
| Badge score | Sets the point threshold for a Points-based badge | Match it to attainable effort and the meaning of the milestone |
| Rule | Selects the achievement for a Rule-based badge | The selected rule is fixed after creation |
| Badge can be earned multiple times | Allows repeated awards where enabled | When disabled, the badge can be earned once; review existing awards separately from future earning |
Select Save to create the badge, then check its Title and Type in the Badges list. Review the immutable choices before saving; use the management guidance below when changing a badge that has already been awarded.
An optional setting allows a badge to be earned multiple times. When enabled, each achievement is counted and reflected in the user profile and leaderboards. This is particularly useful for long-running programs or scenarios where tangible rewards are limited or not used. This option is available for both badge types.
Badges can function independently of rewards, providing recognition even when no shop or products are enabled. Used on their own, they still reinforce progress, achievement, and engagement across the platform.

Points-Based Badges and Tiered Progression
Points-based badges reward accumulated effort over time rather than a single action. A badge is configured with a point threshold (for example, 100 points), which represents a meaningful level of engagement in your incentive program.
- Single-award badge: The badge is earned once when the user reaches the threshold and best used for clear milestones such as “Qualified Partner” or “Program Completion.”
- Repeatable badge (tiered progression): When “Badge can be earned multiple times” is enabled, the badge becomes a tiered progression marker. E.g., a badge threshold is 100 points. The user earns points continuously:
- At 100 points → badge is awarded (1st time)
- At 200 points → badge is awarded again (2nd time)
- At 300 points → badge is awarded again (3rd time), and so on
Points are not reset after earning the badge. Instead, each new threshold crossing awards the badge again, signaling sustained engagement rather than a one-off achievement.
Tiered point-based badges are especially effective when you want to:
- Encourage ongoing participation, not just completion
- Reward consistency and volume of effort
- Create visible progression without forcing complex rule logic
- Support long-running programs, seasonal campaigns, or recurring enablement
Rule-Based Badges — Targeted Recognition
Rule-based badges are awarded when a specific action or condition is met, rather than through accumulated points. They are ideal for recognizing clear milestones, qualifications, or behaviors that matter independently of overall engagement volume.
Unlike points-based badges, rule-based badges are typically earned once per rule occurrence and communicate what was achieved, not how much effort was invested over time.
Use rule-based badges when you want to:
- Mark formal achievements (e.g. certification earned, event attended)
- Signal readiness, qualification, or compliance
- Reward specific actions without encouraging point farming
- Keep badge meaning explicit and easy to understand
Rule-based badges work best when they are intentional and limited, reinforcing clarity rather than noise.
Choose a rule-based badge for a meaningful event
Select the required action from the available rules. The trigger table in Step 2 explains the action categories; use it to distinguish a test completion, a passed package, a certificate and a completed training. Those outcomes carry different meanings.
Describe what the badge recognizes in language the learner can understand. A badge for completing introductory training should not imply professional authorization, and a point threshold should not be presented as a formal certification requirement. Use the appropriate certificate and activity configuration for those separate outcomes.
Managing Badges
Open Settings → Incentives → Badges to create, edit or delete a badge. Its Type cannot be changed after creation, and the selected rule for a rule-based badge is also fixed. These are product limits, not simply recommendations.
A points-based threshold can be changed. Previously awarded badges and their counters remain, while progress is recalculated under the new requirement. Changing whether a badge can be earned multiple times affects future awards. Before changing a threshold, consider how the updated progress will be explained to people already participating.
If the achievement should mean something substantially different, create a new clearly named badge. Deleting a badge removes it for all users, including Profile and Leaderboard. It is not a tool for removing one person’s award.

Points-Based vs Rule-Based Badges — Comparison Overview
| Aspect | Points-Based Badges | Rule-Based Badges |
|---|---|---|
| What they represent | Cumulative effort and ongoing engagement | Completion of a specific requirement or milestone |
| How they are earned | By reaching defined point thresholds | By completing a defined action or condition |
| Trigger type | Accumulation over time | Configured action or event |
| Progress visibility | Gradual progression toward next badge tier | Binary: earned or not earned |
| Learner question answered | “How far have I progressed?” | “Have I completed this requirement?” |
| Typical timing | Earned after sustained activity | After the configured action is processed |
| Dependency on volume | Depends on number of rewarded actions available | Independent of overall activity volume |
| Use across campaigns | Well suited for long-running or recurring programs | Best for fixed requirements or checkpoints |
| Sensitivity to rule changes | Changed thresholds adjust progress; previously issued badges remain | Type and selected rule are fixed; earning-frequency changes affect future awards |
| Role in gamification | Motivation, momentum, friendly competition | Validation, recognition, qualification |
| Best used for | Engagement, loyalty, prioritization, participation | Recognition of a defined milestone within the wider learning program |
| Common examples | Bronze / Silver / Gold tiers | “Certified”, “Onboarding Complete”, “Event Attended” |
| Works well with | Leaderboards, shops, seasonal campaigns | Certificates, audits, access control |
| Risk if misused | Over-inflated points if rules are too broad | Badge fatigue if too many are created |
Step 4: Configure Expiry Schedules — Driving Momentum
Expiry schedules let you align a point-balance reset with a defined audience and time. They can support annual partner programs, seasonal initiatives or a planned refresh, but the reset must be understandable to the people who earned the points.
Open Settings → Incentives → Expiry schedules and select Create. Give the schedule an internal title explaining its purpose, choose its target audience and configure Specific date or Recurring expiration. Review the available timing controls and communicate the actual deadline and cadence.
Select Save to retain the schedule. Review the saved audience and expiry configuration before relying on it. A scheduled future reset is not evidence that points have already expired or that a reminder has been delivered.
| Choice | When it helps | Consequence to explain |
|---|---|---|
| Specific date | A one-off program or a deliberately fixed reset | The eligible audience’s affected points expire at the configured time |
| Recurring expiration | A continuing program with an agreed reset cycle | People need to understand the repeated earning and redemption horizon |
| Target audience | A reset intended for specific countries, organizations or job functions | The matching profile determines who is affected |
| Send expiry reminder email | Give learners time to act before expiry | The configured reminder needs useful timing and a clear explanation |
| Send email after points reset | Explain the completed reset | The message should identify the program and what happens next |
Target Audience and Logic
The audience choices are Country, Organization and Job function, with multiple values and AND/OR combinations. Several values within a criterion broaden that criterion; AND between different criteria narrows the overall audience, while OR broadens it. Check the actual matching profiles rather than assuming a title defines scope.
Use expiry to support a clear program
Expiry can encourage timely participation and redemption, keep dormant balances manageable and align the program with a product or partner cycle. It can also feel unfair when people have few earning opportunities or need a long time to reach a useful reward. Explain the horizon before people invest effort, and consider whether persistent recognition is more appropriate than a reset.
An audience-specific schedule does not establish separate campaign wallets. Do not promise that a reset affects only points earned for one campaign unless that exact behavior is confirmed for your setup. Check overlapping schedules before adding another reset, and verify the effects on balance and recognition separately.
Maintain expiry communication and schedules
Use the schedule’s Send expiry reminder email and Send email after points reset options to control communication for that reset. Explain who is affected, when points expire and where rewards can be reviewed. Administrators maintain reusable message content under Settings → Email sending → System emails → Incentives; Email Sending - Article covers that central configuration. Search, edit or delete schedules from the Expiry schedules overview after reviewing the audience and future resets affected by the change.
For example, a partner program can publish its annual earning and redemption period, send a useful reminder and prepare the next period’s learning offers. The program owner should coordinate reward stock and fulfillment with that timeline rather than treating expiry as an isolated technical setting.


Verify the configuration
Check the intended learner and operational owner, including the relevant role and organization scope. A saved setting and a completed downstream outcome are different evidence.
| Scenario or check | Expected result or evidence |
|---|---|
| An intended learner and an excluded role sign in | Eligibility and shop/leaderboard access match their actual settings |
| A user belongs to an enabled organization | Their earning and redemption experience follows that scope; organization membership is not assumed to create independent rules |
| One representative learning journey is completed | The actual milestone awards and viewing thresholds match the program explanation |
| A badge threshold or earning frequency changes | Existing awards remain distinct from recalculated progress and future awards |
| A proposed badge deletion is reviewed | The owner understands that deletion affects all users, not one award |
| An expiry schedule is reviewed | The actual audience, timing, overlap and communication match the intended reset |
Troubleshooting
| Problem | What to check |
|---|---|
| A user cannot see the shop or leaderboard | Check feature enablement, organization eligibility and each component’s role exclusions separately |
| The award differs from the expected points | Check the saved earning rule and actual learning event; do not assume completion, attendance, score and passing are interchangeable |
| A video has not generated an award | Check the configured viewing threshold and processing before treating a play click as a completed viewing outcome |
| A badge’s type or rule cannot be changed | These are fixed after creation; use a new badge for a different achievement |
| Progress changed after a threshold edit | Compare the new requirement with current progress and previously issued awards |
| A reset affects an unexpected audience | Review saved profile criteria and AND/OR logic, plus overlapping schedules, before adding another reset |
FAQ
-
What happens to leaderboards when learners belong to multiple organizations?
A prerequisite for this behavior is that Incentives are restricted to specific organizations.
When a learner is associated with multiple organizations, leaderboard visibility follows the organizational context in which the incentives program is configured.
- If incentives are segmented by organization, the learner will appear on the leaderboard within each relevant organization, but comparisons remain isolated within that specific audience. This ensures fair benchmarking and prevents unintended cross-organizational visibility
- If a learner belongs to multiple organizations included within the same incentives scope, they appear in a combined leaderboard view spanning all learners in those organizations, sorted according to their overall ranking within that defined scope
Filters can further refine the leaderboard, allowing learners and administrators to focus on a specific organizational relationship when needed.
-
Are Incentives points the same as training virtual credits?
No. Incentives points belong to the learning recognition and reward-redemption program. Organization virtual credits are a separate way to fund training enrollment where configured. A balance in one mechanism should not be treated as a balance in the other.
-
Does changing or deleting a badge affect existing awards?
Changing a points threshold adjusts progress while previously awarded badges and counters remain. Type and the selected rule are fixed after creation. Deleting the badge removes it for all users, including Profile and Leaderboard; it is not an individual-award removal action.
-
Why can I earn points but not see the shop or leaderboard?
The shop and leaderboard are separate configurable components. Their availability can depend on enablement, role exclusions and organization eligibility. Check the component access rather than assuming that a points balance enables every part of Incentives.
-
Why has my points notification not appeared yet?
Awards and notifications are processed asynchronously. A message can appear after a short delay or in a later session if you leave first. Check the available balance and notification record before repeating the learning action.