# Does a Profile Completion Meter Fill Empty Fields?

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/does-a-profile-completion-meter-fill-empty-fields

## Hypothesis

If a percentage showing how much of the profile is filled in makes the missing fields visible after sign-up, users may come back and complete them. Among eligible users with incomplete profiles, the profile completion rate for the predefined field set could rise as a result.

## When to run this test

Optional profile fields that stay blank long after sign-up, together with session recordings of users who never open the profile page, hint that users simply do not notice what is missing. If the indicator works, users who see it return to the missing fields and fewer users add nothing at all. If users leave fields empty on purpose, find out why with a survey first, and keep email and push reminders unchanged during the test.

## Primary metric

**Profile completion rate**: Compare completion of the predefined optional field set among eligible users with incomplete profiles.

## Other metrics

- **Return rate**: Compare subsequent app visits over the same period in both arms.
- **Completed fields per user**: Count valid field entries per assigned user, including those who add none.
- **Progress indicator dismissal rate**: Use dismissal as a diagnostic in the variant; dismissal alone does not prove annoyance.
- **Overall session time**: Compare all assigned users; those who dismiss the indicator are a selected subgroup.

## What to check before and during the test

- **Indicator**: Add one predefined percentage indicator without changing profile fields.
- **Calculation**: Use the same accurate completion rule throughout the test.
- **Placement**: Choose one fixed location before launch.
- **Timing**: Set one eligibility and display trigger; first-session versus later display is a separate test.
- **Format**: Keep the visual format fixed; field count, circle versus bar are separate comparisons.

## What to watch when reading the result

- Read a lift in profile completion rate alongside completed fields per user and return rate. If the lift comes from making an optional or sensitive field required, it is no reason to ship; those fields must stay optional throughout the test.
- The finding is limited to this indicator format, placement and trigger; circle versus bar, or showing it in the first session, are separate comparisons. Confirm users can dismiss the indicator and choose “Later,” read the dismissal rate within the variant only, and compare session time across all assigned users.
- Completing a profile can take time, so measure returns in both arms over an identical window. Once the follow-up period ends, check whether the gap could be chance with the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test), and do not stop the test early after peeking.

## Frequently Asked Questions

### Which outcome matters besides complete profiles?

Count valid fields added per assigned user, including users who add none. Use valid profile completion as the primary outcome. Partial progress and return visits are supporting measures.

### How should the profile-completion percentage be calculated?

Fix eligible fields and the completion rule beforehand. Do not round an unfinished profile to 100%. Exclude sensitive and optional fields from the completion pressure rather than making them required.

### Does dismissing the indicator prove annoyance?

No. Treat dismissal as a variant-only diagnostic. Compare session behavior across assigned users, not selected dismissers, and preserve an option to finish later.