Segmentation Filters

Ad Tracking Enabled

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.

Age

Segments your users by their age, as they indicated from within your app.

Amplitude Cohorts

Clients who use Amplitude can supplement their segments by choosing and importing their cohorts in Amplitude.

Background Push Enabled

Segments by whether users have a push token and haven't unsubscribed.

Birthday

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".

Braze Segment Extensions

After creating a Segment Extension in the Braze dashboard, you can choose to include/exclude those extensions in your segment.

Census Cohorts

Clients who use Census can supplement their segments by choosing and importing their cohorts in Census.

Churn Risk Category

Segments your users by churn risk category according to a specific prediction.

Churn Risk Score

Segments your users by churn risk score according to a specific prediction.

City

Segments your users by their last indicated city location.

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.

Clicked Alias in Campaign

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.

Clicked Alias in Canvas Step

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.

Clicked card

Segments your users by whether or not they have clicked a specific Content Card. This filter is available as a subfilter of "Clicked/opened campaign", "Clicked/opened campaign or Canvas with Tag", and "Clicked/opened step".

Clicked/Opened Campaign

Filter by interaction with a specific campaign. For email messaging, the open event includes both machine opens and non-machine opens.

For email, this also includes the option to filter by "opened any email (machine opens)" and "opened any email (other opens)". 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. For email messaging, the open event includes both machine opens and non-machine opens.

For email, this includes the option to filter by "opened any email (machine opens)" and "opened any email (other opens)". 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.

Clicked/Opened Step

Filter by interaction with a specific Canvas component. For email messaging, the open event includes both machine opens and non-machine opens.

For email, this includes the option to filter by "opened any email (machine opens)" and "opened any email (other opens)".

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.

Connected Facebook

Segments your users by whether they connected your app to Facebook.

Connected Twitter

Segments your users by whether they connected your app to X (formerly Twitter).

Converted From Campaign

Segments your users by whether or not they have converted on a specific campaign. This filter doesn't include users that are in the control group.

Converted From Canvas

Segments your users by whether or not they have converted on a specific Canvas. This filter doesn't include users that are in the control group.

Country

Segments your users by their last indicated country location.

Created At

Segments users by when their user profile was created. If a user was added by CSV or API, then this filter reflects the date they were added. If the user isn't added by CSV or API and has their first session tracked by the SDK, then this filter reflects the date of that first session.

Custom Attributes

Determines whether or not a user matches a custom recorded attribute value. (24-hour period)

Time zone:
Company's Time Zone

Custom Event

Determines whether or not a user has performed a specially recorded event.

Example:
Activity completed with property activty_name.

Time zone:
UTC - Calendar Day = 1 calendar day will look at 24-48 hours of user history

Day of Recurring Event

This filter looks at the month and day of custom attribute with the data type of "date", but does not look at the year. This filter is useful for annual events.

Time zone:
This filter adjusts for whatever time zones the user is in.

Device Carrier

Segments your users by their device carrier.

Device Count

Segments your users by how many devices they have used your app on.

Device Google Ad ID

Segments your users by the Google ad ID.

Device IDFA

Allows you to designate your campaign recipients by IDFA for testing.

Device IDFV

Allows you to designate your campaign recipients by IDFV for testing.

Device Model

Segments your users by their mobile phone's model version.

Device OS

Segments your users that have one or more devices with the specified operating system.

Device Roku Ad ID

Segments your users by the Roku ad ID.

Device Windows Ad ID

Segments your users by the Windows ad ID.

Email Address

Allows you to designate your campaign recipients by individual email addresses for testing. This can also be used to send transactional emails to all your users (including unsubscribed) using the "Email Address is not Blank" specifier within the filter, so that you can maximize delivery of emails regardless of opt-in status.

This filter only checks if user profiles have an email address, whereas the Email Available filter checks for additional criteria.

Email Available

Segments your users by whether they have a valid email address, and if they are subscribed or opted-in to email. This 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.

Note that if you send a transactional message, users whose "Email Available" is false won't be included in the audience calculation but could still receive a message. However, the audience calculation will include only subscribed or opted-in users.

For emails where the opt-in status is important, we suggest using the "Email Available" filter instead of the Email Address filter; the additional criteria can help you target users who truly want to see your messages.

Email Opt In Date

Segments your users by the date on which they opted into email.

Email Subscription Status

Segments your users by their subscription status for email.

Email Unsubscribed Date

Segments your users by the date on which they unsubscribed from future emails.

Entered Canvas Variation

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.

Event Likelihood Category

