What This Update Actually Is
HubSpot already let admins configure auto-association defaults for activity logging on standard objects like Contacts and Companies. This update extends that same control to three additional objects: Contracts, Orders, and Marketing Events.
In plain terms: when a task, call, email, or meeting is logged on a record, HubSpot can now automatically associate that activity with related Contracts, Orders, or Marketing Events too. Admins control the default logic. No more telling sales reps to manually cross-associate. No more building workarounds in workflows to copy activity data across objects.
The configuration lives under Settings > Data Management > Objects > Activities > Associations tab. You pick the source object, pick the activity type, and set the default logging behavior for each associated object you want covered.
Why HubSpot Shipped This
Here's the pattern we see constantly in portals: a rep logs a call on a Contact. That contact is tied to an Order. But the Order record shows zero activity history. Someone pulls a report on Order engagement and the data looks empty, even though the team has been actively working it.
That gap isn't a rep failure. It's a defaults problem. HubSpot's original auto-association feature solved this for Contacts, Companies, and Deals. But as HubSpot expanded its object model with Contracts, Orders, and Marketing Events, those newer objects didn't inherit the same logging intelligence. Admins had to rely on workflows or manual rep behavior to keep those records accurate.
The internal frustration is real. Humans running ops at growing companies spend hours chasing data integrity problems that should be handled at the system level. This update pushes that responsibility where it belongs: into the settings, configured once by an admin, enforced automatically afterward.
How to Use It Step by Step
- Click the Settings icon in the main HubSpot navigation bar.
- Navigate to Data Management > Objects > Activities.
- Click the Associations tab.
- Use the first dropdown to select the source object where the activity gets logged. For example, choose Contact if the activity is being logged on a contact record.
- Select the Activity type you're configuring. Options include tasks, calls, emails, meetings, and notes depending on the source object.
- Under "Log activity to," open the dropdown for each associated object you want to update. You'll now see Contracts, Orders, and Marketing Events listed here alongside the existing options.
- Look for the orange "Default" tag. That tag marks HubSpot's current out-of-the-box behavior. Change only what differs from how your team actually works.
- Click Save. The new default applies to all future activity logging for that object and activity type combination.
One honest caveat: availability depends on whether the object is available to your portal. If you don't see Contracts or Orders in the dropdown, check your hub configuration and tier access before assuming the feature is broken.
What It Touches in Your HubSpot Strategy
This update is quiet. It lives in settings, not in a flashy new tool. But it ripples into more places than most admins realize at first glance.
Reporting is the most immediate win. If your team runs activity-based reports tied to Contracts or Orders (things like calls logged per contract stage or tasks completed per open order), those reports will finally reflect complete data instead of whatever reps remembered to manually associate.
Key Takeaway
Cleaner auto-association defaults mean your activity reports on Contracts and Orders stop undercounting. You don't need to fix the report. You need to fix the default, and this update lets you do exactly that.
Marketing Events is the most interesting addition here. Humans running event-heavy marketing strategies, especially those using HubSpot's Marketing Events object to track webinars, in-person events, or partner activations, have had a persistent visibility gap. Follow-up tasks and post-event calls logged on a contact didn't automatically connect to the event record. Now they can.
For commerce-forward portals using Orders, this also supports better alignment between the sales motion and the post-sale fulfillment record. A call logged on a Contact while an Order is open can now roll up to that Order automatically, giving ops a cleaner picture of what happened between purchase and delivery.
If you're working inside a more complex HubSpot setup, this pairs well with pipeline rules and data governance. We covered the
CRM pipeline rules public API update recently, and the two updates complement each other. Better pipeline rules govern how records move. Better auto-association defaults govern what data lives on those records as they move.
Key Takeaway
Auto-association isn't just a data hygiene feature. It's a reporting foundation. Every downstream report, workflow trigger, and AI summary that touches these objects gets more accurate input when the association defaults are configured correctly.
One more ripple worth noting: if you use
HubSpot's QuickBooks Online or Xero sync and you have Orders flowing between systems, cleaner activity association on the HubSpot side means the record that syncs outbound carries a more complete engagement history. Less reconciliation on the finance side.
Who Should Care Most
This update matters most to a specific set of roles and portal profiles. Here's the honest breakdown:
- HubSpot admins and RevOps leads who own data governance will want to audit their current auto-association settings immediately. The new objects are available but they aren't pre-configured to match your business logic.
- Sales ops and deal desk teams running Contracts as a formal object will see the biggest immediate gain. Activity history on contracts finally becomes trustworthy without training reps to remember manual steps.
- E-commerce and commerce-enabled portals using Orders will benefit from cleaner post-sale activity records, especially if customer success or account management teams log calls and tasks during fulfillment.
- Event marketers and demand gen teams using the Marketing Events object can now tie follow-up activity back to the event record automatically, making attribution and engagement reporting on events far more useful.
- Business owners at companies with 10 to 200 employees who manage their own HubSpot portal should add a 30-minute review of their activity association settings to their quarterly portal audit. This is a set-it-and-forget-it improvement with lasting impact.
George's Take
I've audited a lot of portals where the reporting on newer objects like Contracts and Orders looked completely flat, not because the team wasn't active, but because the defaults were never configured to capture the activity that was happening. This update closes one of those quiet data gaps that nobody notices until they're trying to build a board-level report and the numbers don't match reality. The fix takes maybe 15 minutes in settings. The payoff is every downstream report, every AI summary, every workflow trigger on those objects getting cleaner data from this day forward. That's the kind of foundational work that lets everything else in your portal actually flourish.
“The fix takes 15 minutes in settings. The payoff is every downstream report, AI summary, and workflow trigger on those objects getting cleaner data from this day forward.”
If you're running Contracts and Orders as core objects in your HubSpot setup, it's also worth reviewing how they fit into your broader Revenue Hub architecture. Our complete HubSpot Revenue Hub guide walks through exactly how these objects connect and how to structure them for scale.
If you'd like a second set of eyes on your current activity association settings or a full portal data audit, that's exactly the kind of work the Sidekick team does every week. Book a strategy call at sidekickstrategies.com and let's look at it together.
Frequently Asked Questions
What objects now support auto-association for activity logging in HubSpot?
As of July 24, 2026, HubSpot supports configurable auto-association defaults for Contracts, Orders, and Marketing Events in addition to the existing standard objects like Contacts, Companies, and Deals. Admins configure the defaults under Settings > Data Management > Objects > Activities > Associations.
Where do I configure auto-association settings for activities in HubSpot?
Go to the Settings icon in the main navigation, then Data Management > Objects > Activities > Associations tab. Select the source object, choose the activity type, and set the default logging behavior for each associated object. Look for the orange Default tag to see HubSpot's out-of-the-box settings before you change anything.
Does auto-association for activities apply to existing records or only new ones?
Auto-association default changes apply to future activity logging, not retroactively to existing activity records. If you need historical activity linked to Contracts, Orders, or Marketing Events, you'll need to manually associate older records or use a workflow to bulk-update associations on existing data.
Who has access to auto-association for activities on the new objects?
This feature is available to all HubSpot hubs and tiers. However, the specific objects available in the settings dropdown depend on which objects are active in your portal. If you don't see Contracts or Orders in the list, confirm those objects are enabled in your HubSpot account first.
Why does auto-association matter for HubSpot reporting?
When activities aren't associated with the right objects by default, reports on those objects show incomplete engagement data. Configuring auto-association ensures that calls, tasks, emails, and meetings logged on related records are captured on Contracts, Orders, and Marketing Events automatically, making reports accurate without extra manual steps.
Does this update affect HubSpot Marketing Events specifically?
Yes. Marketing Events can now be configured to auto-receive associated activities. This means follow-up calls, emails, or tasks logged on a Contact after an event can automatically link back to the Marketing Event record, giving teams a cleaner view of post-event engagement and attribution without manual cross-association.
