Understanding Device and User Identifiers in Pushwoosh

Pushwoosh utilizes several types of identifiers to manage devices and users effectively. This guide explains each type and how you can obtain them.

Device IDs

Push Token

The Push Token is a unique, randomly generated identifier issued by a push notification gateway, such as Google's Firebase Cloud Messaging (FCM) or Apple Push Notification service (APNs).

Assignment: It is assigned to your application when a registerDevice request is made.
Changes: This token changes if the application is reinstalled or its data is cleared on a device.
Importance: Push tokens are essential for sending notifications, as the gateway uses them to recognize and address specific devices. Without a valid push token, notifications cannot be delivered.

Related articles: Push token, registerDevice.

HWID (Hardware ID)

The HWID is a unique, randomly generated identifier assigned to a device by the Pushwoosh SDK during its initial setup.

Uniqueness: Each device is assigned its own distinct HWID.
Data Association: All device-related data, including tags and events, are linked to this HWID.
Internal Use: The HWID serves as the primary internal identifier within Pushwoosh.

User ID

The User ID is an optional identifier that you can assign to a specific user.

Purpose: It allows you to maintain consistent user data across all of a user's devices. Alternatively, you can use it to link devices with your CRM identifiers for easier management.
Default Behavior: By default, the User ID is the same as the device's HWID.
Customization: You can override the default User ID by using the setUserId call within your application.

Related articles: Users (UserIDs), setUserId.

How to Obtain Device and User IDs

You can retrieve these identifiers through several methods:

Exported Segment CSV File: Obtain IDs from a CSV file generated by exporting a segment. For more details, refer to the Segments guide.
API Request: Use the /exportSegment API request to get IDs in .csv or .json format.
Physical Device Logs: You can directly find these identifiers in the logs of a physical device. More specific information on this process can be found in the article: How to obtain console logs and device token.
User Explorer: The Pushwoosh User Explorer allows you to view a device and all its associated data, including IDs, assigned tags, triggered events, and received notifications.

For additional information on device identifiers, please refer to the Device identifiers article.

Notification IDs

When working with notifications in Pushwoosh, you'll encounter two primary identifiers: Message ID and Message Code. These are crucial for tracking and managing your sent notifications.

Message ID

The Message ID is a unique numerical identifier assigned to each individual notification.

Format: It is a unique notification number, such as "12345678900".
Location: You can find the Message ID within the "Message details" section of each notification in your Pushwoosh account.

Message Code

The Message Code is a unique identifier assigned to all notifications sent as part of a particular message.

Purpose: It is particularly useful for identifying a specific notification within various API responses. For example, you can use the Message Code to pinpoint a notification in the getMessageLog response.
Location: The Message Code is also provided in the API response of a createMessage request.

{
"status_code": 200,
"status_message": "OK",
"response": {
    "Messages": ["CCEB-AD40FC71-82DB37B9"]
    }
}