Segments your users by likelihood of performing an event according to a specific prediction.

Event Likelihood Score

Segments your users by likelihood of performing an event according to a specific prediction.

External User ID

Allows you to designate your campaign recipients by individual user IDs for testing.

Feature Flags

The segment of your users that have a particular feature flag currently enabled.

First Did Custom Event

Determines the earliest time that a user has performed a specially recorded event. (24-hour period)

Example:
First Abandoned Cart Less than 1 day ago

Time zone:
Company's Time Zone

First Made Purchase

Segments your users by the earliest time that a user made a purchase in your app.

First Name

Segments your users by their first name, as they indicated from within your app.

First Purchase For App

Segments your users by the earliest time that a user made a purchase from your app.

First Used App

Segments your users by the earliest recorded time that they opened your app. Note that this will capture the first session they have using a version of your app with the Braze SDK integrated. (24-hour period)

Time zone:
Company's Time Zone

First Used Specific App

Segments your users by the earliest recorded time that they opened any of your apps within your workspace. (24-hour period)

Time zone:
Company's Time Zone

Gender

Segments your users by gender, as they indicated from within your app.

Hard Bounced

Segment your users by whether or not their email address has hard bounced (such as the email address is invalid).

Has App

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.

Has Marked You As Spam

Segments your users by whether or not they have marked your messages as spam.

Has Never Received a Message from Campaign or Canvas Step

Segments your users by whether or not they have received any campaign or Canvas component.

Heap Cohorts

Clients who use Heap can supplement their segments by choosing and importing their cohorts in Heap.

Hightouch Cohorts

Clients who use Hightouch can supplement their segments by choosing and importing their cohorts in Hightouch.

In Campaign Control Group

Segments your users by whether or not they were in the control group for a specific multivariate campaign.

In Canvas Control Group

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.

Install Attribution Ad

Segments your users by the ad that their install was attributed to.

Install Attribution Adgroup

Segments your users by the ad group that their install was attributed to.

Install Attribution Campaign

Segments your users by the ad campaign that their install was attributed to.

Install Attribution Source

Segments your users by the source that their install was attributed to.

Intelligent Channel

Segment your users by their most active channel in the last three months.

Invalid Phone Number

Segments your users by whether or not their phone number is invalid.

Kubit Cohorts

Clients who use Kubit can supplement their segments by choosing and importing their cohorts in Kubit.

Language

Segments your users by their preferred language.

Last Did Custom Event

Determines the latest time that a user has performed a specially recorded event. This filter supports decimals, such as 0.25 hours. (24-hour period)

Example:
Last Abandoned Cart Less than 1 day ago

Time zone:
Company's Time Zone

Last Engaged With Message

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). For email messaging, the open event includes both machine opens and non-machine opens. (24-hour period)

For emails, this is when an email request is sent to the email service provider (regardless if it actually gets delivered). This also includes the option to filter by "opened any email (machine opens)" and "opened any email (other opens)". 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

Last Enrolled in Any Control Group

Segments your users by the last time that they fell into the control group in a campaign.

Time zone:
Company's Time Zone

Last In App Message Impression

Segments your users by the last time they viewed an in-app message.

Last Made Purchase

Filter users by the last time they made a purchase.

Last Name

Segments your users by their last name, as they indicated from within your app.

Last Purchased Product

Filter users by when they last purchased a specific product.

Last Received Any Message

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

Last Received Email

Segments your users by the last time that they have received one of your email messages. (24-hour period)

Time zone:
Company's Time Zone

Last Received Message from Campaign or Canvas With Tag

Segments your users by when they received a specific campaign or Canvas with a specific tag. This filter doesn't consider when users received other campaigns or Canvases. (24-hour period)

Last Received Message from Specific Campaign

Segments your users by whether or not they have received a specific campaign. This filter doesn't consider when users received other campaigns.

Last Received Message from Specific Canvas Step

Segments your users by when they received a specific Canvas component. This filter doesn't consider when users received other Canvas components.

Last Received Push

Segments your users by the last time that they received one of your push notifications. (24-hour period)

Time zone:
Company's Time Zone

Last Received SMS

Segments your users by the time that the last message was delivered to the SMS provider. This doesn't guarantee that the message was delivered to the user's device. (24-hour period)

Time zone:
Company's Time Zone

Last Received Webhook

Segments your users by the last time that Braze sent a webhook for that user. (24-hour period)

Time zone:
Company's Time Zone

Last Received WhatsApp

Segments your users by the last time that they received a WhatsApp message. This is when the last message API request is sent to WhatsApp, not when the message is delivered to the user's device. (24-hour period)

