Is FCM Token Linked to Device or User Account: Implications for Notification Targeting?

FCM Token Management: Device-Specific or Account-Related?

When storing Firebase Cloud Messaging (FCM) tokens in a database for targeted notifications, it's crucial to understand the token's scope. The question arises: Is the FCM token associated with a specific device or with the user account?

Answer:

The Instance ID token used in FCM messaging represents the app instance on a particular device. Changes in the logged-in user do not alter the token representing the app instance. Uninstalling and reinstalling the app, however, triggers the creation of a new token.

Database Management Considerations:

To handle the scenario where the app user logs out and registers a new account on the same device:

• Logout: Remove the token mapping to the current logged-out user.
• Login: Create a new mapping for the same token to the newly logged-in user.

Token Consistency:

Even with multiple user accounts on the same device, the FCM token for the app remains consistent. This ensures that notifications are delivered to the correct user, regardless of their account status.

Therefore, to provide a seamless notification experience, it's essential to manage the FCM token mapping in the database based on the login and logout events, effectively tracking the user's device and ensuring that notifications are delivered to the appropriate user.

The above is the detailed content of Is FCM Token Linked to Device or User Account: Implications for Notification Targeting?. For more information, please follow other related articles on the PHP Chinese website!