Study guide
11.3 CI vs. SI Architectural Decision Matrix & Performance Optimization
Salesforce Certified Data 360 Consultant formerly Data Cloud Consultant
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Solution Overview & Enterprise Value
1.1 Enterprise Customer 360 & Data Cloud Business Value 1.2 Architectural Foundation: Zero-Copy, Hyperforce, Lakehouse & Data Pipeline 1.3 Platform Terminology, Core Entities & Data Lifecycle Stages 1.4 Data 360's Foundational Role in Predictive & Generative AI
2 Chapter 2: Ethics, Privacy & Governance Fundamentals
2.1 Regulatory Compliance, Data Privacy & Ethics in Customer Data 2.2 Consent Management & Preference Enforcement in Data Cloud 2.3 Data Retention, Deletion, and Privacy Right-to-be-Forgotten (RTBF)
3 Chapter 3: Security, Permissions & Tenant Architecture
3.1 Standard Permission Sets, User Roles & Functional Access 3.2 Data Spaces Architecture, Resource Allocation & Tenant Isolation
4 Chapter 4: Administration, Monitoring & Lifecycle Management
4.1 Data Kits & Package Automation for Cross-Org Deployment 4.2 Auditing, Status Monitoring, Error Logs & Data Explorer 4.3 Sandboxes, Change Management & Metadata Deployment
5 Chapter 5: Ingestion Connectors & Source Integration
5.1 Standard Bundles & Salesforce CRM Connectors (Sales/Service/Marketing) 5.2 Cloud Storage (S3, GCS, Azure Blob) & Streaming Ingestion (Web/Mobile SDK, Ingestion API) 5.3 Zero-Copy Data Federation & Snowflake/BigQuery/Databricks Sharing
6 Chapter 6: Data Lake Objects (DLO) & Data Transformations
6.1 DLO Configuration, Primary Keys, Event Time & Data Stream Categories (Profile, Engagement, Other) 6.2 Streaming & Batch Data Transforms: Formula Fields, SQL Transforms & Data Prep Recipes
7 Chapter 7: Data Model Objects (DMO) & Canonical Harmonization
7.1 Customer 360 Canonical Data Model & Subject Areas 7.2 DLO-to-DMO Mapping Patterns, Cardinality & Custom DMO Design 7.3 Data Validation, Schema Maintenance & Field Mapping Best Practices
8 Chapter 8: Identity Resolution Architecture & Match Rules
8.1 Identity Resolution Concepts, Consolidation Rate & Graph Modeling 8.2 Match Rules & Match Criteria: Exact Match vs. Fuzzy Matching (Deterministic & Probabilistic) 8.3 Multi-Party Identification, Anonymous-to-Known Transitions & Contact Point Matching
9 Chapter 9: Reconciliation Rules & Unified Profile Governance
9.1 Reconciliation Rules: Most Frequent, Source Priority & Last Updated 9.2 Unified Profile Schema (Individual & Contact Points) & Resolution Troubleshooting
10 Chapter 10: Segment Architecture & Audience Design
10.1 Segmentation Canvas, Segment Types (Standard UI & Flow) & Query Processing 10.2 Direct vs. Related Attributes, Cardinality & 1:N Filtering Traps 10.3 Segment Schedule, Refresh Frequencies & Exclusion Logic 10.4 Segment Membership Analysis, Population Drift & Sizing Validation
11 Chapter 11: Calculated & Streaming Insights
11.1 Calculated Insights (CI) Architecture, SQL/Builder Syntax & Dimensions vs. Metrics 11.2 Streaming Insights (SI) Architecture, Windowing (Tumbling/Sliding) & Real-Time Signals 11.3 CI vs. SI Architectural Decision Matrix & Performance Optimization
12 Chapter 12: Data Enhancements, Sharing & Analysis
12.1 Referencing Data 360 Data from Other Systems: Enrichments, Related Lists, Data Graphs & APIs 12.2 Reports, Dashboards & Tableau Analysis on Data 360 Data 12.3 Applying Predictive & Generative AI Tooling to Customer Scenarios
13 Chapter 13: Activation Targets & Outbound Activation
13.1 Activation Targets: Marketing Cloud, External Platforms, Cloud Storage & Data Spaces 13.2 Activation Configuration: Audience Mapping, Related Attributes & Payload Optimization 13.3 Activation Schedules, Publishing Cadence & Incremental vs. Full Refresh 13.4 Activation Troubleshooting: Error Logs, Rejection Reasons & Delivery Failures
14 Chapter 14: Real-Time Data Actions & Flow Automation
14.1 Data Action Targets & Webhook/Platform Event Architecture 14.2 Data Cloud-Triggered Flows & Real-Time Business Orchestration 14.3 End-to-End Enterprise Scenario Walkthrough: Ingestion to Closed-Loop Action
11.3 CI vs. SI Architectural Decision Matrix & Performance Optimization
Key Takeaways Explain This Topic AI
Calculated Insights (CIs) operate in batch over massive historical datasets with hourly or daily refreshes, while Streaming Insights (SIs) operate continuously on in-flight data streams with sub-minute execution latencies.
Calculated Insights support complex multi-hop relational joins across DMOs and Unified Link tables, whereas Streaming Insights are strictly optimized for single streaming sources or minimal lookup joins.
CIs output to materialized insight objects (__cio) utilized by the Segment Canvas, Activations, and CRM Console; SIs do not write to the Segment Canvas and instead output exclusively to Data Actions (Platform Events and Webhooks).
Configuring overly aggressive sliding windows (e.g., a 24-hour lookback evaluated every 30 seconds) creates severe state memory pressure on the streaming engine and rapidly exhausts Data Cloud streaming compute credits.
Consultants must rigorously match business latency requirements to the compute paradigm: sub-minute triggers mandate Streaming Insights, whereas deep historical lifetime aggregations mandate Calculated Insights.
Last updated: September 2026
CI vs. SI Architectural Decision Matrix & Performance Optimization
When designing enterprise customer data solutions in Salesforce Data Cloud, one of the most critical architectural responsibilities of a certified consultant is selecting the right computational paradigm for analytical and real-time requirements. Implementing the wrong tool—such as attempting to use batch Calculated Insights for sub-minute cart abandonment triggers, or attempting to use Streaming Insights for multi-year customer lifetime value calculations—results in project failure, query timeouts, or runaway consumption of Data Cloud credits.
This section provides an exhaustive decision framework comparing Calculated Insights (CI) , Streaming Insights (SI) , Segmentation Canvas Formulas , and Batch Data Transforms , alongside deep-dive performance tuning rules and credit governance strategies.
Comprehensive Architectural Comparison Matrix
The following matrix details the fundamental technical differences between Calculated Insights and Streaming Insights across all evaluation axes:
Architectural Dimension Calculated Insights (CI) Streaming Insights (SI)
Execution Paradigm Batch processing on a scheduled or on-demand cadence Continuous, stateful stream processing on incoming events
Processing Latency Hourly, 4-hour, 12-hour, or 24-hour batch refresh Sub-minute (near-real-time / seconds)
Data Storage Scope Full historical depth (terabytes/petabytes at rest in Lakehouse) In-flight streaming buffer / transient memory state
Underlying Engine Hyperforce distributed big data engine (Spark SQL) Stateful streaming event processing engine
Windowing Capability Calendar dates, rolling days ( LAST_N_DAYS ), fiscal periods Formal temporal windows ( TUMBLING and SLIDING )
Join Complexity High: Supports multi-hop joins across DMOs and Unified Link tables Low: Restricted to single streaming DMOs or simple lookups
Output Destination Materialized Insight Object ( __cio ) in Data Cloud Direct emission to Data Actions (Platform Events / Webhooks)
Direct Segmentation Yes : Fully accessible in Segment Canvas attribute library No : Cannot be dragged directly onto the Segment Canvas
Activation Targets Yes : Exportable as direct/related attributes to S3, MC, Ads No : Transmitted via Platform Events or Webhook payloads
CRM UI Integration Native via FlexCards, Query API, and Copy Field Enrichment Real-time Flow triggers creating tasks/alerts in CRM
Credit Burn Driver Processed data volume, join complexity, and refresh frequency Streaming event volume, window duration, and slide frequency
The 4-Way Compute Decision Framework
In addition to CIs and SIs, Data Cloud architects have two other data manipulation tools at their disposal: Segmentation Canvas Formulas and Batch Data Transforms . Understanding when to deploy each tool is essential for the exam. START: Analytical Requirement
│
Is the requirement real-time (sub-minute latency)?
- ├─── YES ──► STREAMING INSIGHT (SI)
- │ (Windowing + Data Actions)
- └─── NO
- │
- Does it require multi-object data cleansing, flattening,
pivoting, or restructuring before canonical DMO mapping?
- ├─── YES ──► BATCH DATA TRANSFORM
- │ (SQL or Data Prep Recipe)
- └─── NO
- │
- Is it a complex multi-row aggregation (SUM, AVG, COUNT)
reused across multiple segments, activations, or CRM UI?
- ├─── YES ──► CALCULATED INSIGHT (CI)
- │ (Pre-aggregated __cio)
- └─── NO
- │
Ad-hoc, single-segment direct attribute filter?
- └──────────► SEGMENTATION CANVAS FORMULA
- 1. Calculated Insights (CI)
When to Use : Reusable historical aggregations across multiple source records (e.g., Customer Lifetime Value, RFM scores, Total Orders, Preferred Category). When multiple marketing segments or CRM pages need the same pre-computed number without recalculating it repeatedly.
Exam Indicator : "Calculate total spend over the last 3 years and make it available across multiple marketing segments."
2. Streaming Insights (SI)
When to Use : Event-driven behavioral detection requiring action within seconds or minutes. Windowed aggregations over unbounded telemetry.
Exam Indicator : "Detect when a customer experiences 3 payment failures in 10 minutes and immediately open a high-priority case in Service Cloud."
3. Segmentation Canvas Formulas & Direct Filters
When to Use : Ad-hoc, one-off filtering logic specific to a single audience segment. Evaluating simple attributes (e.g., City = 'Chicago' or LastLoginDate >= LAST_30_DAYS ) on single objects without pre-aggregation.
Exam Indicator : "A marketer wants to create a one-time promotional segment of customers living in California who have logged in within the past 7 days."
4. Batch Data Transforms (SQL / Recipe Transforms)
When to Use : Heavy ETL/ELT transformations, joining disparate raw DLOs before DMO mapping, data cleansing, address standardization, or flattening nested JSON structures into tabular formats.
Exam Indicator : "Combine and clean raw POS and online order staging tables to create a unified transaction dataset prior to canonical mapping."
- Refresh Schedules, Performance Tuning & Optimization
- Calculated Insight Optimization Rules
Calculated Insights run against distributed storage. Poorly authored SQL can lead to long execution runtimes and excessive credit consumption.
Right-Size the Dimension Grain :
Anti-Pattern : Grouping by high-cardinality fields such as TransactionTimestamp__c or SessionId__c in a customer-level insight.
Best Practice : Group strictly by the necessary business dimensions (e.g., UnifiedIndividual__dlm.Id__c and ProductCategory__dlm.Name__c ). Every additional dimension multiplies output row volume.
Filter Early with WHERE Clauses :
Anti-Pattern : Aggregating all 10 years of historical transactions and filtering the output later.
Best Practice : Restrict input rows at the earliest possible stage using WHERE SalesOrder__dlm.OrderedDate__c >= DATE_ADD('year', -2, CURRENT_DATE()) .
Align Refresh Cadence with Upstream Ingestion :
If e-commerce orders are ingested once daily at midnight, scheduling a Calculated Insight to refresh every 4 hours wastes compute credits without providing fresh data. Schedule the CI refresh to run shortly after upstream batch ingestion completes.
Prune Unused Insights :
Inactive or deprecated CIs continue to consume scheduled compute resources unless explicitly disabled or deleted.
Streaming Insight Optimization Rules
Streaming Insights maintain an in-memory state store for the duration of open windows. Misconfigured window parameters can crash the streaming pipeline.
The Window Duration vs. Slide Increment Ratio :
The memory footprint of a sliding window is directly proportional to (Duration / Slide).
Catastrophic Configuration : A 24-hour window sliding every 10 seconds creates 8,640 concurrent overlapping windows in memory for every active customer!
Best Practice : Keep slide increments reasonable (e.g., 15-minute window sliding every 2 to 5 minutes).
Avoid Joining Static Historical Tables in SIs :
Attempting to perform deep relational joins between a streaming engagement DMO and massive historical batch DMOs in a Streaming Insight introduces state bloat and latency violations.
Credit & Resource Governance
Data Cloud billing is metered through Data Cloud Credits . Understanding credit consumption drivers is an executive-level consulting skill tested on the exam:
Calculated Insight Credit Consumption
Credits are consumed based on the volume of data scanned (Gigabytes/Terabytes processed) during each scheduled refresh and the compute complexity (number of joins, sort operations, and group-by cardinality).
Cost-Reduction Tactics :
Use incremental refresh capabilities where available.
Avoid full table scans by applying date partitions in WHERE clauses.
Reduce refresh frequency from hourly to daily for non-urgent metrics.
Streaming Insight Credit Consumption
Credits are consumed based on streaming event throughput (millions of ingested events evaluated) and the continuous compute capacity allocated to stateful sliding window evaluation.
Cost-Reduction Tactics :
Filter streaming events at the ingestion source (e.g., configure the Web SDK to only stream relevant e-commerce events rather than every mouse hover).
Increase slide increment intervals to reduce evaluation frequency.
Common Exam Traps & Anti-Patterns
Consultants frequently encounter challenging, trap-laden scenarios on the certification exam. Memorize these critical anti-patterns:
Warning
Trap 1: Attempting to Use Calculated Insights for Sub-Minute Real-Time Actioning The Scenario : A question asks how to trigger an immediate SMS alert when a customer walks past a beacon or abandons a digital shopping cart within 5 minutes. The Trap : Selecting a Calculated Insight with an hourly schedule. The Reality : CIs cannot achieve sub-minute execution latencies. Any scenario requiring immediate closed-loop automation within minutes mandates a Streaming Insight with a Data Action .
Warning
Trap 2: Expecting Streaming Insights to Appear on the Segment Canvas The Scenario : A marketer wants to drag a Streaming Insight metric onto the Segment Canvas to build an audience of shoppers. The Trap : Looking for SIs under the Segment Canvas attribute library. The Reality : Streaming Insights cannot be used directly in the Segment Canvas. SIs output exclusively to Data Actions (Platform Events and Webhooks). If an aggregation is needed for audience segmentation, it must be authored as a Calculated Insight .
Warning
Trap 3: Multi-Table Historical Relational Joins in Streaming Insights The Scenario : An architect attempts to write an SI that joins incoming mobile clickstream data across Sales Order, Order Line Item, Master Product, and Customer Loyalty Ledger. The Trap : Assuming SQL capabilities are identical between CIs and SIs. The Reality : Streaming Insights do not support complex multi-hop historical joins. They are designed for fast aggregations on streaming feeds with minimal lookup data.
Warning
Trap 4: Missing Mandatory Dimension Keys in CIs The Scenario : A data engineer writes a Calculated Insight to compute overall total company revenue and omits the GROUP BY clause. The Reality : The platform rejects the insight. CIs strictly require at least one dimension to define the aggregation grain and primary key.