Understanding Reward Activity Types

The Rewards Module supports eleven distinct activity types that enable organizations to incentivize a wide range of user behaviors and achievements. Each activity type has unique characteristics, assignment methods, and configuration options that determine how rewards are distributed and what actions qualify for recognition. Understanding the differences between activity types helps administrators design effective reward programs that align with organizational objectives.

Overview of Activity Types

The Rewards Module categorizes activity types into two main groups:

Automatically Tracked Activities:

• System monitors activity completion in real-time
• Rewards are distributed automatically when activities are completed
• Conditional logic can refine eligibility criteria
• No manual claim submission required
• Provides immediate user gratification

Manual Claim Activities:

• Users submit claims through customizable forms
• Administrators or program managers review and approve claims
• Enables documentation collection and validation
• Supports activities that cannot be automatically tracked
• Requires human judgment for approval

Automatically Tracked Activity Types

Login

Description:
Rewards users for authenticating to the portal and accessing the platform.

Assignment Method:

• Automatic only

Use Cases:

• Encourage regular portal engagement and habit formation
• Reward consistent platform usage
• Increase daily or weekly active user counts
• Build momentum in new program launches
• Foster community connection through regular visits

Configuration Considerations:

• Frequency Settings: Typically use "Every Time" or "Every Month" to reward repeated logins
• Value: Keep values modest as logins are easy actions requiring minimal effort
• Conditional Logic: Not supported

Example Scenarios:

• Reward 10 points for each login (Every Time) to encourage daily visits
• Reward 100 points for 20 logins per month (Every Month, Frequency: 20) to encourage sustained engagement
• Reward 50 points for first login (Once) as onboarding welcome

Best Practices:

• Combine with other activities to avoid rewarding logins without meaningful engagement
• Monitor for gaming behaviors where users log in repeatedly without genuine participation
• Consider time-based frequencies (daily, weekly, monthly) rather than unlimited "Every Time"

Content View

Description:
Rewards users for viewing specific content items within the portal such as articles, documents, announcements, or knowledge base entries.

Assignment Method:

• Automatic only

Use Cases:

• Drive awareness of important announcements or policy updates
• Increase knowledge base engagement and self-service adoption
• Promote specific content campaigns or featured articles
• Encourage exploration of resource libraries
• Track content consumption for communications effectiveness

Configuration Considerations:

• Frequency Settings: Typically use "Once" per content item or "Every Time" for repeated views
• Value: Moderate values for important content, lower values for general browsing
• Conditional Logic: Not supported

Example Scenarios:

• Reward 25 points for viewing the Q1 Partner Update announcement (Once)
• Reward 50 points for viewing Product Launch Guide (Once)
• Reward 10 points for viewing any knowledge base article (Every Time)

Best Practices:

• Use "Once" frequency for specific critical content to ensure all users consume it
• Avoid over-rewarding content views as users may open content without actually reading it
• Combine content view rewards with comprehension checks or follow-up activities
• Track which content generates most engagement to inform future content strategy

Course Completion

Description:
Rewards users for completing training courses or learning paths in the Training Module.

Assignment Method:

• Automatic only

Use Cases:

• Incentivize professional development and skill building
• Drive completion of required compliance or certification training
• Encourage exploration of training catalog
• Support onboarding and product knowledge development
• Build competency in strategic product lines or solutions

Configuration Considerations:

• Training Course Field: Select a specific course to reward only that course completion, or leave blank to reward any course completion
• Frequency Settings: Typically "Once" for specific required courses, "Every Time" for catalog exploration
• Value: Higher values for difficult, lengthy, or strategic courses; lower values for short introductory content
• Conditional Logic: Supported - can add conditions based on course completion status, scores, or other course attributes

Example Scenarios:

• Reward 500 points for completing Product Certification Level 1 (Once, specific course, conditional logic: Score >= 80%)
• Reward 100 points for completing any course (Every Time, no specific course selected)
• Reward 1,000 points for completing Advanced Technical Training (Once, specific course)

Conditional Logic Examples:

• Condition: Course Status = Completed AND Course Score >= 80
• Condition: Course Category = Product Training
• Condition: Course Duration >= 4 hours

Best Practices:

• Use higher rewards for strategic courses aligned with business priorities
• Implement score-based conditional logic to ensure quality completion
• Scale rewards based on course difficulty and time investment
• Monitor completion rates to ensure rewards are motivating but not excessive
• Consider tiered rewards for course series or learning paths

Deal Registration

Description:
Rewards users for submitting deal registrations through the Deal Registration Module, which creates leads in the integrated CRM system.

