Custom Events

Custom Events are actions taken by your users; they’re best suited for tracking high-value user interactions with your application. Logging a custom event can trigger any number of follow-up campaigns with configurable delays, and enables the following segmentation filters around the recency and frequency of that event:

Segmentation Options Dropdown Filter Input Options
Check if the custom event has occurred more than X number of times MORE THAN INTEGER
Check if the custom event has occurred less than X number of times LESS THAN INTEGER
Check if the custom event has occurred exactly X number of times EXACTLY INTEGER
Check if the custom event last occurred after X date AFTER DATE
Check if the custom event last occurred before X date BEFORE DATE
Check if the custom event last occurred more than X days ago MORE THAN NUMBER OF DAYS AGO (Positive) Integer)
Check if the custom event last occurred less than X days ago LESS THAN NUMBER OF DAYS AGO (Positive) Integer)
Check if the custom event occurred more than X (Max = 50) number of times MORE THAN in the past Y Days (Y = 1,3,7,14,21,30)
Check if the custom event occurred less than X (Max = 50) number of times LESS THAN in the past Y Days (Y = 1,3,7,14,21,30)
Check if the custom event occurred exactly X (Max = 50) number of times EXACTLY in the past Y Days (Y = 1,3,7,14,21,30)

Braze notes the number of times these events have occurred as well as the last time they were performed by each user for segmentation. On the custom events analytics page you can view in aggregate how often each custom event occurs, as well as by segment over time for more detailed analysis. This is particularly useful to view how your campaigns have affected custom event activity by looking at the gray lines Braze overlays on the time-series to indicate the last time a campaign was sent.

custom_event_analytics_example.png

Custom Event Properties

With Custom Event Properties, you can set properties on custom events and purchases. These properties can than be used for further qualifying trigger conditions, increasing personalization in messaging, and generating more sophisticated analytics through raw data export. Property values can be string, numeric, boolean, or Date objects. However, property values cannot be array objects.

For example, if an eCommerce application wanted to send a message to a user when he/she abandons their cart, it could additionally improve its target audience and allow for increased campaign personalization by adding a Custom Event Property of the ‘cart value’ of users’ carts.

customEventProperties.png

Custom Event Properties can also be used for personalization within the messaging template. Any campaign using Action-Based Delivery with a trigger event can use custom event properties from that event for messaging personalization. If a gaming application wanted to send a message to users who had completed a level, it could further personalize the message with a property for the time it took users to complete that level. In this example the message is personalized for three different segments using conditional logic. The Custom Event Property called time_spent, can be included in the message by calling {{event_properties.${time_spent}}}.

Custom Event Properties are designed to help you personalize your messaging or build granular Action-Based Delivery Campaigns. If you would like to create segments based on event property recency and frequency, please reach out to your Customer Success Manager, as this may incur additional data costs.

WAS THIS PAGE HELPFUL?