Show recap — Thursday, July 2, 2026

Another Orange Morning Recap: July 2, 2026

It was a two-host morning. Chris was out, so it was Casey Hawkins and Trisha Merriam carrying the show on the Thursday before a long weekend, which meant the update reading got split and the conversation got a little more room to wander. Fourth of July Eve energy, a farmer deep in her season, and seven updates on the board.

Here is what we got into: Google's new Performance Max image generator, campaigns finally holding leads and companies, pipeline rules arriving for contacts and companies, a deep dive on handing Breeze your own context, the last update standing on automatic meeting associations, and a look ahead to a midday conversation about when AI actually speeds you up.

A Two-Host Morning Before a Long Weekend

With Chris out, Casey did what she does when he is away and asked Trisha, behind his back, what she really thinks of the new AI-generated intro song. The verdict was warm. It is a two-minute bop that buys you a minute to get your life together before the clapping kicks in and tells you to lock in.

Trisha is a farmer, and this is deep in her season, so her weekend plans are mud and weeds. Casey related from the other direction, as the amateur: a wildflower garden that is starting to pay off, marigolds blooming from seeds she and her husband planted in the dark ahead of a week of rain, timed on purpose. It is a good reminder that some of the best results come from planting at the right moment and letting the conditions do the work, which, as it turned out, was a decent metaphor for a few of the day's updates.

Google's Performance Max Gets an Image Generator

Trisha pulled this one forward, though not out of love. She has never been thrilled with the results of a Performance Max campaign, and she has watched teams misread what the format is for, treating a firehose of low-intent audience as if it were qualified demand. So a HubSpot update that touches PMax got her attention for mixed reasons.

The update itself is a clear win. With Chris out, Casey took the part he usually reads: HubSpot now uses Google AI to auto-generate ad-ready images during Performance Max campaign creation. You enter a landing page URL and get landscape, square, and portrait variants back, with no manual sourcing or resizing, and you can regenerate if you want another pass.

Why it matters: Trisha used to hire freelancers to take one asset and spin it into twenty different sizes, so watching AI do that in under a minute lands as the boring-but-real kind of useful. The surprise was the reach. This is in private beta, but it is open to all HubSpot users rather than gated behind Marketing Enterprise, which is a better deal than either of them expected. Casey copied the link mid-segment to go request the beta, with one practical note: private beta windows can fill fast, so if the link is there, take it now rather than later.

For more details: Google Performance Max ad image generation private beta.

Campaigns Can Finally Hold Leads and Companies

Two related updates got grouped here, and they are the ones that got the room thinking. Leads are now a first-class associated object on campaigns, and companies can be associated to campaigns too. Both are in public beta for Marketing Hub Professional and Enterprise. Contacts and deals have been associatable for a while, so this is the rest of the picture arriving.

Trisha has a complicated history with campaigns, mostly because the reporting has felt thin. Her long-standing frustration is that attribution reports gave you contacts created and revenue associated but not much of what happened in the middle. The newer data visualization work in campaign reporting, plus these association types, is what has her considering campaigns again after writing them off.

The lead association is the more interesting of the two for reporting, and it was Casey who named why. Because a single contact can be tied to multiple leads if they show interest more than once, asking how many leads a campaign generated is a different and often better question than how many contacts it touched. Casey also walked the Salesforce parallel, which both she and Trisha know from integration work: Salesforce has campaign members with no clean one-to-one equivalent in HubSpot, and leads might serve as a workable proxy for teams that miss that experience. The open question they left hanging is whether the HubSpot campaign object will one day sync with the Salesforce campaign object directly.

Why it matters: For B2B and ABM teams working primarily in the Leads experience, this fills a real attribution gap. The company association is manual right now, and Trisha likes that for account-based work, because it lets you tell HubSpot which accounts you are targeting from the start rather than letting it guess.

For more details: Associate leads with a campaign public beta and associate companies with a campaign public beta.

Pipeline Rules Come to Contacts and Companies

Pipeline rules, already familiar from deals, tickets, leads, and custom objects, now reach contact and company lifecycle stages. You can control which stages a record is created in, whether stages can be skipped, and whether records can move backward. A broader enhancement rides along: for every object type with pipelines, admins can now set the default stage a record is created in. This is in public beta for Professional and Enterprise.

The naming broke a couple of brains in real time. Casey kept catching that these are really lifecycle-stage rules, since the lifecycle stages are the pipeline of a contact or company, and calling them pipeline rules makes the whole thing harder to hold in your head than it needs to be. Trisha agreed, and the shared conclusion was that lifecycle rules would have been the clearer name.

