We've implemented a customer health score using the new beta feature and would like to visualize it in a HubSpot dashboard with the following insights:
Average health score over time
Health score trends by industry
Biggest changes in the past month (both increases and decreases at the customer level to identify risks and successes)
Key drivers behind these changes (i.e., which underlying score components changed)
I understand the data is available in the CS space, but I’m running into limitations extracting it into HubSpot reports — specifically around accessing timestamps in the reporting area.
Would it be possible to access this data outside the CS space, or is there another way you'd recommend?
Yeah, ran into the same thing when we rolled out health scores. Right now, the built-in reporting is limited, you can’t easily get historical trends or component-level drilldowns directly in dashboards. We ended up exporting the health data via API (there's a beta endpoint for score snapshots if you request access) and pushed it into a data warehouse. From there, we built visualizations in Looker Studio.
Not ideal, but it gave us full control over time-based comparisons and score drivers. If you’re sticking to native tools, you might try logging component changes as custom properties and using workflows to track deltas, but that’s more of a workaround than a fix.
HubSpot’s native reporting definitely isn't there yet to visualize customer health trends over time and understanding what’s driving those changes.
We have a lot of users leveraging Coefficient's certified 2-way sync between HubSpot and Google Sheets or Excel to support CS reporting.
You can use Coefficient to:
Pull all customer health data into a spreadsheet, including the overall score, component scores, industry, and customer info. You can even take snapshots of your data to timestamp items.
Set your data imports on a refresh schedule
From there, you can:
Calculate average health score over time
Trend scores by industry or customer
Use formulas or filters to highlight big score changes over the past 30 days (both increases and decreases)
Identify which components changed by comparing current vs. past values
If you need help with the spreadsheet logic, Coefficient’s AI assistant can generate the formulas and visualizations for you automatically, so you’re not starting from scratch.
Then, you have a couple of options for visualizations depending on where you want stakeholders to see these insights:
Option 1: Visualize directly inside HubSpot
Build your dashboards in Google Sheets
Use Google’s “Publish to Web” function to generate a live chart
Use HubSpot’s “Add Other Content” → “Other Content” option to embed the live chart right into your HubSpot dashboard
This gives you a live, auto-refreshing customer health dashboard inside HubSpot—no native reporting workarounds required. I recently created a video on how this works if you'd like me to share.
Option 2: Visualize in Looker Studio
HubSpot doesn’t have a native Looker Studio connector, which is why @TSburv needs to push data to their data warehouse first
But Looker Studio does have a free Google Sheets connector
So just pull your HubSpot data into Sheets using Coefficient, then connect that Sheet to Looker Studio
In short: with Coefficient, you can build powerful customer health dashboards, auto-refresh them, and embed them wherever your team works—whether that’s inside HubSpot or in Looker Studio.
I also recently created this video about how you can use GPT as well to feed summarized detail of the health score back to HubSpot using Coefficient as well.
Yeah, ran into the same thing when we rolled out health scores. Right now, the built-in reporting is limited, you can’t easily get historical trends or component-level drilldowns directly in dashboards. We ended up exporting the health data via API (there's a beta endpoint for score snapshots if you request access) and pushed it into a data warehouse. From there, we built visualizations in Looker Studio.
Not ideal, but it gave us full control over time-based comparisons and score drivers. If you’re sticking to native tools, you might try logging component changes as custom properties and using workflows to track deltas, but that’s more of a workaround than a fix.