Tags let you organise content — challenges, rewards, achievements, posts — into groups for filtering, campaigns, and analytics.
Settings -> Tags -> Create Tag (#999). Each tag has:
- Name — human-readable (#1950), shown in tables and member UI.
- Slug — auto-derived from the name.
- Colour — for visual grouping.
- Scope — community-specific or org-wide.
Every content editor (challenges, rewards, achievements, posts) has a Tags field in the Basic Info step. Multi-select from existing tags, or type to create new.
Tag UI parity
Rewards previously had a separate ad-hoc tag system; #959 unified rewards with achievements / challenges / posts so they share the same tag picker and behaviour.
Filtering by tag
Every list view (challenges, rewards, etc.) supports filtering by one or more tags. Useful for:
- Running a campaign: tag all campaign-related content with
campaign-name.
- Reporting: filter analytics by audience tag (
audience-b2b, audience-consumer).
- Content audits: find all tagged-as-legacy items to archive.
Human-readable names
Tables show the tag’s human-readable name (#1950) rather than raw slugs. This is a small UX win that adds up on large content libraries.
Best practices
Stick to a small taxonomy (10-20 tags). Tag sprawl (100+ tags, each used once) makes filtering useless.
Use tag conventions: prefix audience tags with audience-, campaign tags with campaign-, content-type tags with type-. Consistency pays off at scale.
