To begin with, you have to differentiate and define opt-out users and app uninstalls:

You can track your opt-out users in the Analytics → Reach tab.

Batch can only have information about what's going on in the app. When a user installs and opens the app, we receive a push token from Apple/Google that allows us to communicate with them.

If the user opt-outs from notifications in the device settings, no information is provided to Batch servers. The actual opt-in status will be updated only when the user opens the app again. Likewise, we do not know in real time when an opt-out user activates push notifications again.

Therefore the Batch database is potentially always "out of synchronization" with reality regarding the opt-in status.

Batch always targets all opt-in and opt-out tokens: it allows us to update the state of the tokens, clean the database and recover the users who would have reactivated the notifications. The notification will never be displayed to an actual opt-out user, it will be blocked by the device.

On Android, users opt-in to push notifications by default. The number of opt-out users corresponds to the users who have:

There are two pages where you can track your app uninstalls:

In this example, we report that 80 users, who were targeted by the push, did not receive it because they uninstalled the application. Uninstalls concern both opt-in and opt-out users, as long as they were targeted by the campaign.

Unlike opt-outs, we receive by return loop the uninstalls that took place between the sending of the last campaign and the campaign of the day. This loop occurs only once a campaign has been sent. That's why you will see uninstalls only on days when a push has effectively been sent.

Note: Sending a test push notification won't trigger the uninstalls detection.