The Campaigns object already works the way HubSpot describes it — a parent container for an entire strategy and every asset in it — and it stays underused because almost everyone still hears the word "campaign" and thinks one email send.

Casey and Chris put the real problem in the open on the show: "The bigger problem this update runs into is the word campaign. Most people hear it and think email send. HubSpot uses it to mean a parent container holding an entire strategy and every asset in it, and that gap is why the object stays underused." That gap is exactly why campaign cloning mattered to Chris more than any other API update in this Hub. "What actually excites me here is campaign cloning," he said. "That is real work moving into the place where the assets already live." Marketing Studio is where that container actually gets built, and this run gave it the plumbing a daily-driver tool needs rather than headline features — copy-paste nodes and an onboarding tour, which Casey read as "Marketing Studio settling in and getting the usability polish a daily-driver tool needs." Even Marketing Control Center's sunset ties back to the same object: its capabilities are folding into Breeze Assistant rather than staying a separate destination, because, in Casey's words, "when updates come out of campaigns, and then you see teamwork moving the same direction, the natural question is why they are not built together." The show's standing take: the Campaigns object already works the way HubSpot describes it. Almost nobody is using it that way yet.