Build segments by User ID

Use the User ID filter to create a segment of known users by their Pushwoosh User ID, or switch it to HWID, Email, Phone, or Token to match by that device identifier instead. This works best when you already know which users or devices you want to include and those identifiers are registered in your project.

How to build a segment by User ID

To create a User ID-based segment:

1. Go to Audience → Segments.

2. Click Create Segment to open the segment builder.

3. In the segment builder, click User ID in Add filter by.

4. Choose which identifier to filter by: User ID, HWID, Email, Phone, or Token.

5. Choose the operator for the condition. Learn more

6. Add the values that should be included in the segment: User IDs, HWIDs, emails, phone numbers, or push tokens, depending on the field you chose in step 4. in and not in take a list of values. starts with, contains, and ends with take a single value. Enter phone numbers in E.164 format, for example +15551234567. Pushwoosh stores them this way, and starts with only matches from the very first character.

Note

Use identifiers that already exist in your Pushwoosh project. If you need to upload a file with User IDs or Hardware IDs, use Import a segment.

7. Add more filters if needed.

8. To target a user across all their devices when the condition matches, use Include all of a user’s devices. Learn how this option works.

9. Click Save.

Tip

You can combine User ID with Tag, Event, Segment, or Geo filters in the same segment to narrow a known user list by behavior, attributes, existing segment membership, or location. For more complex logic, see Build segments with compound filters.

Operators

Each field takes the same five operators, comparing the values you enter against that field’s value on each user or device.

Operator	Description	Example
in	Matches any value in the list	UserID in ["user1", "user2"]
not in	Does not match any value in the list	HWID not in ["a1b2c3d4e5"]
starts with	Begins with the specified string	Phone starts with "+1555"
contains	Contains the specified string	Email contains "example.com"
ends with	Ends with the specified string	Token ends with "9a2e2f"

Multi-device matching

For HWID, Email, Phone, and Token, operators evaluate each device individually. A user matches if any one of their devices satisfies the condition.

not in matches any user with at least one device whose value is not in the list. If a user has several devices, one device outside the list is enough to match, even if another device of that user is on the list.

Turning on Include all of a user’s devices adds every device of a matching user to the segment, including devices whose values are on the excluded list.

Token matching

Token matches the push token shown for a device in User Explorer. It doesn’t match Firebase Cloud Messaging (FCM) sender keys or web push keys, which aren’t indexed for this filter.

Unlike Email, Token values are case-sensitive. Pushwoosh compares them exactly as entered, without lowercasing.

Note

Pushwoosh compares Email values in lowercase, so casing in what you type doesn’t matter. New email devices are stored in lowercase, but a small share of existing devices still have their address stored with uppercase letters. This filter can’t match those regardless of how you enter the value.

Legacy segments

Segments saved before these operators were introduced carry no operator value and are read as in. Nothing changes for existing segments.