[object Object]

The Rebrand

Announced at Dreamforce 2025, effective across 2026 releases. Data Cloud is now Data 360 — its sixth name after Customer 360 Audiences, Salesforce CDP, Marketing Cloud CDP, Salesforce Genie, and Data Cloud. The rebrand timeline: Spring ‘26 release notes use the new name throughout, the Setup menu navigation updated in mid-March 2026, AppExchange listings transitioned over Q2 2026, and the underlying SKU codes (CDP_DATA_CLOUD_*) remain unchanged for billing continuity. Existing API namespaces (/services/data/v62.0/ssot/*) are unaffected. Customer-facing documentation completed the transition by April 2026.

Strategic Positioning

Data 360 is the data foundation for Agentforce 360. Salesforce frames it not as static tables but as live context fueling AI workflows. The semantic model (via Tableau Semantics) normalizes metrics across clouds. Concretely: a Data Stream from a Snowflake table, a Data Lake Object from a Marketing Cloud send, and an Engagement event from a website now share a unified semantic definition of “active customer” that any agent can query without rebuilding the metric per use case. The Tableau Semantics layer compiles these definitions to SQL when consumed by Tableau Next dashboards and to MCP tool responses when consumed by Agentforce agents.

What Actually Changes

No rebuild required. Existing Data Cloud deployments continue under the Data 360 name. New capabilities: Intelligent Context (agents access PDFs, diagrams for task guidance), Tableau Semantics for consistent metrics. Specifically arriving across Spring and Summer ‘26:

  • Intelligent Context: Agentforce agents can ground responses in unstructured assets (PDFs, Confluence pages, Slack canvases) indexed alongside structured DLOs
  • Tableau Semantics: Shared metric definitions across BI and agent surfaces, eliminating “the dashboard says X but the agent says Y” inconsistencies
  • Streaming Ingestion improvements: Sub-second latency for Engagement events, up from 30-second batches
  • Identity Resolution Rulesets: GA for the new declarative ruleset builder, replacing the legacy match-rule UI
  • Calculated Insights v2: SQL-based authoring with version control via Git connector

Example calculated insight definition:

SELECT
  customer.id AS CustomerId,
  SUM(orders.total_amount) AS LifetimeValue,
  MAX(orders.order_date) AS LastOrderDate,
  COUNT(DISTINCT orders.id) AS OrderCount
FROM Customer__dlm customer
LEFT JOIN Order__dlm orders ON orders.CustomerId = customer.id
WHERE orders.order_date >= DATEADD(year, -2, CURRENT_DATE())
GROUP BY customer.id

How to Message

Internally: ‘same platform, broader positioning.’ Externally: ‘the data layer feeding our agents.’ Don’t re-migrate. Don’t over-explain. Update docs and dashboards as you touch them naturally. The internal communication template most enterprises used:

Salesforce renamed Data Cloud to Data 360 to align with the Agentforce 360 product family. Our deployment, integrations, and security configurations are unaffected. Existing dashboards and reports continue to work. New documentation will use “Data 360”; existing references to “Data Cloud” will be updated as documents are revised through normal cycles.

Avoid emphasizing the name change to customers — it’s the sixth rebrand and analysts will note it. Emphasize the new capabilities (Intelligent Context, Tableau Semantics) instead.

What Changed in 2026

Beyond the name, the real architectural shift is positioning Data 360 as the agent grounding layer rather than a standalone CDP. Pre-2026, Data Cloud was sold to marketing teams for segmentation. In 2026, Data 360 is sold to whoever owns Agentforce because grounded agents need Data 360 for accurate, fresh, sharing-aware context. The same product; a different buying center and a different conversation.

Common Failure Modes

Renaming objects in your Data Streams during the rebrand “to match the new branding.” Don’t. Object API names are referenced by every integration, segmentation rule, and downstream consumer. Leave them alone. Second: assuming Tableau Semantics replaces Calculated Insights — they’re complementary. Tableau Semantics defines metrics consumed by BI; Calculated Insights produce stored aggregates consumed by activation and segmentation. Third: turning on Intelligent Context for sensitive PDFs without reviewing what gets indexed. The vector store inherits FLS but unstructured content masking is still maturing.

What to do this week

Update the Data 360 reference in your internal documentation index. Audit one Calculated Insight against the new SQL-based authoring to verify your team can read and maintain it. Pilot Intelligent Context on one knowledge base if you have an Agentforce deployment, with explicit content review before enabling.

[object Object]
Share