CRM Analytics Rebrand: Our Third Name in Five Years

If you've been around Salesforce's analytics platform long enough, you've developed a reflex. Someone in a discovery call says "we want to use Wave" and you pause, do a quick mental calculation of when they last touched the platform, and gently update them. By this point in early 2023, we've done that correction so many times it's practically scripted.

The platform is now called CRM Analytics — CRMA if you're typing fast in Slack. That's the official name as of late 2022, and it's what we're using in all new SOWs, training materials, and client onboarding docs. But the naming history is worth documenting clearly, because it matters more than you'd think when you're managing an enterprise implementation.

The Full Lineage, For the Record

Let's just put it in one place, because we've never found a clean canonical version of this written down:

  1. Wave Analytics — the original name, back when this was a genuinely novel embedded analytics product inside the Salesforce ecosystem
  2. Einstein Analytics — rebranded as Salesforce leaned hard into the Einstein AI umbrella brand
  3. Tableau CRM — renamed after Salesforce acquired Tableau, which created its own set of confusion
  4. CRM Analytics — the current name, now official

Four names. Roughly five years of production use across our client base. If you've been with the platform since the Wave days, you've watched it get renamed more often than most people change jobs.

We want to be fair here: product rebrands happen. They're usually the result of legitimate strategic shifts, portfolio reorganization, or M&A activity, not someone just deciding the name needed refreshing. But four names in five years is a lot to absorb for practitioners, and it has real operational consequences.

Why the Tableau CRM Name Was Especially Disruptive

Of all the name changes, the Tableau CRM rename was the one that caused the most friction in our practice. The Einstein Analytics to Tableau CRM transition landed in a strange spot because it implied a closer relationship between this platform and Tableau Desktop/Tableau Server than actually existed at the product level.

We fielded questions constantly. "So is this just Tableau now?" No. "Can I use my Tableau prep flows here?" Not directly. "Does this replace Tableau in our org?" Almost certainly not.

The name created expectations that the product, at the time, didn't fully meet. We weren't blaming anyone — the acquisition was real, the integration roadmap was real, and the eventual vision of tighter Tableau integration made sense. But in the interim, the name was doing heavy lifting that the product hadn't yet caught up to. We spent a meaningful number of discovery and scoping hours just disambiguating the two platforms for clients who had both in their Salesforce contracts.

The flip side: some clients were genuinely excited because they associated the Tableau brand with serious, enterprise-grade analytics. That association helped us in a few deals. But it also meant that when those clients got into the actual CRMA development experience — SAQL queries, the dataflow editor, the recipe canvas — there was occasionally a "wait, this isn't what I expected" moment. Managing that gap became part of our standard onboarding process.

What CRM Analytics Actually Signals

The move to CRM Analytics in late 2022 reads, to us, as a deliberate step away from the Tableau association and back toward something that describes what the product actually does. It's analytics that lives natively in the CRM. That's accurate. That's what it's for.

The name also aligns the product more clearly with the broader Salesforce platform story rather than positioning it as an extension of an acquired product. Whether that's a permanent strategic stance or a setup for another shift down the road, we genuinely don't know. But as a descriptor of what clients are actually buying and deploying, CRM Analytics is more honest than some of its predecessors.

We'll take accurate over clever.

The Operational Consequences Nobody Talks About

Here's the part of the rebrand story that doesn't make it into release notes: every name change creates a paper trail problem.

Consider what lives inside an enterprise Salesforce org after three or four years of CRMA development:

  • SOW language referencing "Einstein Analytics dashboards"
  • User training documents titled "Tableau CRM for Sales"
  • Salesforce Help Articles bookmarked by your admin team using whatever name was current when they saved them
  • Internal wiki pages, Confluence docs, Jira ticket templates, Slack channel names
  • Job requisitions your HR team copied from somewhere in 2021 that say "Tableau CRM experience required"

None of this breaks anything technically. The platform itself doesn't care what name is on the door. But it creates low-grade organizational confusion that compounds over time. When a new admin joins and searches your internal wiki for "CRM Analytics," they might not find the documentation your previous admin wrote under the Einstein Analytics name. When your procurement team looks at renewal quotes, they're matching contract language against platform names that may have shifted.

