A running aggregate is a Bloomreach Engagement definition that computes a value for each event from the events around it. An example is the country of the last `session_start` before each `purchase`. A regular aggregate produces one value per customer, for example lifetime spend. A running aggregate produces one value per event, so an analysis can be split by an attribute the event itself never carried. An including/excluding switch decides whether the event being computed for (the anchor) counts toward its own value. That matters when the anchor and the source event are the same type. Running aggregates work in analyses but not in Jinja personalization; only aggregates work there.
Category
Metrics, Data Architecture
Also known as
running aggregates; event-level aggregate
In practice
Reach for a running aggregate when a report must split one event by an attribute tracked on a different event. If the value is needed inside an email or in a filter on the customer, build an aggregate instead.
Related
Something out of date?