There are three types of device/user IDs we are using in Pushwoosh:
- Push token — a unique random generated token issued by a push gateway (FCM by Google, APNs by Apple, etc.). This type of ID is assigned to the application (on registerDevice request) and changes every time of application is re-installed or cleared the application's Data on an Android device. Without push tokens, notification can't be sent to devices, 'cause the gateway won't recognize the device.
- HWID (hardware ID) — a unique random generated ID assigned to the device by Pushwoosh SDK on the first SDK initialization. Each device has its own HWID. All device data like tags or events will assign to the HWID. This is the main ID we use internally.
- User ID — an identifier you may assign to a specific user to keep user data consistent across all user's devices. Another way to use is assigning your unique ID to operate devices by your CRM identifiers if it's more convenient to you. By default, the UserID equal to the HWID of the device, but you can overwrite it with setUserId call in your app.
You can get all these IDs in three ways:
- From CSV file of exported segment. See this guide: Segments.
- From .csv or .json file of /exportSegment API request.
- From a physical device logs directly. You may find more specific information on this matter in the following article: How to obtain console logs and device token.
Check this article for more info on Device identifiers.
Moreover, you may found the device and all of its known data like its IDs, tags assigned, events triggered, notification received and even more in your User Explorer.
To identify the notification, we use two types of IDs:
Notification ID — a unique notification number like "12345678900". Could be found in your Statistics → Message History entry. Just open a notification there and check its Push Statistics.
Alternatively, the Notification ID could be found in the page link like "https://app.pushwoosh.com/applications/XXXXX-XXXXXX/messaging-statistics/notifications/statistics/12345678900"
Please note that for load balancing purposes, we do not store messages sent through API with the "devices"/"users" parameter [ref] that contains less than 10 IDs in an array. Due to this, such messages will not be displayed in your Message History as the result, they will not be received the Notification ID. You may temporarily overwrite it for debug purpose, please check this note.
The same applies for the Customer Journey push notifications.
Message Code — a unique message code assign to all notifications sent. Could be useful to identify a notification in some API responses, for example, in the getMessageLog response.
Could be found in the Notification (Push) Details in the Push Statistics.
Or in the API response: