Assess CRM Analytics (Tableau CRM) in an org

Overview

Wave, Einstein Analytics, Tableau CRM and CRM Analytics are four names for one product. The metadata types are still named Wave*. The CRM Analytics page reads those types from your last sync. It shows you what the org uses, how the data flows, what is unhealthy, and what to keep, fix or retire.

Open it from the sidebar under Overview → Org. CRM Analytics.

Before you start

• The org must have been synced since CRM Analytics types were added to MetaLens360. If it hasn't, the page tells you so instead of showing zeros.
• Any signed-in workspace member can read the page.
• Analyze this asset, the assessment narrative and Ask about it need an AI provider. Inventory, lineage and health work without one.
• Refresh runtime data and Deep dataset scan call the org live, so the org's connection must be working.

Steps

1. Choose the org from the Org picker.
2. Move through the tabs from left to right. Each one answers a single question:
   • Overview: what this org uses. Click any type to open its inventory.
   • Architecture: the shape of the implementation and where the load sits.
   • Sources & Targets: where data comes from and where it lands, including external systems.
   • Assets: every asset in the index. Open one and click Analyze this asset for an AI summary.
   • Recipes, Fields and KPIs: pipelines, field usage and a KPI dictionary read from dashboard steps.
   • Lineage: what feeds an asset, what it feeds, and what breaks if it changes.
   • Health: a weighted score with ranked findings.
   • Disposition: a recommendation for each asset: Keep, Fix, Consolidate, Retire, Retire (unverified) or Build.
   • Roadmap: what to do next, in order.
   • Assessment: a full report generated from the metadata pull.
   • Intelligence: ask questions in Ask about it.
3. On Health, click Refresh runtime data to pull job failures, runtimes and usage. Click Deep dataset scan to examine datasets in detail.
4. On Assessment, export the results with Download Word, Findings CSV, Disposition CSV or Roadmap CSV.

How the health score is weighted:

If every rule in a category was skipped, that category shows n/a, not 100. The overall score is then weighted across the categories that were actually scored.

Example

Priya is asked whether acme-prod can retire half its dashboards. On Lineage, she confirms that two "unused" dashboards share a dataset with the sales leadership dashboard. On Disposition, several assets are marked Retire (unverified). That label means they look unused, but usage wasn't confirmed. She clicks Refresh runtime data, re-checks the list, and exports Disposition CSV for ticket ACME-142.

FAQs

Does "Retire (unverified)" mean I can delete it?

No. It means the asset looks unused, but usage data couldn't confirm that. Don't act on it alone. Refresh runtime data first.

What does "Grounded in:" mean under an answer?

It lists the recipes, datasets or dashboards the answer was built from. Answers come from the dependency graph, not from general knowledge. Name a specific asset in your question for the most grounded answer.

Troubleshooting

"Nobody has looked yet"

This message means the org hasn't been synced since CRM Analytics types were added. It isn't a finding of zero assets. Run a sync for the org from Sync Center, and the page will fill in. See Run your first sync.

The health score shows "—" or a category shows n/a

Runtime data hasn't been fetched, or every rule in that category was skipped. Click Refresh runtime data. If that fails, check the org's connection in Connections.

Assets show "?" instead of a count

MetaLens360 couldn't parse that asset's body, so its dependencies are unknown. Re-sync the org. If the asset still can't be read, it may use a format MetaLens360 doesn't parse yet.

Related articles

• Run your first sync
• Selective sync and force full resync
• Configure AI providers
• Pages show no data