How To Create and Use Viewer Counters

User Counters track a separate saved number for each viewer and platform. Use them for check-ins, hydrates, wins, scares, or other community activities.

Create a Counter Category

  1. Open Bot Commands → Data Manager → User Counters.
  2. Click New category.
  3. Enter a descriptive name such as Check In or Times Scared.
  4. Click Create category.

Category names are used by actions and variables, so avoid renaming one after building workflows around it.

Add or Edit a Viewer

  1. Select a category.
  2. Click Add user.
  3. Choose Twitch, YouTube, Kick, or TikTok.
  4. Enter the username and starting value.
  5. Save the entry.

Select an existing viewer to add or subtract from their value, set an exact value, and record an optional reason. Recent history shows changes and who or what made them.

Deleting a viewer removes that row and its history. Deleting a category removes every viewer and history record inside it and cannot be undone.

Update Counters with Action Builder

User Counter actions are available in Automations and Timers:

  • Increment user counter: adds or subtracts an amount.
  • Set user counter: replaces the current value.
  • Reset user counter: sets the value to zero.
  1. Select Chat Bot Commands in Action Builder.
  2. Choose the User Counter action and click Add action.
  3. Select the counter category from the dropdown.
  4. Enter a username or supported variable such as {user}.
  5. Enter the amount or value when requested.
  6. Choose the correct platform, then save and test.

For event-based Automations, {user} normally targets the viewer who caused the event. Timers do not have a triggering viewer, so provide a username or another available variable. If a new category is missing from the dropdown, close and reopen the action editor.

Show a Counter in Messages

Use these variables in supported response fields:

{usercounter:Check In}
{target.usercounter:Check In}

{usercounter:Category} reads the command sender's value. {target.usercounter:Category} reads the targeted viewer's value. Replace Check In with the exact category name.

Example custom-command response:

@{user}, you have checked in {usercounter:Check In} times!

Common Problems

  • Value stays at zero: Check the selected category, username, and platform.
  • Wrong viewer changes: Use {user} for the trigger viewer and {target} only when a target is supplied.
  • Timer action fails: Enter a viewer because Timers do not normally provide {user}.
  • History is missing: Manual or action changes appear after the viewer entry exists and a value changes.