Expo push tokens explained.
Expo push tokens represent app installs, not users. They can rotate and expire, which means you need a plan for storing, updating, and cleaning them over time.
Token lifecycle
- App registers and requests permissions.
- Expo returns a push token for the install.
- Token is stored server-side and mapped to a user or device.
- Token rotates or expires; you update or remove it.
Always assume tokens can change. Build your system to update and clean them continuously.
Token hygiene checklist
- Map tokens to users and devices with clear ownership.
- Deduplicate tokens to avoid double sends.
- Remove tokens that fail permanently.
- Respect permissions and device settings.
How PushWave handles tokens
PushWave stores and deduplicates tokens, segments audiences, and tracks delivery. You do not need to build custom cleanup jobs or tracking tables.
FAQ
Are Expo push tokens stable?
No. Tokens can rotate, expire, or become invalid after reinstalls or permission changes.
Can I use a push token as a user ID?
No. Tokens identify app installs, not users. Always map tokens to users in your own data model.
How should I store Expo push tokens?
Store them server-side with a user or device reference, and be ready to update or delete them.
How do I clean up invalid tokens?
Listen to delivery receipts and remove tokens that fail permanently.
How does PushWave manage tokens?
PushWave stores tokens, deduplicates them, and helps you target segments without custom cleanup jobs.