Use a time series to find when activity changed. Use Attribute Flow to compare related values within the selected events. Use a journey visualisation when you need transitions between successive journey steps.
Event volume over time
Add Velocity of Value or Time Series (Count). Set a grouping attribute to split the series, or leave grouping empty for one overall event-volume series. Add event-type and filter conditions, use Greater than 0 as the starting threshold, and preview.
For a decision breakdown, group by:
outcome['CHAMPION'].decision_strategy.result
Events without a decision may form a separate missing-value group. That can be expected on steps that collect information without applying a decision strategy.
Where the bar/line controls are shown, switch between columns and lines to make the pattern easier to read. Configure Show Legend as Never, Fullscreen or Always. A line can clarify a trend; columns make individual bucket totals easier to compare.
Time buckets
For the shared Top X time-series calculations, bucket size follows the selected interval:
| Selected interval | Bucket size |
|---|---|
| Up to five hours | Minute |
| More than five hours, up to six days | Hour |
| More than six days | Day |
Distinct Count and Attribute Flow summarise the selected period without these time buckets. Specialised widgets can use their own interval rules: for example, Proxy/VPN Users by Hour is an hourly view.
Check your portal's UTC/local time preference when comparing charts or exports. Partially elapsed calendar periods and incomplete buckets should not be compared with completed periods as though they have equal observation time.
Numeric values over time
Add Statistics of Value or Time Series (Median). Select the numeric attribute and explicitly select the statistic you want. The Time Series (Median) entry opens the statistical configuration; verify that Quantile = 0.5 is selected before calling the result a median.
Use Avg for a mean, or compare a median and a high quantile when a few extreme values could distort the mean. The display can be a chart or table depending on the selected statistics. The bar/line toggle is available for Velocity Of and supported average-only configurations.
Signal counts across a period
Add Velocity of Signal. Select the signal-containing attribute, then choose all signals or specific values. A collection of model signals and a collection of device signals are different inputs; choose the collection that answers your question.
Optionally group by another attribute to compare the selected signals across channels, steps or bot types. Add an event filter to isolate the relevant population.
Signal counts over time
Add Velocity of Signal over Time and configure the signal collection, optional selected signals, grouping, event restrictions and threshold. Use it to see whether a signal spike coincided with a traffic change.
A signal count is not a trigger rate. Use Signal Trigger Rate to compare triggers against an event population.
Attribute Flow
Attribute Flow connects the values of two or more ordered grouping attributes. For example:
- Add Attribute Flow.
- Under With the same (group by)…, select
step_namefirst. - Select
outcome['CHAMPION'].decision_strategy.resultsecond. - Add any event filter, set the threshold and result limit, and preview.
- Read each band as a relationship between the adjacent attribute values. Wider bands represent more contributing results.
Attribute Flow does not reconstruct a user's chronological path. Its stages are attributes of matching events. For chronological step transitions, use the journey views. Missing values at an adjacent stage can prevent a link from being drawn, and the result limit can omit lower-ranked combinations.