Custom Events (Bloomreach Engagement)

Custom events are the events a business chooses to track in Bloomreach Engagement, with attributes the business defines itself. Typical examples are `purchase`, `purchase_item`, `view_item`, `view_category`, `cart_update`, `checkout` and `consent`. Unlike system events, their names and attributes vary from project to project because each integration decides what to send. The SDK adds `location`, `os`, `device` and `browser` to every tracked event by default. The common failure is a `purchase` event whose `total_price` or `purchase_status` is named differently from the documented convention. Dashboards and predictions then cannot find the field until data mapping points them to it.