Analytics Groups
Analytics Groups in Salesforce reporting are the row and column bucket dimensions that turn a flat list of records into a Summary, Matrix, or Joined report.
Definition
Analytics Groups in Salesforce reporting are the row and column bucket dimensions that turn a flat list of records into a Summary, Matrix, or Joined report. Adding an Analytics Group means picking a field whose values become the section headers, with each underlying record collapsing into its bucket. A report grouped by Stage shows one row per Stage with the underlying Opportunities folded inside. Grouped by both Stage and Owner, the same data becomes a matrix where one axis is Stage and the other is Owner. Groupings are the single most powerful tool inside the report builder; they convert raw row data into a story without writing a single formula.
Outside of standard reports, the phrase Analytics Groups also appears in CRM Analytics (formerly Tableau CRM, formerly Einstein Analytics, formerly Wave) where Public Groups control who can see an Analytics App and the dashboards inside it. Both meanings share a common idea: bucket records or users into sets so the platform can apply behaviour at the bucket level rather than the individual one. Most documentation now uses the more specific phrases Report Groupings or Analytics App Sharing, but the umbrella term Analytics Groups still appears in older help articles and certification material.
How groupings shape Salesforce reports and dashboards
Tabular, Summary, Matrix, and Joined report formats
Salesforce reports come in four formats. Tabular has no groupings: every record is one row. Summary has one or more row groupings. Matrix has both row and column groupings, useful for two-dimensional pivots. Joined combines multiple report blocks (each potentially grouped) into one canvas. Choosing the format up front decides which Analytics Groups the builder lets you add later.
Group by date with the built-in date buckets
Grouping by a date field exposes extra options: by Day, Calendar Week, Calendar Month, Calendar Quarter, Calendar Year, Fiscal Quarter, Fiscal Year. Salesforce handles the bucket math, so a report grouped by Close Date Calendar Quarter automatically shows quarter labels without a formula. Picking the right granularity is more useful than building a custom Fiscal Quarter formula field most of the time.
Group by bucket fields for ad hoc segmentation
Bucket fields are report-only categorisations that let an analyst group values into custom buckets without modifying the underlying object. Bucket records by Industry into Tech and Non-Tech, or by Amount into Small, Medium, and Large bands. The bucket lives inside the report definition, so it does not persist on records, but it groups them cleanly inside the report.
Stack groupings to drill into multi-level views
A Summary report can have up to four row groupings stacked. The top group is the broadest, each nested group narrows further. A report grouped by Region, then by State, then by Account Owner exposes a three-level breakdown of pipeline. Subtotals at each level make the report self-summarising, which is often more useful than the row-level detail.
Summary fields inside groupings
Each grouping can show summary values: Sum, Average, Min, Max, Median, count, and a few others. Reports can also expose Summary Formulas that calculate values across groupings (year-over-year change, percent of total, win rate). These formulas live at the report level and reference the groupings explicitly through abbreviations like GRAND_SUMMARY:SUM, PARENTGROUPVAL, and PREVGROUPVAL.
Dashboards consume groupings as chart series
When a Summary or Matrix report feeds a dashboard component, the chart inherits the report's groupings. The first grouping becomes the X-axis, the second becomes the series. Changing the report's groupings rearranges the dashboard chart without further dashboard editing. This is why dashboards that look complex are usually downstream of a carefully designed Summary report.
CRM Analytics groups and app sharing
Inside CRM Analytics, Public Groups (created in Salesforce Setup) are the standard mechanism for sharing an Analytics App, its dashboards, and datasets. Adding the Field Sales Analytics Group to the App gives every member of that Public Group access to the contained assets. App-level sharing replaces the older one-asset-at-a-time approach and is the recommended pattern for production analytics rollouts.
Common grouping mistakes
The most common mistake is grouping by a high-cardinality field (Account Name, Opportunity Name) that produces hundreds of one-row groups. Reports become hard to read and slow to render. The second mistake is forgetting that hiding the Details still leaves groupings; collapsed summaries are still computed against the same record set. The third mistake is using a bucket field where a permanent picklist would be better; bucket fields are ad hoc and do not sync across reports.
How to add and use Analytics Groups in a report
Groupings are added in the Lightning Report Builder by dragging a field into the Groups area. Picking the right field and the right granularity does most of the work; the formatting decisions follow.
- Choose the report format
Tabular for raw rows, Summary for one or more row groupings, Matrix for row plus column, Joined for combined blocks. Format is the constraint that decides which groupings are allowed.
- Add the first row grouping
Drag a field into the Group Rows area. Choose date granularity if applicable. Confirm the row count collapses as expected.
- Add a column grouping if using Matrix
Switch to Matrix and drag a field into Group Columns. The report now becomes a two-axis pivot.
- Configure summary fields per grouping
Select Sum, Average, Min, Max, Median, or Count on the relevant numeric fields. Add Summary Formulas if the calculation crosses groupings.
- Bind the report to a dashboard component
Create or edit a dashboard, choose the report as the source, pick a chart type that fits the groupings (column chart for one grouping, stacked column for two), save the dashboard.
- Grouping by a high-cardinality field produces hundreds of one-row groupings and slows the report down. Pick fields whose values are countable in your head.
- Bucket fields live inside one report. They do not sync across reports, so the same buckets have to be re-created each time, or moved to a real picklist for reuse.
- Matrix reports support exactly one row and one column grouping each. Stacking more requires Summary plus drill paths, not Matrix.
- Joined reports cap at five blocks. Beyond that, the report becomes unwieldy and dashboard binding gets brittle.
Trust & references
Cross-checked against the following references.
- Group Records in a ReportSalesforce Help
- CRM Analytics OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Analytics Groups.
- Summary FormulasSalesforce Help
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. Who benefits most from Analytics Groups in an organization?
Q2. What type of data does Analytics Groups typically work with?
Q3. What is the primary purpose of Analytics Groups in Salesforce?
Discussion
Loading discussion…