Badges

Badges turn raw scores into meaningful labels — automatically classifying users as "Trusted", "Suspicious", "Bot", or whatever categories fit your business. They are the human-readable layer on top of numerical scores, and the foundation for automated decision-making.

What Are Badges

A badge is an automatic label applied to an identity when its scores match conditions you define. Where scores are continuous numbers that require interpretation, badges are discrete classifications that are immediately actionable.

Think of badges as the conclusions your team would draw from looking at the scores, codified into rules that apply themselves. Instead of a team member looking at a Humanity score of 12 and thinking "that's a bot," the "Bot" badge does that classification automatically, consistently, and instantly.

Badge Types

Every badge has a type that indicates whether it represents a positive, negative, or neutral classification:

• Good — positive classifications that indicate trustworthy behavior. Examples: "Verified", "Trusted", "Power User". Good badges signal that an identity has passed your quality bar and may deserve elevated privileges or reduced friction.
• Bad — negative classifications that indicate risk or abuse. Examples: "Suspicious", "Bot", "Freeloader", "Multi-Account". Bad badges flag identities that warrant restrictions, manual review, or automated action.
• Neutral — informational classifications that provide context without judgment. Examples: "New User", "High Volume", "International". Neutral badges help you segment and understand your user base without implying risk.

Badge types are displayed visually in the dashboard — color-coded so your team can spot patterns at a glance without reading every label.

Badge Rules

Badge rules define the conditions under which a badge is assigned to or removed from an identity. You create rules in the dashboard under Settings, and each rule maps a set of conditions to a specific badge.

Score Conditions

The most common condition: assign a badge when one or more scores fall within a range.

• All four scores above 80 — assign "Trusted"
• Humanity below 25 — assign "Bot"
• Uniqueness between 20 and 50 — assign "Suspicious"
• Behavior below 30 AND identity older than 7 days — assign "Anomalous" (enough data to be confident)

Score ranges let you create precise classifications. A Humanity score of 45 might not warrant a "Bot" badge, but it could trigger a "Possibly Automated" badge that puts the identity on a watchlist without taking drastic action.

Identity Age

Restrict badge rules based on how long the identity has existed. This is useful for time-bounded classifications like "New User" (first 48 hours) or for ensuring you only badge identities once enough data has accumulated for a confident assessment.

Combining Conditions

Rules can combine multiple conditions. All conditions in a rule must be true for the badge to apply. This lets you create highly specific classifications:

• Humanity above 90 AND Authenticity above 85 AND Uniqueness above 80 AND identity older than 7 days — "Verified" (high confidence across the board, with enough history to be sure)
• Uniqueness below 40 AND Authenticity below 50 — "Freeloader" (low uniqueness combined with disposable data strongly suggests trial abuse)

Badge Delays

Scores fluctuate. A user's Behavior score might dip to 45 for an hour, then recover to 72 as more events arrive. Without safeguards, badges would flicker on and off with every minor score change, creating noise and unreliable classifications.

Dregs prevents this with configurable delays on both applying and removing badges:

• Apply delay — how long the conditions must be continuously met before the badge is assigned. A 1-hour apply delay means the scores need to stay in the triggering range for a full hour before the badge appears.
• Remove delay — how long the conditions must be continuously unmet before the badge is removed. A 24-hour remove delay means that even if scores briefly recover, the badge stays for at least a day.

Hysteresis turns badges from volatile labels into stable, reliable classifications. Once a badge is applied, it means that the conditions were sustained, not momentary.

Badges and Alerts

Badges and alerts are designed to work together. Alert rules can use badge presence or absence as trigger conditions. This creates a powerful layered system:

1. Scores update continuously as events arrive
2. Badge rules evaluate those scores and apply stable labels
3. Alert rules trigger based on those badges and notify your team or systems

This chain — score triggers badge, badge triggers alert, alert sends notification — gives you the best of both worlds. Badges absorb the volatility of raw scores, and alerts act on the settled classifications. The result is fewer false alarms and more actionable notifications.

For example: instead of alerting when Uniqueness drops below 40 (which might flicker), create a "Multi-Account" badge with a 2-hour apply delay, then alert when the badge appears. By the time the alert fires, you know the condition has been sustained.

Use Cases

Free Trial Abuse

You might create a "Freeloader" badge that applies when Uniqueness is below 40. Set a remove delay of 7 days so the badge persists even if the user deletes their duplicate account. Pair with a Warning-level alert to notify your team for manual review, or a webhook alert to automatically restrict the account in your application.

VIP Users

You might create a "Trusted" badge that applies when all four scores are above 80, with a 7-day apply delay. This identifies your most legitimate, long-term users. Use this badge to reduce friction — skip CAPTCHA, auto-approve actions, or offer premium features.

Suspicious Signups

You might create a "Suspicious" badge for identities less than 48 hours old with Authenticity below 45. This catches disposable emails, fake names, and inconsistent data at signup. Route these identities to a manual review queue before they can cause damage.

Bot Flagging

You might create a "Bot" badge when Humanity is below 20, with a short apply delay and a long remove delay. Bots are usually obvious within minutes, but you want the label to stick for investigation. Pair with a Critical alert for immediate team notification.

Viewing Badges

Badges appear directly on identity cards in the dashboard, giving your team instant visual context when reviewing a user. You can also filter identities by badge in the search bar by typing a badge name to see all identities carrying that classification.

The combination of badges and the search bar makes it easy to answer questions like "show me all users flagged as Suspicious this week" or "how many identities currently have the Trusted badge."