A push token is an anonymous ID generated by Apple (iOS) or Google (Android) for your installation. Batch's SDK collects automatically that token each time you open the app and sends it to our servers. If your users were offline the first time they opened your app, Batch will collect the token the next time they open it with a working Internet connection.
Each time you schedule a push campaign from the dashboard, Batch will:
Select the installs matching your campaign targeting;
Find the tokens attached to these installs;
Send the list of targeted tokens to Apple/Google with the message you want to deliver to these users.
Apple and Google automatically invalidate push tokens when users uninstall the app. They will generate a new token if the same users reinstall the app later.
Batch automatically takes care of updating/cleaning your users’ tokens so you can just focus on the wording of your next push campaign. Please note we do not receive that kind of feedback in real time. We receive information on the validity of your users' tokens each time you try to send them a push notification.
🚧 Note on token invalidation:
Please note that test push notifications do not trigger a token invalidation by Apple or Google even if the device is no longer reachable, only push campaigns in production will trigger a token invalidation by Apple or Google if the device is no longer reachable. The response time from Apple or Google is very variable, the push token can be considered valid by Apple for several days or even weeks in some cases.
🚧 Note for web push:
Web push notifications work in a similar way. The token is provided by the push service of each browser (e.g. Google for Chrome, Mozilla for Firefox, etc). We also receive feedback on the validity of the token each time we try to push it.
This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on batch.com and our blog.