Our standard advice now when we finish an implementation: do a documentation audit as part of the project close. Find every place the platform name appears in internal materials and standardize it. It's not glamorous work, but it saves real time later.

What We Tell New Clients

We've developed a fairly consistent story for clients who are new to the platform and need to understand why all this naming complexity exists. It goes roughly like this:

The platform has been renamed several times for reasons that mostly reflect Salesforce's evolving corporate strategy rather than changes to the product itself. The underlying technology has matured significantly over this period — the rename from Wave to Einstein Analytics to Tableau CRM to CRM Analytics tracks a genuine evolution in capability, not just cosmetic changes. But the names themselves have sometimes generated confusion that the product didn't deserve.

What you need to know practically:

  • If you're searching for documentation, technical content, or community answers, you may need to search under multiple names. "Einstein Analytics SAQL" and "CRM Analytics SAQL" will return related but different result sets. The older content under previous names is often still accurate and useful.
  • When you write internal documentation, pick CRM Analytics and stick to it. Introducing the historical names only when absolutely necessary (e.g., explaining why an old dashboard is named "EA Sales Performance").
  • Certifications on the Salesforce platform may still use or reference older naming conventions in some cases. Don't let that throw you off.
  • When talking to your Salesforce AE or support, "CRM Analytics" is the term to use. You may occasionally still hear the older names from people who've been around a while — that's fine, it's the same product.

We also tell clients that the naming history is actually a useful signal: this is a platform that has been iterated on, repositioned, and invested in over a sustained period. That's generally better than a product that hasn't moved. The frustration of keeping up with the names is a side effect of a platform that's been actively developed.

That's not spin — we genuinely believe it. But we also acknowledge that it's cold comfort when you're updating 40 pages of user training documentation for the third time.

Technical Documentation Implications

One practical thing we've started doing in our implementations: we add a brief naming history note at the top of our technical documentation templates. It reads something like:

This platform has been marketed under several names: Wave Analytics, Einstein Analytics, Tableau CRM, and (currently) CRM Analytics. All names refer to the same Salesforce native analytics platform. Technical documentation online may use any of these names.

It's a small thing, but it saves the "wait, what's the difference between Einstein Analytics and this?" conversation with every new team member who picks up the docs.

Similarly, when we're writing SAQL or building dataflow documentation, we're careful not to let platform naming bleed into technical vocabulary in ways that will age badly. The technical primitives — datasets, lenses, dashboards, recipes, dataflows — have been more stable than the platform name itself. We anchor our technical writing to those terms rather than to whatever the current brand happens to be.

On Stability Going Forward

We'll be honest: we're not entirely sure the CRM Analytics name will be the last one. Salesforce's product portfolio is large and continues to evolve. If there's another significant acquisition or strategic shift, we wouldn't be shocked to see the name change again.

What we've learned from managing clients through multiple rebrands is that the right posture is to build implementation practices that are somewhat name-agnostic. We document the technical layer carefully. We help clients build internal terminology that's based on what the product does for them ("our sales analytics platform," "the pipeline dashboard") rather than what Salesforce happens to call it this year. That way, a rename doesn't require a complete re-education effort.

We've also gotten more conservative about using brand names in deep technical contexts — in code comments, in field labels, in metadata API names — because those are the hardest things to change if the name shifts again. A dashboard named "CRMA_SalesPipeline_v2" is going to age better than one named after a specific brand era.

The Honest Bottom Line

Four names in five years is a lot. It has created real operational overhead for our practice and for our clients. Documentation maintenance, disambiguation conversations, job description drift, certification naming confusion — none of these are huge problems individually, but they add up.

At the same time, the platform itself has genuinely matured through this period. The product we're working with as CRM Analytics in early 2023 is substantially more capable than what Wave Analytics was when many of us started with it. The rebrand history is inseparable from that evolution story.

Our practical stance: use "CRM Analytics" consistently in everything you produce going forward, document the historical names once in a reference section for your team, and build your implementation practices in a way that doesn't depend too heavily on whatever the current brand name happens to be.

And when a client emails you asking about "their Wave instance," take a breath, smile a little, and send them the naming history link.

You've done it before. You'll do it again.