When you combine multiple HubSpot dashboards, the Y-axis often defaults to distinct count instead of your intended metric aggregation. This happens because HubSpot can’t properly interpret conflicting field types or aggregation rules from different dashboard sources.
Here’s how to take control of your metric calculations and eliminate the distinct count issue entirely.
Control aggregation logic with spreadsheet-based data management
CoefficientHubSpotHubSpotThe distinct count problem occurs becauseallows you to import the raw data from eachobject that feeds your original dashboards, then apply your own aggregation logic. Instead of lettingguess at the calculation method, you define exactly how each metric should be calculated.
How to make it work
Step 1. Import raw data from all dashboard sources.
Use Coefficient’s HubSpot integration to import the underlying data from each object (contacts, deals, activities) that feeds your original dashboards. Select only the custom fields you need for your calculations to keep your dataset clean and focused.
Step 2. Create calculated columns with proper aggregation.
Build calculated columns in your spreadsheet that define exactly how each metric should be aggregated. For example, if you want total lead conversions, use SUM functions instead of letting HubSpot default to distinct count. Use COUNTIFS for unique record counts and AVERAGE for rate calculations.
Step 3. Standardize metric definitions across sources.
Create consistent field definitions that work across all your imported data sources. If one dashboard counts “qualified leads” differently than another, build a unified definition using IF statements and logical operators to ensure consistent calculations.
Step 4. Set up automated refreshes.
Schedule your imports to refresh automatically (hourly, daily, or weekly) so your properly calculated metrics stay current as new data flows into HubSpot. This ensures your aggregation logic continues working without manual intervention.
Get accurate dashboard metrics every time
Start buildingTaking control of your aggregation logic eliminates the distinct count issue because you’re defining the calculation method directly.properly aggregated dashboard metrics that show actual values instead of confusing distinct counts.