Streamline data management by allowing CRM Administrators & HubSpot Operations Managers to create “Property Bundles” that automatically generate associated tracking properties (e.g., date-stamped, duration, and transition properties) alongside a primary property.
The Problem: Currently, when building out custom tracking (such as tracking a custom status or an internal milestone), the process is highly manual and repetitive. If I create a custom property, I often need a corresponding set of “helper” properties to make that data actionable:
- Date entered [Status]
- Date exited [Status]
- Time in [Status]
- Previous [Status]
Creating these one-by-one is tedious, error-prone, and adds unnecessary clutter to the property creation workflow. It creates a significant barrier to maintaining clean, well-tracked data.
The Proposed Solution: Implement a “Property Bundle” or “Property Group Template” feature within the Property Settings.
- When creating a primary property, provide an optional checkbox to “Attach Tracking Bundle.”
- Selecting this would automatically generate a pre-configured set of associated properties (timestamps, counters, etc.) using the base name of the primary property.
- This would mirror the logic HubSpot already uses for default properties like Lifecycle Stage, bringing that “native” level of tracking functionality to custom objects and properties.
- Would natively group primary and auxilary properties into the same property group .
This grouping would cut down on the time it takes for getting projects up and running by standardizing repetitive tasks, ensure every property is organized, and would let you accurately track activities that might otherwise be missed.
How this differs from “Property Change Events”:
I am aware of the existing “Property Change Event” functionality. While helpful for audit trails and tracking who changed a value, it does not serve the need for actionable, record-level tracking.
My proposal is for “Property Bundles” that generate native CRM properties on the record. Unlike Event data, these properties would be:
- Immediately usable in standard Lists and Workflows without custom coded actions.
- Visible directly on the Record view for Sales/Service/Marketing users.
- Not subject to the 25-event limit of the Events tool, allowing for granular tracking across the entire CRM architecture.