Feature request
Is your feature request related to a problem?
When configuring a CDP destination (e.g. HubSpot), the "Trigger options" allow throttling to "Run once per person per interval" with a maximum interval of 24 hours. This uses a rolling 24-hour window, not calendar-day boundaries. Customers who want to send exactly one event per calendar day of user activity are unable to do so: if a user is active at 11pm Monday and 7am Tuesday, the Tuesday event is suppressed because the rolling window hasn't expired.
Describe the solution you'd like
Add a calendar-day-based interval option to CDP destination trigger options, e.g. "Run once per person per calendar day." This would reset the deduplication window at midnight (in the project's configured timezone) rather than using a rolling TTL.
Describe alternatives you've considered
- Rolling 24-hour window: Close but not accurate at day boundaries. Misses the late-evening-then-early-morning case.
- Deduplication on the destination side: Pushes complexity to the customer's CRM workflow and not all destinations support it.
- Custom Hog expression via API: The masking hash field accepts arbitrary Hog expressions, so a date-aware hash could theoretically be set via the API today, but this isn't exposed in the UI and isn't documented or supported.
Additional context
Reported by a customer wanting to send a "daily active use" event to HubSpot. The use case of "notify an external system once per calendar day of activity" is likely common across CRM and marketing integrations.
Debug info
Feature request
Is your feature request related to a problem?
When configuring a CDP destination (e.g. HubSpot), the "Trigger options" allow throttling to "Run once per person per interval" with a maximum interval of 24 hours. This uses a rolling 24-hour window, not calendar-day boundaries. Customers who want to send exactly one event per calendar day of user activity are unable to do so: if a user is active at 11pm Monday and 7am Tuesday, the Tuesday event is suppressed because the rolling window hasn't expired.
Describe the solution you'd like
Add a calendar-day-based interval option to CDP destination trigger options, e.g. "Run once per person per calendar day." This would reset the deduplication window at midnight (in the project's configured timezone) rather than using a rolling TTL.
Describe alternatives you've considered
Additional context
Reported by a customer wanting to send a "daily active use" event to HubSpot. The use case of "notify an external system once per calendar day of activity" is likely common across CRM and marketing integrations.
Debug info