Skip to content

Data points

At Braze, data means action: each piece of data that arrives in Braze updates segment membership, can trigger and cancel messaging, is immediately available for messaging personalization, and more. Data points help you define the most impactful information for your business. By thoughtfully considering what information to track, you ensure that you’re targeting the highest-impact data for your users’ experience.

Data points define a billing and pricing structure based on information logged against user profiles. Our Customer Success team can help recommend data best practices to fit your needs. You can find a more detailed breakdown of this definition in your Braze contract.

“Data points” shall refer to a billable unit of use of the Braze Services, measured by a session start, session end, custom event, or purchase recorded, as well as any attribute set on an end user profile. For clarity, each one of the above-mentioned data (such as session start, session end, custom event, or purchase recorded, as well as any attribute) set to an end user’s profile at one point in time shall each count as a single data point.

Data and events collected by default by the Braze Services, including, for example, push tokens, device information, and all campaign engagement tracking events, such as email opens and push notification clicks, are not counted as data points.

See this article’s Consumption count section to understand what data counts toward your data point allocation.

Management and usage

To view your data point usage, go to Settings > Billing and select the Total Data Points Usage tab.

For more information on the data point dashboard components, refer to Billing.

Consumption count

In sum, data points are accumulated when a user’s profile data is updated or when they perform specific actions. Essentially, data points are counts of each of your user’s session starts, session ends, events, and purchases.

You can find a breakdown of how Braze accumulates data points in the following sections. If you ever have any questions about the nuances of Braze data points, your Braze account manager can answer them.

The following actions do not consume data points:

  • Deleting users from Braze
  • Using Connected Content in messaging
  • Subscription state changes globally and around subscription groups
  • Renaming your users’ external IDs through API calls
  • Blocking events, attributes, or event properties

Special circumstances


An array is an ordered collection of items stored within a custom attribute. In terms of consumption, updating an array costs one data point per API call. If you add values to an array incrementally, it will count as one data point per value.


Custom attributes uploaded via CSV count toward your data points. However, CSV imports for segmentation purposes (imports made with external_id, braze_id, or user_alias_name as the only field) will not consume data points.

Also, as subscription state changes do not consume data points, updating the email_subscribe, push_subscribe, subscription_group_id, or subscription_state fields in your CSV file will not incur charges.

Data points

Non-billable data points (out of the box)

Data type Data point
Profile data Country
Profile data Language
Profile data User ID
Profile data User alias
Recent devices Number of devices
Recent devices Most recent watch
Recent devices App version
Recent devices Device
Recent devices Device OS
Contact settings Email subscribed
Contact settings Push subscribed
Contact settings Apps registered for push
Contact settings Subscription group
Campaigns received Email address
Install attribution Install source
Install attribution Campaign
Install attribution Ad Group
Install attribution Ad
Miscellaneous Random bucket number
Canvas messages received Canvas messages received
Twitter Followers
Twitter Following
Twitter Number of tweets
Facebook Likes

Billable data points

Data type Data point Notes
Profile data First name  
Profile data Last name  
Profile data Email address  
Profile data Gender  
Profile data Age group  
Profile data Country When manually collected. Does not count toward consumption when automatically collected.
Profile data City  
Profile data Language When manually collected. Does not count toward consumption when automatically collected.
Profile data Most recent device locale  
Profile data Time zone  
Profile data Date of birth (DOB)  
Profile data Bio  
Profile data Phone number  
App usage data Session start  
App usage data Session end  
Custom attributes All custom attributes  
Custom events All custom events  
Custom event properties All custom event properties Custom event properties enabled for segmentation with the filters X Custom Event Property in Y Days or X Purchase Property in Y Days are all counted as separate data points in addition to the data point counted by the custom event itself.
Purchases All purchases  
Amplitude cohort assignment All assignments  
Mixpanel cohort assignment All assignments  
Hightouch cohort assignment All assignments  
Appsflyer cohort assignment All assignments  
Most recent location All most recent locations Entering or exiting geofences doesn’t consume data points because geofence data is not stored against the user profile. Geofences are monitored by Apple and Google location services; Braze only gets notified upon a user triggering a geofence.
Twitter Username  
New Stuff!