Lens Explorer
Lens Explorer is the interactive data-exploration tool inside Salesforce CRM Analytics (formerly Tableau CRM, originally Einstein Analytics, originally Wave Analytics).
Definition
Lens Explorer is the interactive data-exploration tool inside Salesforce CRM Analytics (formerly Tableau CRM, originally Einstein Analytics, originally Wave Analytics). A lens is an ad-hoc query and visualization built against a single dataset. The Lens Explorer is the no-code interface where an analyst drops fields onto chart shelves, filters records, groups results, and drills into subsets. The chart you see is just a view of a query the platform builds for you in the background.
Analysts reach for the Lens Explorer to answer one question at a time: revenue by region, conversion rate by source, churn by tenure. A lens can be saved and reused, clipped onto a dashboard, exported, or thrown away after a quick look. Lenses are also the building blocks of CRM Analytics dashboards, so most dashboard work starts as exploration in a lens. Salesforce has steered the broader analytics story toward Tableau, but the Lens Explorer is still the native exploration surface for orgs running CRM Analytics.
How the Lens Explorer turns clicks into queries
What a lens actually stores
A lens is a saved query plus a visualization configuration aimed at one dataset. It records the query the platform generated, the chart type you chose, and the bindings between fields and chart shelves. Open the lens later and CRM Analytics re-runs the query, so the chart reflects current data rather than a frozen snapshot. That live behavior is the difference between a lens and an exported image. A lens is the smallest reusable unit of analytics in the product. You build one to answer a question, then either keep it as a standalone exploration asset or fold it into a dashboard. Because the lens points at a single dataset, its scope is bounded by what that dataset contains and how it was shaped. If a field is not in the dataset, the lens cannot use it, and you have to fix the data layer first. This single-dataset rule keeps lenses fast and predictable, and it is why dashboard designers often build several lenses, one per dataset, rather than forcing everything into one view.
Shelves, filters, and groupings
The Explorer is the no-code authoring environment. You pick a dataset, see every available field, and drag fields onto the chart elements: bars, stacks, color, size, and pages. The platform builds the visualization as you go. Measures are the numbers you aggregate, such as sum of amount or count of rows. Dimensions are the categories you slice by, such as region, stage, or product. Filters narrow the records before any aggregation runs, and they apply to everything downstream in the lens. Grouping pivots the data into categories, and you can group by more than one dimension to get nested breakdowns. The Explorer also lets you change the measure, change the sort order, and switch the aggregation without touching code. Each of these actions rewrites the query underneath, which is why the chart updates the moment you make a change. This tight loop is the whole point of exploration. You are not writing a report spec and waiting; you are nudging fields around and reading the answer in real time, then keeping the version that finally fits the question you started with.
Chart mode, table mode, and compare tables
The Lens Explorer offers several ways to look at the same query. Chart mode is the default and gives you bar, line, donut, scatter, heat map, and many other visual types. Table mode shows the raw grouped rows, which is handy when you want exact numbers rather than a shape. The compare table is a spreadsheet-style view where you can add columns, write formulas across columns, and compute derived metrics like ratios or growth without leaving the lens. Compare tables are useful when a single measure is not enough and you need to combine two or three into one calculated column. SAQL mode is the escape hatch. It exposes the Salesforce Analytics Query Language query that the Explorer has been writing for you, and you can edit it directly to reach features the point-and-click UI does not surface. Most lenses never need SAQL mode, but knowing it exists matters when a stakeholder asks for something the shelves cannot express. You can move between these modes on the same lens, so exploration in chart mode and precision work in a compare table are not separate tools.
Datasets and the data layer underneath
Lenses query datasets, which are the shaped and snapshotted tables CRM Analytics builds from Salesforce objects, external sources, or both. A dataset is not a live pointer at your CRM records; it is a copy that has been extracted, transformed, and optimized for fast analytics queries. Recipes and dataflows refresh datasets on a schedule, so the data in a lens is only as current as the last successful refresh. The structure of the dataset decides what the lens can do. Fields that were not pulled in during the build are simply unavailable, and a poorly shaped dataset with too many rows or weak filtering makes every lens on it feel slow. This is the most common cause of sluggish exploration. When a lens is slow, the fix usually lives in the dataset, not in the lens configuration. Good dataset design means pulling only the fields you need, pre-aggregating where it makes sense, and keeping row counts reasonable. Analysts who understand this relationship debug performance at the right layer instead of fiddling endlessly with chart settings that were never the bottleneck.
From a lens to a dashboard
Lenses are the raw material for CRM Analytics dashboards. The common pattern is to explore a question in the Lens Explorer until the chart is right, then clip that lens onto a dashboard as a widget. Clipping carries the query and chart configuration into the dashboard designer, where you arrange it alongside other widgets and wire up interactions. One widget can filter the others, so selecting a region in one chart can narrow every chart on the canvas. A dashboard is therefore a composed experience assembled from many lenses, each answering part of the story. Designers rarely build complex charts directly inside the dashboard editor; they build and validate them as lenses first, because a lens is reusable and a one-off dashboard widget is not. This separation keeps work tidy. The lens is the data view, refined in isolation. The dashboard is the layout and the interaction model. When a chart needs to change, you update the lens behind it, and the dashboard picks up the new definition rather than forcing you to rebuild the widget from scratch.
Sharing, security, and where Tableau fits
Lenses follow the standard CRM Analytics sharing model. You can share a lens with other users, and they will see the chart and the query, but they only see data their dataset access allows. Security predicates and app sharing still apply, so the underlying data layer governs what each person can read regardless of who built the lens. This keeps exploration safe to share inside a tenant without leaking rows. The strategic picture is worth understanding. Salesforce acquired Tableau in 2019 and has positioned Tableau, including Tableau Pulse, as its long-term analytics direction for the broader market. CRM Analytics still ships and is fully supported, and the Lens Explorer has no announced retirement. For existing CRM Analytics investments, lenses remain the right native tool, and there is no urgency to move. For brand-new analytics programs, it is reasonable to evaluate Tableau alongside CRM Analytics before committing. Knowing both stories lets you give honest advice: keep using the Lens Explorer where it already serves the org, and weigh the platform choice deliberately when you are starting fresh rather than defaulting either way.
Build a lens in the Lens Explorer
Building a lens in the Lens Explorer is a no-code task done inside Analytics Studio. You start from a dataset, shape a question with fields and filters, then save or clip the result. These steps cover the common path from blank lens to a chart you can reuse.
- Open a dataset in Analytics Studio
In CRM Analytics, go to Analytics Studio, find the dataset you want to explore, and open it. CRM Analytics creates a new lens against that dataset and shows the Lens Explorer with every available field listed on the left.
- Set the measure and grouping
Pick the measure to aggregate, such as sum of amount or count of rows, then add one or more dimensions as groupings. The chart updates immediately. Add a second grouping when you need a nested breakdown like amount by stage within region.
- Filter and choose a chart type
Apply filters to narrow the records before aggregation, then switch the chart type to match the question. Use table mode for exact numbers or a compare table when you need calculated columns combining several measures.
- Save the lens or clip it to a dashboard
Save the lens with a clear name so it can be reused, or clip it to a new or existing dashboard to turn it into a widget. Clipping carries the query and chart configuration into the dashboard designer for further layout work.
The default visual view offering bar, line, donut, scatter, heat map, and other chart types for the current query.
A grouped row view that shows exact aggregated numbers rather than a chart shape.
A spreadsheet-style view where you add columns and write formulas to compute derived metrics across measures.
Direct access to the Salesforce Analytics Query Language query behind the lens for features the no-code UI does not expose.
- A lens queries one dataset only. If a field is missing, fix the dataset build or recipe rather than expecting the Explorer to add it.
- Lenses show data as of the last dataset refresh, not live CRM records. Stale numbers usually mean a dataflow or recipe has not run, not a lens bug.
- Slow lenses are almost always a dataset problem. Trim fields and row counts at the data layer before tuning chart settings that were never the bottleneck.
- SAQL written by hand can drift from what the Explorer expects. Edits made in SAQL mode may limit some point-and-click options afterward, so save a copy first.
Prefer this walkthrough as its own page? How to Lens Explorer in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Explore and Visualize Your Data in CRM AnalyticsSalesforce
- Clip a Lens to a DashboardSalesforce
Straight from the source - Salesforce's reference material on Lens Explorer.
- View Your Data in a LensSalesforce
- SAQL Overview (Analytics SAQL Developer Guide)Salesforce
Hands-on resources to go deeper on Lens Explorer.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Lens Explorer used for inside Salesforce CRM Analytics?
Q2. Each interaction an analyst makes in Lens Explorer is compiled into what underlying query language?
Q3. When should an analyst promote a saved lens into a CRM Analytics dashboard rather than keep exploring in Lens Explorer?
Discussion
Loading discussion…