Why it matters: These are guardrails for data quality. Stopping records from skipping critical stages or landing in the wrong lifecycle phase is what keeps conversion rates and stage reporting trustworthy. And since not every company wants its records to start in the same place, the new default-stage control is the piece that makes that intentional instead of assumed.

For more details: Pipeline rules for contacts and companies public beta.

The Deep Dive: Handing Breeze Your Context

The update that turned into the day's deep dive was Context Home custom context, which adds a new section under the Breeze menu where you can type free-form text or upload files directly. Every user can add context to their own Context Home, and admins can set context at the portal level. It is live across all hubs and tiers, and Casey's take was that it is a real upgrade she is a little surprised took this long: a place to just hand Breeze the background it has been missing.

Casey walked through the Context section live. Alongside the brand kit and the identification and products fields, some pulled in automatically and some set by hand, the new custom area is where the odd-but-important stuff finally has a home. She and Nico Lafakis had been playing in a demo portal built on Beats by Dre, which made for a funny mismatch against the Value First framework also loaded in there, but the point came through: you can dump context in and set whether it is visible to everyone in the account or just to you.

To make it concrete, Casey had Breeze draft a context doc for Casey Co Marketing on the spot, describing the business and where she wants to take it, the kind of starting place she said not to overthink. The tie-in to earlier work was clear. She and Trisha ran an AI enablement training a few months back where the whole message was context, context, context, and this is HubSpot catching up to that. If you are moving from Claude or another tool into Breeze and it feels like HubSpot does not know you yet, ask the tool you already use to write a context doc and drop it in.

Casey was candid that she is still working her way into Breeze, defaulting to Claude or Hub Helper Harry out of habit more than doubt, and she named the friction anyone hits: an AI tool that can do something one week and not the next teaches you to go where you feel confident. Trisha is the bigger Breeze advocate of the two, still learning but glad to see upgrades like this one. The best use case of the segment landed on Trisha's own world. A flower business has hard seasonality, right down to what is in stock at a given moment, and a context doc that knows what is blooming and when could be a real content-marketing aid for anyone in that world.

For more details: Context Home custom context with free-form text and file uploads.

Automatic Associations for Meetings, the Last Update Standing

The last update of the morning, the one Casey called the last kid picked for the team, was a quiet fix that turns out to matter. Meetings created in HubSpot or synced into it now follow the automatic association rules you set, wherever the meeting originated. Before this, only meetings created directly in the CRM followed those rules, while scheduling-page and calendar-synced meetings fell back to a default. It is live across all hubs and tiers.

Why it matters: Casey had a real-time realization here. She had logged a meeting a few days earlier and watched it attach to old deals for no reason she could see, filed it under weird, and moved on. Reading the update, she put it together: the default behavior logs a meeting to the five most recently associated open deals, which explains the mystery and explains why bringing every meeting under your own rules is worth doing. The rules live in settings under objects, activities, and associations, and both hosts admitted it was their first time opening that screen, which is probably true for a lot of people.

For more details: Automatic associations for meetings.

When AI Speeds You Up, and When It Doesn't

The show closed on a look ahead to a midday conversation between Casey and Trisha about a feeling both of them know well: sometimes AI helps, and sometimes it just gets in the way. The frame they kept coming back to is that learning AI alongside a cohort of people in roughly the same place beats trying to keep up with the super users, whose output can be dazzling and also very far from where most people actually are. George's AI clone came up as the example. It is impressive, and it exists because he had years of video content to feed it, which most people do not have.

Trisha brought the best analogy. She was around when the mouse was invented, and her first reaction was that it slowed her down, because she already had ten fingers and a command line. She has come all the way around to wanting to talk to her tools conversationally, and that arc is exactly why the pair want to meet people where they are rather than expect a leap to the command line. Casey works next to Chris and his terminal often enough to know the leap is real. The invitation was open: come hang out, and they will meet you where you are.

The Rest of July 1's Updates

The show worked through all seven, including a terms-of-service notice in the Legal Center that is worth a read even though it is not the flashiest item on the board. Full breakdowns of all seven updates from July 1 are on the updates blog: HubSpot Updates: July 1, 2026.

The Sign-Off

Chris and Casey are planning to do the morning show tomorrow, Friday, July 3, covering the week ahead a little early before observing HubSpot's week of rest the following week. Have a great Thursday, and a great Fourth of July.

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.