Reporting & Analytics

Salesforce offers a spectrum of analytics tools, from built-in reports to enterprise BI platforms. Selecting the right tool for each user persona, data volume, and analytical complexity is a core CTA skill. The wrong tier either frustrates users with limited capabilities or wastes budget on tools nobody fully uses.

Analytics Tools

Figure 1. Analytics tool spectrum positioned on a single complexity and volume axis. Standard Reports should be the starting point for every requirement; the escalation trigger to each next tier must be a specific gap, not a preference for more sophisticated tooling.

Standard Reports and Dashboards

Built into every Salesforce edition. Always evaluate this option first.

Capabilities

Feature	Support
Report types	Tabular, Summary, Matrix, Joined
Filters	Standard, cross, row-level formulas
Grouping	Up to 3 levels
Charts	Bar, line, pie, funnel, scatter, gauge
Dashboards	Up to 20 components per dashboard
Scheduling	Email delivery on schedule
Subscriptions	Users subscribe to reports and dashboards
Custom report types	Join up to 4 objects
Bucket fields	Group report data without formulas
Conditional highlighting	Color-code based on thresholds

Limitations

Limitation	Impact	Workaround
2,000 rows in dashboards	Summary dashboards only show top 2,000 groups	Use report drill-down or CRM Analytics
No cross-org reporting	Cannot query data across multiple orgs	CRM Analytics or Tableau with multi-org data sources
Limited joins	Max 4 objects in custom report type	Use CRM Analytics dataflows for complex joins
Historical data	Only snapshot fields, limited trending	Analytic Snapshots or CRM Analytics
Complex calculations	Row-level formulas are limited	Use CRM Analytics SAQL or Tableau calculations
No real-time	Reports query data at execution time; no streaming	Use Platform Events + CRM Analytics for near-real-time
80-character field limit	Report formula fields truncate long text	Export or use CRM Analytics

CTA exam default

Standard reports should be your default recommendation for any reporting requirement. Only escalate to CRM Analytics (formerly Tableau CRM) or Tableau when you can articulate a specific limitation that standard reports cannot address. Judges look for cost-consciousness.

Historical Trending and Analytic Snapshots

Two approaches to tracking data over time. This comes up regularly in CTA scenarios.

Historical Trending

Aspect	Detail
Objects supported	Opportunities, Cases, and up to 3 custom objects
Fields tracked	Up to 8 fields per object
History retained	Up to 5 snapshots over 3 months
Configuration	Declarative (Setup)
Reporting	Historical trend reports (shows field values at each snapshot)

Analytic Snapshots (Reporting Snapshots)

Aspect	Detail
Source	Any summary or tabular report
Target	Custom object (stores snapshot data as records)
Schedule	Daily, weekly, or monthly
Retention	As long as records exist (subject to storage)
Reporting	Standard reports on the target custom object

When to use which:

Scenario	Use
Track opportunity amount changes over time	Historical Trending
Monthly KPI dashboard comparing performance over 12+ months	Analytic Snapshots
Regulatory compliance requiring data at specific points in time	Analytic Snapshots
Quick “what changed” analysis on cases	Historical Trending

Storage impact

Analytic Snapshots create real records in custom objects. A weekly snapshot of 10,000 rows produces 520,000 records per year. Factor this into data storage calculations and LDV planning.

CRM Analytics (formerly Tableau CRM)

The in-platform advanced analytics solution, tightly integrated with Salesforce data.

When CRM Analytics is the Right Choice

Requirement	Why CRM Analytics
Complex calculations on Salesforce data	SAQL/SAQL-powered computations beyond report formulas
Cross-object analytics beyond 4-object join	Dataflows can join unlimited objects
Predictive analytics	Einstein Discovery integration
Embedded analytics	Dashboard components embedded in Lightning pages
AI-powered insights	Einstein Discovery for automated findings
Salesforce-native experience	Users stay within Salesforce; no context switching
Action from insight	Direct actions (create records, update fields) from dashboards

Architecture - Full Data Pipeline

The data pipeline moves data from source systems through transformation layers into consumable analytics assets. Understanding each stage matters for CTA scenarios involving analytics architecture.

