What is Salesforce CRM Analytics? Wave, Einstein Analytics, Tableau CRM, and CRMA, explained once

Salesforce CRM Analytics (CRMA) is Salesforce's native analytics platform: datasets, data prep recipes, the SAQL query language, and dashboards that live inside your Salesforce org and respect its security model. If you have heard the names Wave Analytics, Einstein Analytics, or Tableau CRM, you have heard about this same product. One platform, four names, twelve years.

The naming timeline

• 2014: Wave Analytics. Launched as Salesforce's cloud analytics tool, sometimes called Analytics Cloud.
• 2017: Einstein Analytics. Renamed to align with the Einstein AI branding as predictive features arrived.
• 2020: Tableau CRM. Renamed after Salesforce acquired Tableau, borrowing the stronger visualization brand.
• 2022: CRM Analytics. The current name. Salesforce repositioned it as the natively-built analytics layer for Salesforce data.

Nothing was migrated between those names. Your Wave-era datasets, dataflows, and dashboards carried forward through every rename. What did change, gradually and substantially, was the platform underneath: Recipes largely replaced dataflow JSON for data prep, Einstein Discovery brought model building, and the Agentforce era is now exposing CRMA datasets to AI agents.

CRM Analytics is not Tableau

This is the confusion the 2020 name caused, and it still costs companies money. Tableau is a separate visualization platform that Salesforce also owns. It connects to hundreds of data sources and lives outside your org. CRM Analytics lives inside Salesforce, queries Salesforce data natively, enforces row-level security through predicates, and writes back into Salesforce workflows.

Because they are different products, moving dashboards from Tableau into CRM Analytics is a real migration with real work in it: workbooks become dashboards, calculated fields become SAQL or recipe logic, and row-level security gets rebuilt as predicates. Moving from "Tableau CRM" to "CRM Analytics" is not a migration at all; that was a rename. Anyone selling you a "Tableau CRM to CRM Analytics migration" is charging you to move to the product you already own. What a Tableau CRM-era org may genuinely need is modernization: old dataflow JSON moved to Recipes where it belongs, security predicates rebuilt for how the business is organized now, and dashboards tuned against the current runtime.

What the platform is made of

• Datasets: columnar stores optimized for aggregation, loaded from Salesforce objects or external sources.
• Recipes (and legacy dataflows): the data prep layer that joins, transforms, and schedules refreshes.
• SAQL: the query language behind every dashboard step. Where the performance problems hide.
• Dashboards: JSON-defined pages of steps and widgets. Every step on a page fires on load, which is why undisciplined dashboards get slow.
• Einstein Discovery: model building on top of datasets, with all the leakage traps any ML system has.
• Security predicates: row-level access rules evaluated at query time.

Where implementations go wrong

After 150+ engagements across every vintage of the platform, the failure patterns repeat: dashboards accumulate dead steps that fire on every load, recipes silently drop rows through watermark and sync edge cases, security predicates written for a 2017 org chart break on every reorg, and Discovery models score high on leakage instead of signal. Each of those has a published deep-dive in our Insights archive.

If one specific dashboard is the pain point, the fastest diagnosis is a flat-fee teardown: send the dashboard JSON export, no org access needed, and get back a step-level audit with a prioritized fix list in 48 hours.