Allows you to filter based on whether your users have opted-in to ad tracking. Ad tracking relates to the IDFA or "identifier for advertisers" assigned to all iOS devices by Apple, which can be set by SDKs. This identifier allows advertisers to track users and serve them targeted ads.
Segmentation Filters
The Braze SDK provides you with a powerful arsenal of filters to segment and target your users based off of specific features and attributes. You can search or narrow these filters by filter category.
To learn about the different custom attribute data types you can use to segment users, view Custom attribute data types.
Segments your users by their birthday, as they indicated from within your app.
Users with a birthday on the 29th of February will be included in segments including March 1.
To target December or January birthdays, only insert filter logic within the 12-month span of the year you're targeting. In other words, do not insert logic that looks back to the previous calendar year's December or forward to the next year's January. For example, to target December birthdays, you can filter for "on December 31", "before December 31", or "after November 30".
Clicked Alias in Any Campaign or Canvas Step
Filter your users by whether they clicked a specific alias in any campaign or Canvas. This only applies to email messages.
If multiple users share the same email address:
- When the email is opened or clicked, all other users with that same email address also have their profiles updated.
- If the original user changes their email address after the message is sent and before the open or click, the open or click gets applied to all remaining users with that email address instead of the original user.
Filter your users by whether they clicked a specific alias in a specific campaign. This only applies to email messages.
If multiple users share the same email address:
- When the email is opened or clicked, all other users with that same email address also have their profiles updated.
- If the original user changes their email address after the message is sent and before the open or click, the open or click gets applied to all remaining users with that email address instead of the original user.
Filter your users by whether they clicked a specific alias in a specific Canvas. This only applies to email messages.
If multiple users share the same email address:
- When the email is opened or clicked, all other users with that same email address also have their profiles updated.
- If the original user changes their email address after the message is sent and before the open or click, the open or click gets applied to all remaining users with that email address instead of the original user.
Filter by interaction with a specific campaign.
For email, if multiple users share the same email address:
- When the email is opened or clicked, all other users with that same email address also have their profiles updated.
- If the original user changes their email address after the message is sent and before the open or click, the open or click gets applied to all remaining users with that email address instead of the original user.
For SMS, an interaction is defined as:
- The user last sent a reply SMS matching a given keyword category. This is attributed to the most recent campaign received by all users with this phone number. The campaign must have been received in the last four hours.
- The user last selected any shortened link in an SMS message that has user click tracking turned on, from a given campaign.
Clicked/Opened Campaign or Canvas With Tag
Filter by interaction with a specific campaign that has a specific tag.
If multiple users share the same email address:
- When the email is opened or clicked, all other users with that same email address also have their profiles updated.
- If the original user changes their email address after the message is sent and before the open or click, the open or click gets applied to all remaining users with that email address instead of the original user.
For SMS, an interaction is defined as:
- The user last sent a reply SMS matching a given keyword category. This is attributed to the most recent campaign received by all users with this phone number. The campaign must have been received in the last four hours.
- When the user last selected any shortened link in an SMS message that has user click tracking turned on, from a given campaign or Canvas step with tag.
Filter by interaction with a specific Canvas component.
For SMS, an interaction is defined as:
- The user last sent a reply SMS matching a given keyword category. This is attributed to the most recent campaign received by all users with this phone number. The campaign must have been received in the last four hours.
- The user last selected any shortened link in an SMS message that has user click tracking turned on, from a given Canvas step.
Segments your users by whether or not they have a valid email address, and if they are subscribed/opted-in to email. The email available filter checks for three criteria: if the user is unsubscribed from emails, if Braze has received a hard bounce, and if the email was marked as spam. If any of these criteria are met, or if an email doesn't doesn't exist for a user, the user will not be included.
Segments your users by whether or not they have entered a variation path of a specific Canvas. This filter evaluates all users.
For example, if you filter for users who have not entered a Canvas variation control group, you will receive all users who are not in the control group regardless if they entered the Canvas.
The segment of your users that have a particular feature flag currently enabled.
Segments by whether or not a user has ever installed your app. This will include users who currently have your app installed and those that have uninstalled in the past. This generally requires users to open the app (start a session) to be included in this filter. However, there are some exceptions, such as if a user was imported into Braze and manually associated with your app.
Segments your users by whether or not they were in the control group for a specific Canvas. This filter only evaluates users who have entered the Canvas.
For example, if you filter for users who are not in the control group for a Canvas, you will receive all users who entered the Canvas but are not in the control group.
Segments your users by the last time they have clicked or opened one of your messaging channels (Content Card, email, in-app, SMS, push, WhatsApp). Includes the option to filter by machine opens or other opens for email messages. (24-hour period)
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the user last selected any shortened link in a message that has user click tracking turned on.
Time zone:
Company's Time Zone
Segments your users by determining the last message that was received. (24-hour period)
For Content Cards and in-app messages, this is when a user last logged an impression, not when the card or in-app message was last sent.
For push and webhooks, this is when any message was sent to the user.
For WhatsApp, this is when the last message API request was sent to WhatsApp, not when the message was delivered to the user's device.
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device.
Example:
Last Received Message Less than 1 Day ago = less than 24 hours ago
Time zone:
Company's Time Zone
Segments your users by whether or not they have reported their locations. In order to use this filter, your app needs to have location tracking integrated.
Segments your users by the locale information from the most recently used device.
Attributes that are the properties of custom attributes.
When filtering a nested time custom attribute, you can choose to filter based on "Day of Year" or "Time". "Day of Year" will check only the month and day for comparison. "Time" will compare the full timestamp, including the year.
Segments your users who have provisional push authorization or are enabled for foreground push. Specifically, this count includes:
1. iOS users who are provisionally authorized for push.
2. Users who explicitly activated push notifications for any of the apps in your workspace. For these users, this count includes only foreground push.
Push Enabled does not include users who have unsubscribed.
After segmenting with this filter, you will be able to see a breakdown of who is in that segment for Android, iOS, and web in the bottom panel, called Reachable Users.
Segments your users by their subscription status for push.
Segments your users by which variant of a multivariate campaign they have received.
For Content Cards and in-app messages, this is when a user logs an impression, not when the card or in-app message is sent.
For push and webhooks, this is when the message is sent to the user.
For WhatsApp, this is when the last message API request is sent to WhatsApp, not when the message is delivered to the user's device.
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device.
Received Message from Campaign
Segments your users by whether or not they have received a specific campaign.
For Content Cards and in-app messages, this is when a user logs an impression, not when the card or in-app message is sent.
For push and webhooks, this is when the message is sent to the user.
For WhatsApp, this is when the last message API request is sent to WhatsApp, not when the message is delivered to the user's device.
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device.
Received Message from Campaign or Canvas with Tag
Segments your users by whether or not they have received a specific campaign or Canvas with a specific tag.
For Content Cards and in-app messages, this is when a user logs an impression, not when the card or in-app message is sent.
For push and webhooks, this is when the message is sent to the user.
For WhatsApp, this is when the last message API request is sent to WhatsApp, not when the message is delivered to the user's device.
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device.
Received Message from Canvas Step
Segments your users by whether or not they have received a specific Canvas component.
For Content Cards and in-app messages, this is when a user logs an impression, not when the card or in-app message is sent.
For push and webhooks, this is when the message is sent to the user.
For WhatsApp, this is when the last message API request is sent to WhatsApp, not when the message is delivered to the user's device.
For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). When multiple users share the same email address:
- On the initial send, only the specific targeted user's profile is updated.
- When the email is delivered, or if the user then opens the email or a link in the email, all users sharing that email address will appear to have received the message.
For SMS, this is when the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device.
Allows you to filter based on segment membership anywhere that filters are used (such as segments, campaigns, and others) and target multiple different segments within one campaign.
Note that segments already using this filter cannot be further included or nested into other segments. You must recreate the segment you're trying to include by using the same filters.
Segments your users by the e.164 sending phone number field.
When a phone number is sent to Braze, Braze tries to coerce it into the e.164 format that is used to send across SMS and WhatsApp channels. The coercion process can fail if the number isn't formatted properly, which results in the user profile having a phone number but not a sending phone number.
Use cases:
- Use regular expressions (regex) with this filter to segment by phone numbers with a specific country code.
- Use this filter to segment users by phone numbers that failed the e.164 coercion process.
Determines whether or not a user has performed a specially recorded event between 0 and 50 times in the last specified number of calendar days between 1 and 30. (Calendar Day = 1 calendar day will look at 24-48 hours of user history)
Learn more about X-in-Y behavior here.
Example:
Abandoned Cart exactly 0 times in the last 1 calendar day
Time zone:
UTC - To account for all time zones, 1 calendar day will look at 24-48 hours of user history, depending on the time the segment is evaluated; for 2 calendar days, will look at 48-72 hours of user history, and so on.
X Custom Event Property In Y Days
Determines whether or not a user has performed a specially recorded event in relation to a specific property between 0 and 50 times in the last specified number of calendar days between 1 and 30. (Calendar Day = 1 calendar day will look at 24-48 hours of user history)
Learn more about X-in-Y behavior here.
Example:
Added to Favorites w/ property "event_name" exactly 0 times in the last 1 calendar day
Time zone:
UTC - To account for all time zones, 1 calendar day will look at 24-48 hours of user history, depending on the time the segment is evaluated; for 2 calendar days, will look at 48-72 hours of user history, and so on.
Segments your users by the amount of money that they have spent in your app in the last specified number of calendar days between 1 and 30. This amount will only include the sum of the last 50 purchases.
Learn more about X-in-Y behavior here.
Segments your users by the number of times a purchase was made in relation to a certain purchase property in the last specified number of calendar days between 1 and 30.
Learn more about X-in-Y behavior here.
Segments your users by the number of times (between 0 and 50) they have made a purchase in the last specified number of calendar days between 1 and 30.
Learn more about X-in-Y behavior here.
Segments your users by the number of sessions (between 0 and 50) they have had in your app in the last specified number of calendar days between 1 and 30.
Learn more about X-in-Y behavior here.