Ali Demirbaş - Lab
TRGet in touch

UI Elements

Notification Badge: Number or Dot A/B Test Example

A count communicates how many items need attention.

  • UI elements
  • Visit rate for the indicated section

Option A vs Option B

Two alternatives; neither is the incumbent.

Changed
Options
Page
UI elements
Difference
changed

Hypothesis

A dot signals something new without giving a quantity. A count may clarify the task or make it feel larger; compare both displays for the same real pending items and use the same clearing rule.

How to run this test

Primary metric

Visit rate for the indicated section

Compare visits to the section indicated by the badge among eligible assigned users.

Other metrics

  • Action completion rateCompare completion of the predefined task in the indicated section.
  • Badge interaction rateReport visits to the indicated section; a visit alone does not prove the task was completed.
  • App or site exit rateCompare exits within the same session window.

What to check before and during the test

  • FormatCompare a numeric badge with a dot for the same pending state.
  • Count rangesReview predefined ranges based on actual pending-item counts.
  • ClearingKeep the same read or clear behavior.
  • PlacementKeep the same control and position.
  • DeviceCheck readability and discoverability on mobile.

Setup mistakes to avoid

  1. 1Do not show a badge unless there is a real notification or pending task.
  2. 2Change badge format only, not its position.
  3. 3Allow users to clear or dismiss the badge appropriately.
  4. 4Do not rely on red color alone to communicate the badge.
  5. 5Do not choose a winner from clicks alone; check task completion.