Looker Studio CRM Dashboard Data Does Not Match the CRM: What to Check
When a Looker Studio CRM dashboard does not match the CRM, the dashboard total for leads, opportunities or pipeline value differs from the CRM source. The cause is usually the connector, the filters, the date fields, duplicate records or data freshness. Trace the data from the CRM record through the connector to the dashboard metric to find where the value changes.
Table of Contents
- 01.The CRM data flow you are debugging
- 02.What to check first
- 03.The date field and the filter set
- 04.Pipeline stages and lead status
- 05.Duplicate records and the connector
- 06.Data freshness and calculated fields
- 07.How to test the fix
- 08.How to validate the final result
The CRM data flow you are debugging
CRM data in Looker Studio flows from the CRM record, through a connector, into a data source, then into a dashboard metric. The value can change at any of those steps. A dashboard total that differs from the CRM is usually correct for a wrong configuration, so the goal is to find which step changed the value.
| Step | What can change | How to check |
|---|---|---|
| CRM record | Record exists but is filtered out | Open the record in the CRM directly |
| Connector | Connector misses or duplicates records | Check connector sync and field mapping |
| Date field | Wrong date field filters records | Confirm which date field the dashboard uses |
| Filters | Dashboard filters exclude records | Remove filters and compare |
| Data freshness | Dashboard lags the CRM | Check the connector refresh setting |
What to check first
- Open the CRM directly and confirm the record count for the same period and filter.
- Confirm which date field the dashboard uses, created date, closed date or similar.
- Remove dashboard filters and compare the unfiltered total with the CRM.
- Check the connector sync status and data freshness setting.
- Look for duplicate records in the connector output that inflate the total.
The date field and the filter set
CRM dashboards usually filter by a date field, such as the created date or the closed date. If the dashboard uses a different date field than the CRM view you compare against, the totals differ. Confirm which date field the dashboard filters on and compare the same field in the CRM. Pipeline value and opportunity counts are especially sensitive to the date field choice.
Pipeline stages and lead status
A dashboard that counts opportunities by pipeline stage can differ from the CRM if the stage definitions do not match. The connector pulls the stage as it exists in the CRM, but the dashboard may group or filter stages differently. Confirm the stage mapping between the connector and the dashboard. A won count can differ if the dashboard includes a stage the CRM view excludes.
Duplicate records and the connector
A connector can duplicate records if the sync logic creates multiple rows for one CRM record, or if the CRM itself has duplicate contacts. Duplicate records inflate the dashboard total. Check the connector output for duplicate IDs. If the CRM has duplicate records, the dashboard correctly counts them, and the fix is in the CRM, not the dashboard. CRM duplicate problems are covered in existing CRM duplicate lead guides.
Data freshness and calculated fields
The connector caches data based on its refresh setting. A dashboard can lag the CRM by the freshness window. Check the refresh setting and force a sync if needed. Calculated fields in the dashboard, such as a weighted pipeline value, can also differ from the CRM if the calculation logic does not match. Confirm any calculated metric matches the CRM definition.
How to test the fix
- 1.Confirm the CRM record count for the same date field and filter set.
- 2.Remove dashboard filters and compare the unfiltered total.
- 3.Check the connector output for duplicate records.
- 4.Force a connector sync and confirm the dashboard updates.
How to validate the final result
The dashboard matches the CRM when the total agrees for the same date field, filter set and freshness window, and no duplicate records inflate the count. If the dashboard is correct but the CRM has duplicates, the fix is in the CRM. A full validation process is covered in the guide on Looker Studio dashboard audit checklist.
Frequently Asked Questions
Why does my Looker Studio CRM dashboard show more leads than the CRM?
The connector may be duplicating records, or the CRM itself has duplicate contacts. Check the connector output for duplicate IDs. If the CRM has duplicates, the dashboard correctly counts them and the fix is in the CRM, not the dashboard.
Why does my pipeline value not match the CRM?
Confirm the date field the dashboard filters on, the pipeline stage mapping and any calculated field such as a weighted value. A dashboard using a different date field or stage set than the CRM view will show a different total.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Looker Studio Dashboard Audit Checklist: How to Validate Every Important Metric
A complete audit checks data sources, authentication, date ranges, dimensions, metrics, filters, calculations, blended data and the final totals against the source platforms. Work through each layer in order.
Looker Studio Charts Showing Incorrect Totals: How to Audit the Data
A wrong total can come from the source data, aggregation, blending, a calculation or a filter. Trace the value through each layer to find which one introduced the wrong number before changing the chart.
Looker Studio Metrics Are Duplicated: How to Find the Cause
Duplicated metrics usually come from blended joins, duplicate source rows, aggregation or multiple sources pulling the same metric. This is a reporting problem, not a duplicate conversion tracking problem.