Read the recap

Back to Hubsessed Office Hours: Reporting & Dashboards
Hubsessed Office Hours: Reporting & Dashboards

Hubsessed Office Hours - Reporting and Dashboards - Oct 21, 2026

  • Joshua OakesHost
  • Madelyn DonovanHost

Wednesday, October 21, 2026

Sign in to watch the full replay and read the transcript.

Sign inSubscribe free
SharePost on X (opens in a new tab)Share on LinkedIn (opens in a new tab)

Lorelei Uribe brought a reporting question: how to make email engagement rates by cohort client-ready and usable outside HubSpot. Joshua Oakes, joined by Chris Carolan, covered dashboard filter links, Breeze, data sets synced to Google Sheets and customer portals.

Clips from this session

Key takeaways

A client-ready report has to look good and work outside HubSpot; that is a different question from whether the data can be pulled.

A text widget on a dashboard can hold links to preset filter states, a menu that removes filter friction; it gets hard to maintain across many companies or parameters.

Breeze can do the final mile of math between a data layer and a presentation layer, combining figures the underlying reports don't carry, especially inside a Breeze project with instructions and references.

If a team insists on its copy-and-paste spreadsheet, that is an adoption problem, not a reporting problem: let the most AI-forward person try the new way and champion it.

Showing AI work on screen while answering a question, in a no-pressure way, lets the idea become the team's own.

A data set can turn yes or no into one or zero, so unique click rates become simple percentages, and a nightly sync to Google Sheets removes the copy and paste.

Out of the box, "customer portal" in HubSpot means tickets; tickets are for help desk work, not success management.

Any portal, out of the box or built, depends on a data model that works and a process people have adopted, including a process that no longer waits for month-end cleanup.

Rates are aggregates of other records' activity, which makes them hard to show in an object-based portal; AI that can see the data changes what is possible.

Asking AI for an outcome rather than starting from an object changes the frame away from custom code.

Questions answered

  1. 0:00:32How do we make email engagement reporting by cohort look good, and usable outside HubSpot?Question
  2. 0:07:26A dashboard menu: preset filter links in a text widgetTopic
  3. 0:09:22Two paths: bridge what you have built, or let Breeze generate the reportTopic
  4. 0:11:44How do I bring two reports together to show the percentage of delivered emails that were clicked?Question
  5. 0:13:52Not a reporting problem: an adoption problemTopic
  6. 0:15:52It has to be their idea: showing Breeze on screen while you answerTopic
  7. 0:18:54Fixing hand-keyed spreadsheet reporting with a data set in HubSpotTopic
  8. 0:23:20Syncing the data set to Google Sheets so nobody copies and pastesTopic
  9. 0:25:01Pulling data out of HubSpot, and reports as exhaustTopic
  10. 0:26:33Could the report be available directly in a portal hosted by HubSpot, for the stakeholders?Question
  11. 0:32:45What "customer portal" means out of the box in HubSpot, and why tickets are not success managementTopic
  12. 0:35:19A first look at setting up a customer success spaceTopic
  13. 0:40:47The key to any portal is the data model, and a process people have adoptedTopic
  14. 0:43:23Rates in an object-based portal: a black hole, unless AI is an optionTopic
  15. 0:48:19When AI says you need custom code, and what is already solved in the UITopic
  16. 0:50:42Describe your dream app: the Breeze builderTopic
  17. 0:54:22When will the new workflow builder get a delay based on a property?Question
  18. 1:00:07Start with the outcome, not the objectTopic

Related episodes