Figure 2. CRM Analytics full data pipeline showing the five architectural layers: sources, transformation via Dataflows or Recipes, in-memory Dataset storage, consumption through Lenses and Dashboards, and action outputs including record creation and Lightning page embedding. Recipes support write-back to Salesforce objects, which Dataflows do not.

Recipes vs Dataflows

Recipes are the newer, recommended approach for most use cases. They offer a visual point-and-click interface, data preview during transformation, more join types, and built-in ML transformations (Predict Missing Values, Detect Sentiment). Dataflows use JSON definitions and are still needed for advanced scenarios like complex augment operations or legacy configurations.

Key Concepts

Concept	Description
Dataflow	ETL pipeline that extracts, transforms, and loads data into datasets
Recipe	Visual, no-code data transformation tool (newer than dataflows)
Dataset	Optimized in-memory data store for fast analytics
SAQL	Analytics-specific query language (more powerful than SOQL for analytics)
Dashboard	Interactive visualization with bindings and selections
Lens	Single dataset exploration view
Story	Einstein Discovery AI-generated narrative from data

CRM Analytics Limitations

Limitation	Impact
Refresh frequency	Dataflows typically run every 1-24 hours; not real-time
Dataset row limits	250M rows per dataset (varies by license)
Learning curve	SAQL and dashboard JSON require training
License cost	Requires CRM Analytics Plus or Growth permission set license
Not a data warehouse	Not designed for massive historical data storage
External data limits	External connector row limits vary

Tableau

A standalone enterprise BI platform for complex analytics across any data source. Integration with Salesforce has improved since the acquisition, but Tableau remains a separate product.

Tableau Architecture

Figure 3. Tableau platform architecture showing the Creator-Server-Consumer workflow and the full range of data sources Tableau can connect to. The Tableau Embedded path back to Salesforce Lightning pages is how organizations surface enterprise BI within the Salesforce experience without requiring users to context-switch to Tableau.

When Tableau is the Right Choice

Requirement	Why Tableau
Multi-source analytics	Connect to databases, data warehouses, cloud apps, files
Complex visualizations	Advanced chart types, geospatial, statistical analysis
Enterprise BI standard	Organization-wide analytics beyond CRM data
Data warehouse analytics	Query Snowflake, BigQuery, Redshift directly
Governance at scale	Centralized data governance, certified data sources
Non-Salesforce users	Users who never touch Salesforce but need business analytics

Tableau vs CRM Analytics Decision Matrix

Factor	Standard Reports	CRM Analytics	Tableau
Data source	Salesforce only	Salesforce + limited external	Any data source
User persona	Business users	Analysts + business users	Analysts + data teams
Setup complexity	Low (clicks)	Medium (dataflows, SAQL)	High (server, connections)
Learning curve	Minimal	Moderate	Moderate-High
Cost	Included	Add-on license	Separate product + licenses
Embedding	Native in Salesforce	Native in Salesforce	Tableau Embedded
Real-time	Query-time	Near-real-time with sync	Live connections or extract
Cross-object	4 objects max	Unlimited (dataflows)	Unlimited (SQL)
Predictive	No	Einstein Discovery	Tableau AI / external models
Mobile	Salesforce Mobile App	CRM Analytics Mobile	Tableau Mobile

CRM Analytics vs Tableau - Architecture Differences

Figure 4. CRM Analytics versus Tableau pipeline architecture side by side. CRM Analytics keeps all processing inside Salesforce with scheduled dataflow refreshes; Tableau uses an external server with live connections or extract-based refresh cycles. The critical architectural difference is where data is processed and stored, which drives both cost and latency characteristics.

Architecture Aspect	CRM Analytics	Tableau
Data processing	Inside Salesforce platform	External server or cloud
Data storage	Salesforce analytics storage (datasets)	Tableau extracts or live queries to source
Query language	SAQL (proprietary)	VizQL + native SQL passthrough
Refresh model	Scheduled dataflow/recipe runs	Live connection or scheduled extract refresh
Embedding	Native Lightning component	Tableau Embedded (iframe or API)
AI capabilities	Einstein Discovery (native)	Tableau AI + external model integration
Administration	Salesforce admin team	Dedicated Tableau admin team

When to use both together