Assignment Method:

• Automatic or Claim Submission

Use Cases:

• Encourage partners to register sales opportunities early
• Increase pipeline visibility and sales forecasting accuracy
• Drive competitive deal protection requests
• Reward proactive opportunity identification
• Build partner engagement in joint selling efforts

Configuration Considerations:

• Assignment Method: Automatic is recommended for immediate gratification; Claim Submission enables additional documentation collection
• Frequency Settings: Typically "Every Time" to reward all deal registrations
• Value: Moderate to high values based on deal registration strategic importance
• Conditional Logic: Supported - can add conditions based on deal registration fields such as deal size, region, product, or status

Example Scenarios:

• Reward 200 points for any deal registration submission (Every Time, automatic)
• Reward 500 points for deal registrations in target product categories (Every Time, automatic, conditional logic: Product Category = Strategic Solution)
• Reward 1,000 points for large deal registrations (Every Time, automatic, conditional logic: Estimated Deal Value >= $100,000)

Conditional Logic Examples:

• Condition: Deal Size >= 50000
• Condition: Region = North America OR Region = Europe
• Condition: Product Line = Next-Gen Platform
• Condition: Competition Identified = Yes

Best Practices:

• Use automatic assignment for immediate recognition and motivation
• Implement conditional logic to reward quality registrations meeting specific criteria
• Scale rewards based on deal size or strategic importance
• Monitor for registration quality to ensure users aren't gaming the system
• Consider higher rewards for registrations that convert to qualified opportunities

Qualified Deal Registration

Description:
Rewards users based on qualified opportunities in the CRM system, representing deals that have progressed beyond initial registration to validated opportunities.

Assignment Method:

• Automatic or Claim Submission

Use Cases:

• Reward partners for advancing deals through qualification stages
• Incentivize opportunity progression and sales pipeline health
• Recognize successful deal closure and revenue generation
• Scale rewards based on deal value using percentage-based calculations
• Drive focus on high-value opportunities

Configuration Considerations:

• Assignment Method: Automatic is recommended for real-time recognition
• Reward Value Type: Fixed Amount for consistent rewards, or Percentage Of for value-scaled rewards
• Amount Field: Select opportunity currency field (Deal Amount, Revenue, Expected Revenue, etc.) for percentage calculations
• Frequency Settings: Typically "Every Time" to reward each qualified opportunity
• Value: Can be substantial, especially for percentage-based rewards on large deals
• Conditional Logic: Supported - can add conditions based on opportunity fields such as stage, close date, product, or deal characteristics

Example Scenarios:

• Reward 1,000 points for each closed-won opportunity (Every Time, automatic, conditional logic: Opportunity Stage = Closed Won)
• Reward 2% of deal amount for qualified opportunities (Every Time, automatic, Reward Value Type: Percentage Of, Amount Field: Deal Amount)
• Reward 5,000 points for opportunities over $500,000 (Every Time, automatic, conditional logic: Deal Amount >= 500000)

Percentage-Based Reward Configuration:

• Select Reward Value Type: Percentage Of
• Select Amount Field: Choose the currency field from the opportunity (Deal Amount, Revenue, etc.)
• Enter Value: Enter the percentage (e.g., enter "2" for 2%, not "0.02")
• System calculates reward automatically: If Deal Amount = $50,000 and Value = 2, reward = $1,000 (or 100,000 points)

Conditional Logic Examples:

• Condition: Opportunity Stage = Closed Won
• Condition: Close Date >= 2025-01-01 AND Close Date <= 2025-12-31
• Condition: Deal Amount >= 100000
• Condition: Product Category = Enterprise Solutions

Best Practices:

• Use percentage-based rewards to align incentives with deal value
• Implement stage-based conditional logic to reward at appropriate qualification milestones
• Consider separate activities for different opportunity stages (qualified, closed-won)
• Monitor reward distribution to ensure budget alignment
• Set minimum deal thresholds to focus rewards on significant opportunities

Idea Submission

Description:
Rewards users for submitting ideas through the Ideas Module, encouraging innovation and continuous improvement contributions.

Assignment Method:

• Automatic or Claim Submission

Use Cases:

• Foster innovation and creative problem-solving
• Crowdsource product improvements and feature requests
• Encourage customer feedback and enhancement suggestions
• Build community engagement through collaborative ideation
• Recognize contributors who share valuable insights

Configuration Considerations:

• Assignment Method: Automatic rewards all submissions immediately; Claim Submission enables selective recognition of quality ideas
• Frequency Settings: Typically "Every Time" to encourage ongoing ideation, or limit with monthly/quarterly frequencies
• Value: Moderate values to encourage participation without over-incentivizing volume over quality
• Conditional Logic: Supported - can add conditions based on idea category, status, or other attributes

