Most teams should start with standard Salesforce reports and dashboards, which are included with Salesforce and cover operational reporting on CRM data. Add CRM Analytics when you need deeper analysis and predictions inside Salesforce, on mostly Salesforce data. Choose Tableau when leaders need Salesforce blended with finance, marketing, product or warehouse data, or want one analytics platform across departments. In every case, agree on metric definitions before you pick the tool.
What are standard Salesforce reports and dashboards?
Standard reports and dashboards are the reporting tools built into every Salesforce org. They query live CRM records, respect each user's sharing access and need no separate license.
Admins and trained business users build reports from report types, then place charts, tables and metrics on dashboards. Features such as joined reports, dynamic dashboards, subscriptions and reporting snapshots stretch them further than many teams realize. Their limits show up with data that lives outside Salesforce, long historical trends and complex calculations across many objects.
Our guide to Salesforce dashboards leadership will actually use, linked below, covers how to get the most from them. This article focuses on when to go beyond them.
What is CRM Analytics?
CRM Analytics is Salesforce's native analytics layer, previously sold as Tableau CRM and before that Einstein Analytics. It runs inside Salesforce and is licensed separately from your core CRM licenses.
It syncs Salesforce data, and data from some external connectors, into datasets built for fast analysis. Recipes and data flows prepare and combine that data. Dashboards and lenses can then be embedded on Lightning record pages and app pages, so insight appears where reps and managers already work. Its predictive features, historically branded Einstein Discovery, can score records and suggest next steps.
Despite the old name, CRM Analytics is a different product from Tableau. It uses its own data model, query language and dashboard designer.
What are Tableau, Tableau Cloud and Tableau Next?
Tableau is Salesforce's enterprise business intelligence platform for analyzing data from almost any source. It is licensed separately from Salesforce and is not limited to CRM data.
Authors build workbooks in Tableau Desktop or in the browser, and publish them to Tableau Cloud, which Salesforce hosts, or to a self-managed Tableau Server. Published, certified data sources let many dashboards share one definition of each metric. Tableau Pulse delivers key metrics to people in email, Slack, Microsoft Teams or the browser, with automated explanations of what changed.
Tableau Next is the newer offering built on Salesforce's data platform, Data 360. It centers on a semantic layer, Tableau Semantics, that defines metrics once so people and AI agents interpret data consistently. It is aimed at conversational and agent-driven analytics, and it sits alongside Tableau Cloud rather than replacing it. Salesforce's Core, Advanced and Max editions now include embedded analytics built on Tableau Next, and the Tableau+ bundle combines Tableau Cloud and Tableau Next, so confirm with your account team what you already own.
How do the three options compare?
The short answer: reports serve daily CRM work, CRM Analytics serves deeper analysis inside Salesforce, and Tableau serves analysis across many systems.
| Factor | Standard reports and dashboards | CRM Analytics | Tableau |
|---|---|---|---|
| Data sources | Records in your Salesforce org | Mainly Salesforce data, plus synced external sources through connectors | Salesforce, warehouses, databases, files and many other applications |
| Who builds it | Admins and trained business users | Admins or developers with CRM Analytics skills | Analysts and BI developers, with self-service authoring for trained users |
| Data volume and blending | Live queries on current records; limited joins and history | Prepared datasets built for larger volumes and combined CRM data | Large volumes and blending across systems, often through a warehouse or Data 360 |
| Embedding in Salesforce | Native everywhere in the org | Native components on record, app and home pages | Embeddable through a Lightning component; usually opened in Tableau itself |
| AI and predictive features | Limited; mostly summaries and formulas | Predictive scoring and recommendations on CRM data | Pulse metric insights, AI-assisted authoring and, with Tableau Next, agent-driven analytics |
| Licensing structure | Included with Salesforce user licenses | Separate add-on user licenses, with editions that differ in features | Separate product; role-based licenses for creators, explorers and viewers |
| Admin effort | Low; part of normal Salesforce administration | Moderate; data sync, recipes, security and dashboard upkeep | Higher; data sources, refresh schedules, permissions and content governance |
When are native Salesforce reports enough?
Native reports are enough when your questions are about records that live in Salesforce and people act on them day to day. That covers most pipeline, activity, case and campaign reporting.
- Your leadership metrics can be calculated from Salesforce objects alone.
- Current snapshots matter more than multi-year trends, or reporting snapshots cover the history you need.
- Users want lists and simple charts they can act on from the same screen.
- Nobody on the team has capacity to maintain a second analytics platform.
If leaders distrust the current dashboards, a new tool rarely fixes that. Poor definitions and incomplete records will look the same in any product.
When does CRM Analytics fit?
CRM Analytics fits when the data is mostly Salesforce data, but the analysis has outgrown standard reports. It is strongest when insight must appear inside Salesforce, next to the record someone is working.
- Managers need trends, cohorts or calculations across several objects that joined reports handle poorly.
- Sales or service teams would act on predictive scores shown on the record page.
- You want analytics inside Salesforce apps without sending users to another tool.
- Some external data is needed, but Salesforce remains the center of the analysis.
It is a weaker fit when most of the data lives elsewhere. It also needs someone who knows its data model, so plan for that skill before you buy.
When does Tableau fit?
Tableau fits when the answer depends on data from several systems, or when the company wants one governed analytics platform across departments. Salesforce becomes one important source among many.
- Leadership questions join Salesforce with ERP, finance, marketing, support or product-usage data.
- You have, or plan, a data warehouse that should feed reporting.
- Analysts need to explore, build calculations and publish their own views.
- Customers or partners need secure analytics, each seeing only their own slice.
- Data volumes or history exceed what native reports handle comfortably.
Tableau is a poor fit when a few people need a few static monthly reports. Someone has to own data sources, refreshes and content, or the environment decays.
How does Data 360 relate to this decision?
Data 360, formerly Data Cloud, unifies customer data from many systems into profiles Salesforce can use. It is a data platform, not a reporting tool, but it can feed analytics.
Tableau Next is built on Data 360, and Tableau can also connect to it. If your data is scattered and has never been matched or unified, deal with that first, in Data 360 or a warehouse. Our guide to when you need Data Cloud, linked below, explains the prerequisites.
How should a Tableau and Salesforce project run?
A Tableau project with Salesforce succeeds when metric definitions and data sources are settled before anyone designs a dashboard. The build itself is usually the easy part.
- Start with decisions and metric definitions. List the recurring decisions leaders make, then write down how each metric is calculated and who owns it.
- Map the data sources. Decide which Salesforce objects and which other systems feed each metric, and whether to connect directly or through a warehouse or Data 360.
- Choose hosting and identity. Pick Tableau Cloud or Tableau Server, connect single sign-on and set up projects that mirror your departments.
- Model, secure and certify data. Build published data sources with friendly field names, apply row-level security and certify the ones people should trust.
- Prototype with real users. Share drafts early, reconcile totals against Salesforce with the data owner and watch what people still export to spreadsheets.
- Govern and drive adoption. Separate sandbox and production content, train authors and viewers, name champions and retire views nobody opens.
What mistakes should you avoid?
The most common mistakes are buying a tool before defining the questions, and underestimating the upkeep a second platform needs.
- Buying Tableau or CRM Analytics to fix distrust that really comes from bad data or disputed definitions.
- Pointing workbooks straight at dozens of raw Salesforce objects, which produces slow queries and conflicting calculations.
- Building one dashboard for executives, managers and analysts at once, so it serves none of them.
- Scheduling every extract refresh for the same early-morning slot, then not noticing when jobs fail.
- Buying authoring licenses for everyone when most people only need to view.
- Launching without an owner, so personal copies and duplicate reports pile up.
What does this look like in practice?
Three of our analytics projects show the pattern: native tools reached a limit, and the fix was data architecture first, dashboards second.
A home-improvement company ran a heavily customized Salesforce org. Native dashboards could not track KPIs across product lines, segments and lead sources, and data was spread across Salesforce, a call-center AI tool and MailChimp. We built secure Tableau connections to custom objects for prospects, lead sources, appointments and sales. Dashboards covered cost per lead, a sales-lead index and conversion by product line and segment. The company could identify its top-performing marketing channels across three product lines and multiple markets.
A political-advocacy agency had bought Tableau two years earlier and never connected its fundraising data. Rather than brittle custom APIs, we used Marketing Cloud Intelligence as the central hub, with a native connector to Tableau. The agency moved to Tableau Plus with AI, 23 user licenses and role-based client access. It went from an unusable system to a scalable foundation and a client-facing donor-data offering.
A SaaS company, in this case running HubSpot rather than Salesforce, shows the same need from another CRM. Its team pulled numbers by hand from HubSpot, Zendesk, Maxio and SQL before meetings. Tableau Cloud with a daily refresh replaced those spreadsheets with interactive pipeline dashboards, and gave a foundation for adding the other sources.
If you are weighing these options, our Salesforce optimization team can review your reporting, definitions and data before you commit to a new license.
