Testers Installed but Not Counted

Introduction

A common frustration during closed testing is seeing testers confirm they installed the app, while Play Console shows fewer active installs than expected. This situation usually means you’re dealing with a testers installed but not counted issue, where the installation happened in a way Google does not recognize. From the tester’s perspective, the app works fine. From Google’s perspective, the install may not exist at all.

In this article, we’ll explain why this happens and how to fix the issue so installs are counted correctly.

Quick Answer / TL;DR

Testers are not counted when:

The app is installed via APK or sideloaded
Installation happens before opt-in
A different Google account is used
The Play Store install is incomplete

To fix this, testers must opt in first and complete a Play Store installation using the same Google account.

What Google Means by “Installed but Not Counted”

This issue does not mean Play Console is broken.

Google checks one thing: “Was this app installed from the Play Store after opt-in using the same Google account?”

Only installs that meet all requirements appear as Play Console active installs. Anything outside this process is ignored, which leads to a tester install not counted situation. This is why developers often see Google Play installs not showing even when testers insist they installed the app.

Common Reasons This Issue Happens

1. App Was Installed via APK or Sideloaded

This is the most frequent cause of a closed testing install issue.

An APK install not counted because:

It bypasses the Play Store
It doesn’t trigger testing metrics
Google cannot verify tester participation

Even if the app works perfectly, APK installs are invisible to closed testing.

2. Tester Installed Before Opting In

Some testers install the app first and opt in later. Google only tracks installs that happen after opt-in. Any earlier install must be removed and redone.

3. Tester Used a Different Google Account

If a tester:

Opts in with one account
Installs using another account

Google treats the install as invalid, resulting in a Google Play testing install mismatch.

4. Play Store Installation Was Interrupted

If the install:

Was cancelled
Failed silently
Never fully completed

Google may not record it as a valid install.

How to Fix “Testers Installed but Not Counted” (Step by Step)

Step 1: Confirm Opt-In Was Completed First

Ask testers to confirm they opted in before installing the app.

Step 2: Reinstall the App Correctly

Have testers:

Uninstall the app
Open the official Play Store testing link
Install again from the Play Store
Open the app at least once

This fixes most testers installed but not counted cases.

Step 3: Verify the Correct Google Account

Ask testers to:

Check the active Google account in Play Store
Use the same account they opted in with

Step 4: Avoid APK Distribution Entirely

Do not share APK files during closed testing. They always lead to APK install not counted problems.

Avoiding This Issue in the Future

Most install-count issues happen because testers are unclear about the correct process. Developers who provide clear, step-by-step instructions rarely face repeated tester install not counted problems. If managing installs manually becomes difficult, many teams use guided testing services like 12testers14days.com to ensure testers opt in and install correctly every time.

Using reliable testers also reduces delays caused by incorrect installs and helps closed testing move forward smoothly.

Tools & Official Resources

Frequently Asked Questions

Do APK installs ever count for closed testing?

No. APK or sideloaded installs are never counted.

Does reinstalling fix the issue?

Yes, if the tester opts in first and installs from the Play Store using the correct account.

Conclusion

When testers are installed but not counted, the problem is almost always how the install was done, not whether it happened. Once testers follow the correct opt-in and Play Store installation process, installs appear properly and closed testing can continue without delays.