Time zone:
Company's Time Zone

Last Sent Specific SMS Inbound Keyword Category

Segments your users by when they last sent an SMS to a specific subscription group within a specific keyword category.

Last Used App

Segments your users by the most recent time that they have opened your app. (24-hour period)

Time zone:
Company's Time Zone

Last Used Specific App

Segments your users by the most recent time that they have opened a specific, designated app. (24-hour period)

Time zone:
Company's Time Zone

Location Available

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.

Median Session Duration

Segments your users by the median length of their sessions in your app.

Message Open Likelihood

Filters your users based on their likelihood to open a message on a specified channel on a scale of 0-100%. Users without sufficient data to measure a likelihood for a channel can be selected using "is blank."

Mixpanel Cohorts

Clients who use Mixpanel can supplement their segments by choosing and importing their cohorts in Mixpanel.

Money Spent

Segments your users by the amount of money that they have spent in your app.

Most Recent App Version Name

Segments by the recent name of the user's app.

Most Recent App Version Number

Segments by the recent app version number of the user's app.

Most Recent Device Locale

Segments your users by the locale information from the most recently used device.

Most Recent Location

Segments your users by the last recorded location at which they have used your app.

Most Recent Watch Model

Segments your users by their most recent smartwatch model.

Nested Custom Attributes

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.

Number of Facebook Friends Using App

Segments your users by how many Facebook friends they have who use the same app.

Number of Twitter Followers

Segments your users by how many X (formerly Twitter) followers they have.

Phone Number

Segments your users by the E.164 formatted 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 an unformatted phone number but not a sending phone number. This segment filter returns users by their e.164 formatted phone number (when available).

Use cases:
- Use this filter to understand the most accurate target audience size when sending SMS or WhatsApp messages.
- 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.

Provisionally Authorized on iOS

Allows you to find users who are provisionally authorized on iOS 12 for a given app.

Purchased Product

Segments your users by products purchased in your app.

Push Enabled

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.

Push Enabled For App

Segments by whether users have push enabled for your app on their device. These users are reachable via push but might not be opted in. This count includes users who have provisionally authorized foreground and background push tokens.

Push Opt In Date

Segments your users by the date on which they opted into push.

Push Subscription Status

Segments your users by their subscription status for push.

Push Unsubscribed Date

Segments your users by the date on which they unsubscribed from future push notifications.

Random Bucket #

Segments your users by a randomly assigned number (0 to 9999 inclusive). It can enable the creation of uniformly distributed segments of truly random users for A/B and multivariate testing.

Received Campaign Variant

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.

Segment Cohorts

Clients who use Segment can supplement their segments by choosing and importing their cohorts in Segment.

Segment Membership

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 because this may create a cycle where Segment A includes Segment B, which then tries to include Segment A again. If that happened, the segment would keep referencing itself, making it impossible to calculate who actually belongs in it. Also, nesting segments like this adds complexity and can slow things down. Instead, recreate the segment you're trying to include using the same filters.

Session Count

Segments your users by the number of sessions they have had in any of your apps within your workspace.

Session Count For App

Segments your users by the number of sessions they have had in a specific, designated app.

Soft Bounced

Segment your users by whether they soft bounced X times in Y days. Segment filters can only look back 30 days, but you can look back further with Segment Extensions.

This filter operates differently than a soft bounce event in Currents. The Soft Bounced segment filter counts a soft bounce if there was no successful delivery during the 72 hour retry period. In Currents, every unsuccessful retry is sent as a soft bounce event.

Subscription Group

Segments your users by their subscription group for email, SMS/MMS, or WhatsApp. Archived Groups will not appear and cannot be used.

Tinyclues Cohorts

Clients who use Tinyclues can supplement their segments by choosing and importing their cohorts in Tinyclues.

Total Number of Purchases

Segments your users by how many purchases they have made in your app.

Unformatted Phone Number

Segments your users by their unformatted phone number. Does not include parenthesis, dashes, or other symbols.

Uninstalled

Segments your users by whether they have uninstalled your app and have not reinstalled it.

Updated/Imported from CSV

Segments your users based on whether they were a part of a CSV upload or not.

Web Browser

Segments your users by the web browser they use to access your website.

X Custom Event In Y Days

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.

X Money Spent in Y Days

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.

X Product Purchased In Y Days

Filter users by times a specific product was purchased.

X Purchase Property In Y Days

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.

X Purchases in Last Y Days

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.

X Sessions In Last Y Days

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.