Example Scenarios:

• Reward 100 points for any idea submission (Every Time, automatic)
• Reward 500 points for ideas in strategic categories (Every Time, automatic, conditional logic: Idea Category = Product Enhancement)
• Reward 1,000 points for approved ideas (Claim Submission, reviewed based on idea acceptance)

Conditional Logic Examples:

• Condition: Idea Category = Customer Experience
• Condition: Idea Status = Approved
• Condition: Idea Type = Product Feature Request

Best Practices:

• Balance automatic rewards (encouraging volume) with quality-based conditional logic
• Consider tiered rewards: lower for submission, higher for accepted/implemented ideas
• Monitor idea quality to ensure rewards aren't incentivizing low-value submissions
• Recognize idea implementation separately from submission
• Provide feedback on submitted ideas to maintain ongoing engagement

Event Registration

Description:
Rewards users for registering for events such as webinars, conferences, training sessions, or partner summits through the Events Module.

Assignment Method:

• Automatic or Claim Submission

Use Cases:

• Drive event registration and attendance
• Build awareness of upcoming events and programs
• Incentivize participation in strategic events
• Increase webinar and training session attendance
• Reward early registration for better event planning

Configuration Considerations:

• Assignment Method: Automatic is recommended for immediate confirmation and encouragement
• Frequency Settings: Typically "Every Time" to reward each event registration
• Value: Scale based on event importance, duration, and strategic value
• Conditional Logic: Supported - can add conditions based on event type, date, location, or other attributes

Example Scenarios:

• Reward 50 points for any event registration (Every Time, automatic)
• Reward 500 points for annual partner summit registration (Every Time, automatic, conditional logic: Event Name = Annual Partner Summit)
• Reward 200 points for webinar registrations (Every Time, automatic, conditional logic: Event Type = Webinar)

Conditional Logic Examples:

• Condition: Event Type = Conference
• Condition: Event Date >= 2025-06-01 AND Event Date <= 2025-09-30
• Condition: Event Location = Las Vegas
• Condition: Event Category = Technical Training

Best Practices:

• Use higher rewards for strategic events requiring significant time commitment
• Consider bonus rewards for early registration to aid event planning
• Implement separate rewards for registration vs. attendance if tracking is available
• Scale rewards based on event value and organizational priorities
• Monitor registration patterns to optimize event scheduling and promotion

Classroom Training

Description:
Rewards users for attending in-person or instructor-led classroom training sessions, recognizing time investment and learning commitment.

Assignment Method:

• Automatic or Claim Submission

Use Cases:

• Encourage attendance at in-person training events
• Recognize time and travel investment for classroom learning
• Drive participation in certification programs
• Support hands-on skill development
• Build community through in-person learning experiences

Configuration Considerations:

• Assignment Method: Claim Submission is common for classroom training to verify attendance
• Frequency Settings: Typically "Every Time" to reward each training attendance
• Value: Higher values than online courses to reflect time, travel, and scheduling investment
• Conditional Logic: Supported - can add conditions based on training type, location, duration, or certification level

Example Scenarios:

• Reward 1,000 points for attending Technical Certification Workshop (Every Time, claim submission)
• Reward 2,500 points for multi-day classroom training (Every Time, claim submission, conditional logic: Training Duration >= 3 days)
• Reward 500 points for regional training events (Every Time, claim submission, conditional logic: Event Location = Regional Office)

Conditional Logic Examples:

• Condition: Training Type = Certification
• Condition: Training Duration >= 8 hours
• Condition: Training Location = Corporate Headquarters
• Condition: Certification Level = Advanced

Best Practices:

• Use claim submission to collect attendance verification and training feedback
• Scale rewards based on training duration, complexity, and travel requirements
• Consider travel expense reimbursement in addition to points/cash rewards
• Verify attendance through sign-in sheets, certificates, or trainer confirmation
• Recognize both participation and successful certification completion

Claimable Activity

Description:
A flexible activity type that allows users to submit claims for activities that cannot be automatically tracked by the system. This catch-all category supports any behavior or achievement that requires documentation and manual validation.

Assignment Method:

• Claim Submission only (automatic assignment not available)

Use Cases:

• Reward behaviors not captured by other activity types
• Recognize achievements requiring documentation
• Support custom organizational initiatives
• Incentivize activities in external systems
• Enable flexible reward distribution for unique circumstances

Common Claimable Activity Examples:

