⚡
claimr
  • Getting started
    • Create an account
    • Sign in to your account
    • Reset password
    • Edit profile
  • ⚡️claimr core components
  • Team roles and management
  • Campaigns
    • Create new campaign
    • Campaign settings
  • Groups
    • Create new group
    • Group settings
  • Quests
    • Create new quest
    • Quest settings
  • Tasks
    • Create new task
    • Task settings
    • Telegram tasks
    • X (Twitter) tasks
    • TikTok tasks
    • Discord tasks
    • YouTube tasks
    • Web3 tasks
      • Connect a wallet
      • Transactions count
      • Wallet balance
      • Token balance
      • NFT balance
      • Link3 balance
      • Mint an NFT (721)
      • Mint an NFT (1155)
      • Verify transactions
    • PoW tasks
    • HTTP request tasks
    • Referral tasks
    • Form tasks
    • Poll tasks
    • Events tasks
    • API tasks
  • Widget
    • Publish campaign
    • Widget configurations
    • Widget attributes
    • Integrate claimr widget into your website
    • claimr widget integrations
      • Google Analytics integration
      • Google Analytics Client ID
      • Google Tag Manager integration
      • HotJar integration
  • Rewards
    • Reward settings
    • Custom rewards
  • Events
    • Daily check-ins
    • Challenges
    • Ranks
    • KOLs
  • Codes
    • Secret codes
    • Invite codes
      • Enter invite code task
      • Claim invite code task
    • Gift codes
  • Test users
  • Pop-ups
    • Into pop-up
    • Completion pop-up
  • API
    • API token
    • API methods
    • User token
  • Webhooks
    • Set up webhooks
    • Assign webhooks
    • Webhook scopes
  • SDK
  • Forms
    • Create forms
    • Form settings
    • Pages
    • Blocks
    • Quizzes
  • Data analytics
    • Activity
    • PoW analytics
    • User information
    • Failed actions
    • Issues analytics
  • How to
    • Create X campaign
    • Create Discord campaign
    • Integrate claimr widget into dApp
    • Integrating claimr widget into Telegram mini app
    • Customize user experience with tags and attributes
    • Add custom points to users
  • UX requirements
    • Campaign UX requirements
    • Group UX requirements
    • Quest card UX requirements
    • Quest UX requirements
    • Task UX requirements
    • User progress UX requirements
    • Pop-ups UX requirements
    • Interactive components UX requirements
Powered by GitBook
On this page
  • Understanding Campaigns
  • 1. User progress block
  • Username
  • User progress
  • Login/Logout button
  • 2. Highlighted quests
  • 3. Campaign description
  • 4. Challenges
  • 5. Group
  • Quest card
  • Tasks
  • State indicators
  • Pop-ups and notifications:
  • Close/View more buttons:
  • 6. Leaderboard

Was this helpful?

  1. UX requirements

Campaign UX requirements

This guide outlines the key design elements and considerations for building visually appealing and user-friendly ⚡️claimr campaigns.

PreviousUX requirementsNextGroup UX requirements

Last updated 1 month ago

Was this helpful?

Understanding Campaigns

A campaign in claimr is a structured set of activities and challenges designed to engage users and drive specific actions. It's a container with various elements, such as quests, tasks, rewards, and leaderboards, all working together to achieve your campaign goals.

1. User progress block

Username

Displays the username of the logged-in user. If the user is not logged in, it might show a generic placeholder or prompt the user to log in.

  • Clarity: Use a legible font and appropriate font size.

  • Placement: Position the username prominently at the top of the page.

  • Logged-out state: Clearly indicate that the user is not logged in and provide a clear path to log in or sign up.

User progress

Shows the user's progress within the campaign.

  • Visual clarity: Use clear labels and visual cues to represent progress.

  • Accessibility: Ensure the progress bar is accessible to screen readers.

Logged-in state: Display personalized information, such as the user's name, points, and a progress bar.

Logged-out state: Show a simplified progress bar or a call to action to log in.

For more information, read User progress UX requirements

Login/Logout button

