# Notification Badge: Number or Dot A/B Test Example

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/notification-badge-number-or-dot-ab-test-example

## Hypothesis

If the badge shows the number of pending items, users see how much is waiting and may open the section with a clear purpose; a plain dot only says something is new. A count could bring a higher visit rate for the indicated section than the dot when it clarifies the work, or fall behind it when it makes the work feel larger.

## When to run this test

Low section visits while the badge is showing, user research where people ask what the badge means, or support tickets about pending items that went unnoticed mean the notification badge is either missed or misunderstood. If the count clarifies the work, users who see it enter the section and complete the pending task; if it makes the work feel larger, visits run higher with the dot. Before launch, confirm the badge appears only for real pending items and that users can clear it by reading or dismissing them.

## 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 rate**: Compare completion of the predefined task in the indicated section.
- **Badge interaction rate**: Report visits to the indicated section; a visit alone does not prove the task was completed.
- **App or site exit rate**: Compare exits within the same session window.

## What to check before and during the test

- **Format**: Compare a numeric badge with a dot for the same pending state.
- **Count ranges**: Review predefined ranges based on actual pending-item counts.
- **Clearing**: Keep the same read or clear behavior.
- **Placement**: Keep the same control and position.
- **Device**: Check readability and discoverability on mobile.

## What to watch when reading the result

- Do not call either format a winner just because the visit rate or the badge interaction rate is higher; tapping a badge does not mean the task got done. Check whether the difference carries through to the action completion rate in the indicated section, and confirm the app or site exit rate does not rise.
- Read the result separately for the predefined ranges of real pending counts, since a few items and many items may draw different reactions. Check that both formats can be noticed without relying on red color alone, and review readability on mobile screens. Do not carry the result over to badges on other controls or positions without testing them there.
- Once you split the result by count range, each range on its own is a small group, so differences there can easily stay unclear. Set the number of users per arm that each range needs before launch with the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator).

## Frequently Asked Questions

### Does more section traffic mean the numbered badge won?

No. Use completion of the predefined action in the destination section. Badge interaction alone does not establish task completion.

### Can the pending-item count affect the result?

Yes. A number may clarify the work or make it seem larger. Review predefined ranges of real pending counts and compare exits over the same session window.

### Which badge-design mistakes should be avoided?

Do not invent pending work. Avoid relying only on red, provide a way to clear the badge and check mobile readability and discoverability.