What This Update Actually Is
HubSpot custom events let you track almost anything: video views, cart abandonment, product page visits, file downloads, in-app actions. But until now, when those events fired, the timeline card on a contact, company, or deal record looked like a wall of raw property data.
This update adds a fourth step to the custom event setup wizard: Customize Timeline. You can now write a header and subheader using token-based templates that pull in real values when the event fires. You can choose which properties appear on the expanded card. And you can drag those properties into any order you want.
You can also hide the property list entirely when the header and subheader already tell the full story. This is not a cosmetic tweak. It's a fundamental shift in how custom event data becomes readable for the humans who live in those records every day.
Why HubSpot Shipped This
Custom events are powerful, but they've always had a readability problem. A sales rep opening a contact record and seeing "custom_event_fired: true" alongside a dozen property values in no particular order doesn't know what to do with that. They have to dig. They have to guess. Often, they ignore it entirely.
That gap matters most in hand-off moments. When a marketing event fires and a sales rep needs to act on it, or when a support agent is reviewing what a contact did before filing a ticket, raw event data creates friction. The internal frustration is real: your team set up the event, but the people reading the timeline don't trust what they're seeing.
HubSpot shipped this to close that gap. The goal is that anyone reviewing a record's activity should immediately understand what happened, without needing to be the person who built the event.
How to Use It Step by Step
- Open a new or existing custom event in HubSpot. Navigate to step 4, labeled Customize Timeline, either by progressing through the wizard or clicking it directly in the top navigation bar.
- Use the Insert Token dropdown to build your header template. Pull in the linked record's name, any property defined on this custom event, or any object properties you added in step 3 (Enrich Event). The right-hand preview updates in real time.
- Write a subheader the same way. Use it to surface the next most important detail: the specific action taken, the value involved, or the source of the event.
- In the property display section, uncheck any properties you don't want shown on the expanded card. Drag the remaining properties using the handle on the left to set the order from most to least important.
- If your header and subheader already tell the complete story, turn off the Show Properties toggle entirely. The card will display only those two lines on the expanded view.
- Save the event. Fire a test event and open the linked record's activity timeline to confirm the card reads the way you intended before rolling it out to live traffic.
What It Touches in Your HubSpot Strategy
This update touches more than just the timeline view. Think through every place your team uses custom events today, and ask whether the humans reading those records can actually act on what they see.
On the Smart CRM side, this directly improves the signal quality on contact, company, deal, and ticket records. If you've built behavioral scoring models that rely on custom events, cleaner timeline readability means your reps will actually notice those signals instead of scrolling past them.
Key Takeaway
If your team uses custom events for behavioral scoring, readable timeline cards mean sales reps will act on those signals. Unreadable cards get ignored. This update turns data into decisions.
On the workflow side, custom events already trigger automation. But when a workflow fires because of an event and a rep then looks at the record to understand context, the timeline card is what they read. A well-labeled card reduces the need for internal Slack messages and hand-off calls.
On the reporting side, this doesn't change your event data or your reports. But it does change how your team interprets events in context. Pairing readable event cards with real-time data in the CRM creates a much cleaner operational picture.
That's especially relevant if you've already turned on HubSpot's real-time table updates. Live property data on index pages combined with readable event cards on the record view is a significant upgrade to how your team experiences the CRM.
On the integration side, if you're sending custom events from an external system via the Events API, this update applies there too. You can now control how those third-party events surface on HubSpot records, which is a major win for RevOps teams managing complex tech stacks.
Key Takeaway
Custom events sent via the HubSpot Events API from external tools now also benefit from timeline display customization. RevOps teams with multi-system data flows should audit their existing custom events and apply headers and subheaders to every event that's customer-facing or rep-facing.
If your data strategy involves pulling external signals into HubSpot, this pairs naturally with tools like Webhook Data Sources in HubSpot Data Studio. The more you can bring external behavioral data into HubSpot, the more important readable event cards become.
Who Should Care Most
Not everyone feels this equally. Here's who should prioritize it right now.
- RevOps and Marketing Ops teams who built custom events for behavioral tracking: go back through every active custom event and apply the new display settings. This is a one-time investment that pays off every time a rep or agent opens a record.
- Sales teams using HubSpot Sales Hub Professional or Enterprise who rely on behavioral context before calls: readable event cards mean less pre-call research time and faster qualification decisions.
- Service Hub teams handling complex tickets where a contact's pre-ticket behavior matters: if a customer abandoned a form or hit an error before filing a ticket, that event card should tell the agent exactly what happened at a glance.
- SaaS companies and e-commerce operators tracking in-app or on-site events via the Events API: this is the group with the most to gain, since their events often carry complex property data that previously had no readable display layer inside HubSpot.
- Businesses in onboarding or implementation phases with Marketing Hub Professional and above: building readable custom events from the start is far easier than retrofitting them later. Set the display format now, before your event library grows.
George's Take
We see this pattern constantly inside portals: a talented ops person builds a sophisticated custom event schema, it fires perfectly, the data is all there, and then it sits invisible because nobody on the front line knows how to read it. The event did its job. The timeline didn't. That's not a data problem. That's a communication design problem. This update hands you the tools to solve it inside HubSpot itself, without asking your reps to become data engineers. I'd start with your three most-fired custom events today, apply the new display settings, and watch how quickly the humans on your team start referencing that data in their calls.
“The event did its job. The timeline didn't. That's not a data problem. That's a communication design problem. This update gives you the tools to fix it.”
If you're thinking about how this fits into a broader behavioral data strategy, it's worth reading about how B2B customer journey mapping is evolving in 2026. Custom events are one of the sharpest tools you have for capturing real behavioral signals, and this update makes those signals visible to everyone on your team.
If you want help auditing your existing custom events, setting up display templates that actually serve your sales and service teams, or building a behavioral event strategy from the ground up, let's talk. Book a strategy call with the Sidekick team and we'll show you exactly where your current event setup is leaving signal on the table.
Frequently Asked Questions
What is the Custom Event Timeline Display update in HubSpot?
It's a new step in HubSpot's custom event setup wizard that lets you control how an event appears on linked record timelines. You can write a header and subheader using token-based templates, choose which properties display on the expanded card, reorder those properties, or hide them entirely. It shipped June 8, 2026.
Which HubSpot hubs and tiers support custom event timeline display customization?
The feature is available on Marketing Hub, Sales Hub, Service Hub, Content Hub, and Data Hub, all at Professional and Enterprise tiers. Any user with custom event edit access can configure the timeline display settings in the event setup wizard.
How do I customize the header on a HubSpot custom event timeline card?
In the custom event setup wizard, go to step 4, Customize Timeline. Use the Insert Token dropdown to build a header template. Available tokens include the linked record's name, properties defined on the custom event, and any object properties added in step 3. A live preview updates as you build the template.
Can I hide properties on a custom event timeline card in HubSpot?
Yes. You can uncheck individual properties to remove them from the expanded card, drag remaining properties into your preferred order, or turn off the Show Properties toggle entirely so only the header and subheader appear. This is useful when your header and subheader already tell the full story of the event.
Does this update affect custom events sent via the HubSpot Events API?
Yes. Events sent from external systems via the HubSpot Events API are still custom events in HubSpot's data model. The timeline display customization applies to them as well, which means RevOps teams can now control how third-party behavioral data surfaces on HubSpot records without changing any API payloads.
Do I need to reconfigure my existing custom events to use the new timeline display settings?
Yes, existing events won't automatically get headers or reordered properties. You'll need to open each event, navigate to the Customize Timeline step, and configure the settings manually. Existing events will still fire and record data as before; this update only changes how they display on the record timeline.