Allows users to log in or out of their account.

  • Clear labeling: Use distinct labels or icons to indicate the logged-in or logged-out state.

  • Placement: Position the button near the user's name or progress information.

2. Highlighted quests

Prominently displayed quests to attract attention and encourage participation.

  • Visual prominence: Use design elements (e.g., size, color, animation) to highlight these quests.

  • Relevance: Ensure the highlighted quests are relevant and engaging to users.

3. Campaign description

Provides an overview of the campaign's goals, objectives, and rewards.

  • Clarity: Use clear and concise language.

  • Engagement: Write in a compelling and informative tone.

  • Visual appeal: Use formatting and visuals to enhance readability.

4. Challenges

Activities that encourage users to go above and beyond the standard quests in your campaign. They offer a way to boost engagement and provide unique opportunities for users to earn rewards or recognition.

  • Clear presentation: Clearly explain the challenge objectives and rewards.

  • Optional participation: Make it clear that these challenges are optional.

  • Flexibility: Allow for different naming conventions (Seasons, Eras, etc.).

5. Group

Organizes quests into logical groups, making it easier for users to navigate your campaign and understand the relationships between different quests. This helps provide context and structure to the user journey.

  • Grouping: Visually group related quests together.

  • State indicators: Clearly indicate whether the group is locked or unlocked.

  • Group Description: Provide a concise description of the quest group's theme or focus.

For more information, read Group UX requirements

Quest card

Represents an individual quest within a quest group.

  • Preview: Provide a preview of the quest's objectives and rewards.

  • State indicators: Clearly indicate whether the quest is active, locked, or completed.

For more information, read Quest card UX requirements

Tasks

Specific actions within a quest.

  • State indicators: Clearly communicate the task's status (active, locked, or completed).

  • Task header: Provide a concise and informative title.

  • Task description: Offer clear instructions.

  • Call to action: Include a clear CTA button.

For more information, read Task UX requirements

State indicators

These visual cues help users quickly understand the overall status of campaigns, quests, tasks: Active, Completed, or Locked.

  • Visual clarity: Use distinct colors, icons, timers or labels to differentiate between the states.

  • Accessibility: Ensure the indicators are easily distinguishable for users with visual impairments, utilizing sufficient contrast and screen-reader-friendly descriptions.

Pop-ups and notifications:

Provide feedback and information to users.

  • Visual appeal: Use subtle animations, icons, or colors.

  • Accessibility: Ensure notifications are accessible to screen readers.

  • Clear close option: Provide a prominent close button.

  • Mobile optimization: Ensure pop-ups display correctly on smaller screens.

For more information, read Pop-ups UX requirements

Close/View more buttons:

Allow users to close or expand certain sections or elements within the campaign.

  • Clear labeling: Use clear and concise labels (e.g., "Close," "View More").

  • Placement: Position buttons logically based on the content they control.

For more information, read Interactive components UX requirements

6. Leaderboard

The leaderboard displays a ranked list of users based on points or performance metrics. It helps foster engagement by highlighting top contributors or achievers.

States and behaviors to design for:

  • Default view: Displays the full leaderboard with all ranked users visible.

  • Collapsed leaderboard state: Only the heading row and the top 9 ranked users are shown when the list is long. Include View more / Hide buttons to expand or collapse the list.

  • Leaderboard pop-up: Design the button for flows when the leaderboard appears only after clicking it.

  • Collapse button in pop-up: When opened in a modal, include an option to collapse or minimize the leaderboard view.

  • Pagination: If the full list is too long to load at once, add pagination to allow users to browse through pages of results.

  • Clear rankings: Present user rankings and relevant metrics clearly.

  • Visual hierarchy: Use size, color, and placement to highlight top performers.

Example: Campaign stucture
Example: User progress
Example: Highlighted quests and user progress
Example: Challenges
Example: Group of quests
Example: Group of quests
Example: Follow X task
Example: Invite code task
Example: Locked campaign state
Example: Completed campaign state
Example: Different quest states
Example: Submit email pop-up
Example: Leaderboard
Pagination