In enterprise architectures, CRM Analytics and Tableau often coexist. CRM Analytics handles operational analytics embedded in Salesforce (sales manager dashboards, service agent insights). Tableau handles enterprise BI across all data sources (executive cross-system reporting, data science exploration). The deciding factor: does the analytics consumer live in Salesforce or outside it?

Data Cloud Reports

Data Cloud has its own analytics capabilities for unified customer data across systems.

Data Cloud Analytics Use Cases

Use Case	How Data Cloud Helps
Unified customer profile reporting	Aggregate data from multiple systems into a single view
Segment analysis	Analyze customer segments across touchpoints
Identity resolution metrics	Report on match rates and data quality
Activation analytics	Measure segment activation performance
Calculated insights	Custom KPIs computed across the unified data model

Data Cloud vs CRM Analytics

Data Cloud analytics focuses on the unified customer profile: cross-system identity, segmentation, and activation. CRM Analytics focuses on operational reporting and predictive analytics on CRM data. They are complementary, not competitive. A mature analytics architecture may use both.

Einstein Discovery

Uses AI to automatically analyze datasets and surface insights, predictions, and recommendations.

Capabilities

Feature	Description
Automated insights	Discovers correlations and patterns humans might miss
Predictions	Builds predictive models (classification, regression)
Recommendations	Suggests actions to improve outcomes
Story-based narratives	Explains findings in natural language
Model deployment	Deploy predictions as formula fields on Salesforce objects
Bias detection	Flags potential bias in predictive models

When to Recommend Einstein Discovery

• Customer asks: “Why are we losing deals?” or “What predicts case escalation?”
• Need predictive scoring beyond rule-based (lead score, churn risk, win probability)
• Want to surface non-obvious patterns in large datasets
• Need explainable AI (vs. black-box models)

Analytics Decision Tree

Figure 5. Analytics tool selection decision tree separating Salesforce-only from multi-source reporting paths. The four-object join limit and predictive analytics requirement are the most common escalation triggers from Standard Reports to CRM Analytics; Tableau and Data Cloud enter when non-Salesforce users or a unified customer profile are requirements.

Analytics Architecture Patterns

Pattern 1: Standard-Only (Small/Medium Orgs)

Figure 6. Standard-only analytics pattern suitable for small and medium orgs with straightforward reporting needs. No additional licenses, no separate infrastructure, and no specialized admin skills required. This is the right default for most scenarios until a specific gap demands escalation.

Pattern 2: CRM Analytics Augmented

Figure 7. CRM Analytics augmented pattern where standard reports handle day-to-day operational reporting while CRM Analytics takes on advanced use cases: joining external data, complex analytics embedded in Lightning pages, and Einstein Discovery predictions written back as formula fields on records.

Pattern 3: Enterprise Analytics (Large/Complex Orgs)

Figure 8. Enterprise analytics architecture showing all three reporting tiers operating simultaneously. Standard Reports and CRM Analytics serve Salesforce users with operational and sales analytics; Tableau serves all business users from a central data warehouse; Data Cloud unifies customer data from all three source systems to surface unified insights back within Salesforce.

Reporting Performance Optimization

Strategy	When to Apply
Report filters	Always - filter to the minimum dataset needed
Indexing	Add custom indexes on fields frequently used in report filters
Skinny tables	For reports on objects with many fields, request skinny tables from Salesforce Support
Async reports	Reports running > 2 minutes should use async API
Dashboard filters	Use dynamic dashboard filters instead of multiple similar dashboards
Scheduled reports	Schedule heavy reports during off-peak hours
Data summarization	Use rollup summary fields or batch Apex to pre-compute aggregates
Archive old data	Move old records to Big Objects or external storage to reduce report scan

Related Topics

• Decision Guides: Reporting tool selection decision flowchart
• Licensing: CRM Analytics and Tableau licensing details
• Platform Capabilities: Governor limits affecting report performance
• Trade-Offs: Analytics tool trade-off analysis
• Data Architecture: LDV considerations for reporting performance

Sources

• Salesforce Help: Reports and Dashboards
• Salesforce Help: CRM Analytics
• Salesforce Help: Historical Trending
• Salesforce Help: Reporting Snapshots
• Salesforce Help: Einstein Discovery
• Salesforce Help: Data Cloud Analytics
• Salesforce Architects: Analytics Architecture
• Tableau: Tableau Server Documentation