• Customer reference calls or testimonials
• Social media mentions and engagement
• Case study participation and content contribution
• Speaking engagements at industry events
• Customer success stories and win documentation
• Community forum participation and support
• External certification achievements
• Trade show booth staffing
• Co-marketing activity participation
• New partner recruitment

Configuration Considerations:

• Assignment Method: Claim Submission only
• Claim Form: Design comprehensive forms collecting all information needed for validation
• Frequency Settings: Varies widely based on activity nature
• Value: Determine based on activity effort, impact, and strategic importance
• Conditional Logic: Not supported (validation occurs through human review)

Example Scenarios:

• Reward 500 points for customer reference calls (claim submission with call details, customer name, date)
• Reward 1,000 points for social media posts about company products (claim submission with post link, engagement metrics)
• Reward 2,000 points for speaking at industry conferences (claim submission with event details, presentation topic)

Claim Form Design for Claimable Activities:

• Activity Description: Text field for detailed description of what was done
• Date Completed: Date field for activity completion date
• Supporting Evidence: Long text field for documentation, links, or proof
• Additional Context: Fields specific to activity type (customer name, event name, post URL, etc.)
• Checkbox Confirmations: Verify activity meets eligibility criteria

Best Practices:

• Create clear, specific activity descriptions explaining what qualifies
• Design claim forms that collect essential validation information
• Provide examples of successful claims in program descriptions
• Establish clear approval criteria shared with users
• Review claims consistently and provide detailed feedback on rejections
• Monitor claim patterns to identify additional activities that could be automated
• Consider separate claimable activities for distinct behavior types rather than one catch-all

Choosing the Right Activity Type

Decision Framework:

1. Can the activity be automatically tracked in Magentrix?

   • Yes → Use appropriate automatic activity type (Login, Content View, Course Completion, etc.)
   • No → Use Claimable Activity

2. Does the activity require documentation or validation?

   • Yes → Use Claim Submission assignment method (even for trackable activities)
   • No → Use Automatic assignment method

3. Does the activity involve external systems or manual processes?

   • Yes → Use Claimable Activity with comprehensive claim forms
   • No → Use specific activity type matching the behavior

4. Is quality verification needed before reward distribution?

   • Yes → Use Claim Submission or implement conditional logic
   • No → Use Automatic assignment

Activity Type Selection Examples:

Activity Type Limitations and Considerations

Conditional Logic Support:

• Supported: Deal Registration, Qualified Deal Registration, Course Completion, Idea Submission, Event Registration
• Not Supported: Login, Content View, Classroom Training, Claimable Activity

Assignment Method Flexibility:

• Automatic Only: Login, Content View, Course Completion
• Automatic or Claim Submission: Deal Registration, Qualified Deal Registration, Idea Submission, Event Registration, Classroom Training
• Claim Submission Only: Claimable Activity

Integration Dependencies:

• Course Completion: Requires Training Module
• Deal Registration: Requires Deal Registration Module and CRM integration
• Qualified Deal Registration: Requires CRM integration with opportunity object
• Idea Submission: Requires Ideas Module
• Event Registration: Requires Events Module
• Classroom Training: May require external training management system integration

Best Practices Across All Activity Types

Strategic Activity Selection:

• Choose activity types that directly align with organizational objectives
• Prioritize activities with measurable business impact
• Balance automatic activities (lower administrative burden) with claim-based activities (higher validation)

Appropriate Value Calibration:

• Scale rewards based on effort, time investment, and strategic importance
• Test reward values with pilot groups before broad deployment
• Monitor participation rates and adjust values to optimize engagement

Clear Activity Descriptions:

• Write descriptions that explicitly state what qualifies for rewards
• Include examples of qualifying activities
• Specify any quality requirements or conditional criteria
• Communicate approval processes and timelines for claim-based activities

Frequency Optimization:

• Match frequency settings to desired behavior repetition
• Use "Once" for one-time onboarding or milestone activities
• Use time-based frequencies (Monthly, Quarterly) for recurring behaviors
• Use "Every Time" for high-frequency, low-value activities

Conditional Logic Precision:

• Implement conditional logic to ensure quality standards
• Test conditions thoroughly before activation
• Document conditional logic for future reference and consistency
• Review conditional logic effectiveness based on distribution patterns

Regular Performance Review:

• Monitor participation rates by activity type
• Analyze which activities drive desired outcomes
• Identify underutilized activities requiring promotion or redesign
• Adjust configurations based on data and user feedback

Jump to Reward Module Checklist

<< Managing Reward Claims | User Guide: Claiming Rewards >>