September 11, 2026 — Versioned analyses, events through the agent, and marks
You now edit an analysis without changing what is live, track how many times each condition of a rule was met, look up received events through the agent, and identify accounts and items by a visual mark.
Versioned analyses
You now change an analysis without the change reaching real traffic ahead of time. Every edit creates a draft, and publishing takes the whole cascade live at once. A previous version can be restored, and a version can run in observation, deciding nothing. See Versioning.
Rules that use an analysis
The analysis page now shows the rules that run it and those that record it, and flags the two incomplete states: the analysis that scores with nobody recording it, and the one that is recorded with nobody querying it. Removing an analysis in use is now refused. See Analyses.
Conditions met
You now see how many times each condition of a rule was met on each day, on the version page, alongside the total runs. The reading distinguishes the day with no traffic from the day the rule ran and the condition was never met. See Versioning.
Agents
The agent connected to the account now reads received events, beyond the configuration: it counts a period’s events, optionally split by a field, and retrieves the rows themselves, with the same filters as Explore. It also lists the account’s analyses and details one of them. See Agents.
Incompatible changes to agent access
Reading the account’s data now requires a consent of its own, separate from the configuration consent. The change is incompatible: a connection authorized only to read the configuration stops reaching the lookup of metric values and the listing of a field’s values, until it is reconnected. See Agents.
Incompatible changes to agent responses
Two changes are incompatible for those who read the agent’s responses themselves: an event type’s detail no longer carries the values already received by a list field, which come only from the field’s value listing; and references to lists and to fields in filters now occupy keys of their own. See Agents.
Explore
You now compare two fields of the same event type inside a filter. The filter’s value can name another field with $field_name in place of a typed value, and the query compares the two columns row by row, which locates the events where they disagree. See Explore.
Marks
You now identify an account or an item of a list field by a visual mark: a color, an icon, or a brand’s logo, located by name or by website address. The mark follows the record wherever it is presented. See Settings and Fields.
Other improvements
- Alerts: an alert’s feedback block is now called Ratings, and the attribution, in the panel and in the Slack notification, now reads Rated by. See Alerts.
- Rules: on a published version, the edit button is now called New version from this one, and the version states that it cannot be edited.
- Analyses: the run analysis action takes the Version target, which writes to the event which version of the analysis decided the case.
Fixes
- Rules in observation: a version in observation over a field with inheritance received the value inherited by the active version, not its own, which made the two versions look like they agreed precisely on the events where inheritance decides. Observation now keeps a memory of its own. See Versioning.
- Fields: creating a field could be refused with an error about a column the form does not show, and the page came back without indicating what had prevented the registration. Registration completes again.
- Explore: opening an Explore address with no active session returned an error instead of the sign-in screen. The sign-in screen now opens normally; when the address is too long to be kept, the return is to the home page.
- Exports: the accents in a CSV file appeared corrupted when opening the file on macOS. The file is now recognized as UTF-8.
- Notifications: an alert notification was discarded when the destination refused the delivery by rate limiting. Delivery is now rescheduled and retried.