Summary
Add support for temporal filters in rollup properties so customers can calculate values from associated records within a rolling or fixed time window.
This request is related to: Rolling Date Property Options
Problem statement
Today, rollup properties support aggregations like min, max, count, sum, average, earliest date, and latest date, and they allow conditional filters. However, those conditions do not support the kind of date-based logic needed for common business questions such as:
- Average NPS rating from the last 12 months
- Sum of associated revenue from the current quarter
- Count of support tickets created in the last 30 days
- Average product usage over the last 90 days
This creates a gap between what customers can report on in analysis tools and what they can store as a reusable property on the record.
Example use case
As a customer, I want to calculate the average of the latest NPS survey responses over the last 12 months so that I can:
- surface this metric directly on company or contact records
- use it in lists, workflows, scoring, and segmentation
- avoid maintaining separate reports or manual exports for operational use cases
Why the current behavior is limiting
Customers can currently:
- store NPS response data on contact properties
- analyze survey responses within a selected date range in feedback reporting
- use rollup properties to average numeric values from associated records
But they cannot combine these into a property-level metric when the definition depends on time (i.e., trailing average of NPS survey ratings).
In practice, this means a user can answer the question in reporting, but cannot operationalize the answer as a property for automation, filtering, scoring, or record-level visibility.
Requested functionality
Support time-based conditions in rollup properties, including both:
1) Rolling windows
Examples:
- in the last 7 days
- in the last 30 days
- in the last 90 days
- in the last 12 months
- in the current month / quarter / year
2) Fixed date ranges
Examples:
- between January 1, 2026 and December 31, 2026
- between two specified dates
- before / after a selected date
Proposed UX
When configuring a rollup property, allow the user to add a condition based on a date or datetime property from the associated record, with operators such as:
- is in the last X days
- is in the last X months
- is in the current month
- is in the current quarter
- is in the current year
- is between
- is before
- is after
Ideally, these would work alongside the existing association-label and conditional logic options.
Expected benefits
- Makes rollup properties more useful for operational metrics, not just lifetime aggregates
- Enables better automation, segmentation, and record-level visibility
- Reduces dependence on custom workflows, exports, or external computation
- Aligns property logic more closely with the date filtering customers already expect in reporting and lists
Priority rationale
This would unlock a broad set of high-value use cases across Service, Sales, and Customer Success, especially for customers trying to operationalize time-bound health, satisfaction, activity, and revenue metrics.
Concrete example to reference
Need: Average latest NPS survey responses over the last 12 months
Current limitation: Rollup properties can average values, but cannot apply a rolling 12-month filter to the associated response data
Desired outcome: A reusable property that updates automatically and can be used across records, views, workflows, and reports
Suggested acceptance criteria
- Rollup properties can filter on date/datetime properties from associated records
- Users can choose both rolling and fixed temporal filters
- Temporal filters can be combined with existing rollup conditions
- Supported rollup types include at least count, sum, average, min, and max when date filters are present
- The resulting property is usable anywhere standard rollup properties are usable today
