DATA 360 / QUERY & INSIGHTS
Query & Insights
Data 360's SQL dialect, Calculated Insights, and the Query API. The bridge from the SQL you already write in Marketing Cloud to the queries that run over the unified data model.
Foundation · 2
Production note
Data 360 query gotchas: where the SQL instinct misleads
Data 360's query surfaces look like the SQL you already write in Marketing Cloud — and that resemblance is the trap. Ten gotchas across the dialect, Calculated Insights, and the Query API, each with the question to answer first and the cost of getting it wrong.
Decision framework
Data 360 Query & Insights: Style Guide
The opinionated rules Cleon applies to every Data 360 query decision — the Calculated Insight vs. live Query call at the center, the SQL conventions, the cost and freshness discipline, the patterns to prefer and the ones to refuse, plus the agent-readiness check and a pre-ship checklist. The discipline document that ties the Query & Insights subcategory together.
Reference · 5
Reference
Data Cloud SQL: the dialect you query the unified profile with
What Data Cloud SQL is: an ANSI-compliant dialect you run in the Query Editor and the Query API over DMOs, DLOs, and Calculated Insight Objects — the unified profile, not flat Data Extensions. The naming rules, the clause behavior, and what carries over from Marketing Cloud SQL.
Reference
Bridging from Marketing Cloud SQL: a crosswalk to Data 360's query surfaces
A practitioner's crosswalk for the Marketing Cloud SQL veteran: each MC SQL pattern you already know, its Data 360 equivalent, and where the instinct quietly misleads. Assumes the dialect — links to it rather than re-documenting it.
Reference
Calculated Insights: the metric you compute once and retrieve everywhere
What a Calculated Insight is: an aggregation defined by dimensions and measures — not an arbitrary SELECT — pre-computed once and served everywhere as a queryable Calculated Insight Object. Batch vs streaming, the real limits of each, the freshness that makes the result trustworthy or silently wrong, and the separate SQL dialect you author it in.
Reference
The Data 360 Query API: running SQL over the model from code
The programmatic side of Data Cloud SQL: run a live query over the unified model from code and get rows back. The two surfaces — the synchronous Query API v2 with its nextBatchId cursor, and the newer asynchronous Query Connect API with a queryId and offset paging — the auth flow at a high level, the time constraints Salesforce enforces, and when a live query beats a Calculated Insight.
Reference
Consuming query results: who reads a Calculated Insight, and why they all read the same one
The retrieve-many half of compute-once-retrieve-many, made explicit. Where a Calculated Insight goes after it's computed — segments, activations, agents, analytics — and why every consumer inheriting the same grain and freshness is the point, not an accident.