Salesforce Data 360 (Formerly Data Cloud): A Practical Guide For Growth
What Salesforce Data 360 is, how it turns scattered customer data into unified profiles your teams and agents can act on, what drives its consumption bill, and a five-step plan to start small and prove value before you scale.
Key Takeaways
- Data 360 is Data Cloud, renamed. Salesforce rebranded Data Cloud to Data 360 on October 14, 2025, and says the functionality is unchanged. Many screens, permission sets and docs still say "Data Cloud".
- It connects, harmonizes and unifies customer data from Salesforce and external systems into unified profiles, then lets you segment, analyze and act on that data across Sales, Service, Marketing, Commerce and Agentforce.
- Agentforce depends on it. Data 360 must be provisioned for any Agentforce use, and it must be implemented, not just switched on, for agents grounded in unified customer data.
- Pricing is consumption-based. Every streaming refresh, unification run, query and activation spends credits, so cost is an architecture decision, not a procurement detail.
- The companies that get value fastest pick one use case, define its success metric, model the data for that use case, and scale only once the result and the credit burn are understood.
Salesforce Data 360 (formerly Salesforce Data Cloud) is the data layer of the Salesforce Platform. It brings customer data from Salesforce orgs, data warehouses, websites, apps and files into one model, resolves it into unified customer profiles, and makes those profiles usable inside Sales Cloud, Service Cloud, marketing journeys, analytics and AI agents. Salesforce describes it as the real-time data engine behind the platform and the data foundation for Agentforce.
This guide is written for the leaders who have to make it pay off: revenue, marketing, service and IT leaders at growing and mid-market companies who already run on Salesforce and are being asked whether Data 360 is worth turning on. It covers what the product does, how it works, what it costs to run, where projects go wrong, and a practical sequence for getting a first use case live.
What Is Salesforce Data 360, And Is It Just Data Cloud Renamed?
Yes. Salesforce Data 360 is the new name for Salesforce Data Cloud. Salesforce announced it with Agentforce 360 at Dreamforce on October 13, 2025, and the rebrand took effect on October 14, 2025. Salesforce Help states that the functionality is unchanged and that you may still see "Data Cloud" in the product and documentation during the transition.
Data 360 began as a customer data platform (CDP) for marketers. Salesforce now positions it as the evolution of that CDP: a data layer for every team, which also grounds AI. It runs on Hyperforce, ingests batch and streaming data, and can query data that stays in an external warehouse without copying it.
The rename is cosmetic, but it causes real confusion during projects. This is what you will still see under the old names:
| Where you look | What it says today | What it means |
|---|---|---|
| Product name | Salesforce Data 360 (Data 360) | The same product formerly sold as Data Cloud |
| Setup | "Data Cloud Setup" in many orgs and docs; "Data 360 Setup" in newer material | The admin area for users, data spaces and integrations |
| Access | Data Cloud Architect, Data Cloud Activation Manager, Data Cloud Activation Specialist, Data Cloud User | Unchanged names; assign them as before |
| Multi-org | "Data Cloud One" (sometimes "Data 360 One") | One home org sharing Data 360 with companion orgs |
| Flows | Data Cloud-Triggered Flows | Flows that start from changes in Data 360 data |
| Platform | Salesforce Platform (formerly Einstein 1 Platform); Agentforce 1 Editions (formerly Einstein 1 Editions) | Related renames you will meet in contracts and older articles |
How Does Salesforce Data 360 Work?
Data 360 works in four stages: it connects to your data sources, harmonizes their data into one standard model, unifies records about the same person or account into a single profile, and then lets teams, flows and agents act on those profiles. Each stage is configured separately, and each one consumes credits when it runs.
Bring In Batch, Streaming And Zero-Copy Data
Data streams connect sources: Salesforce clouds through native connectors, cloud storage such as Amazon S3 and Google Cloud Storage, web and mobile events, the Ingestion API, MuleSoft, and warehouses such as Snowflake, Databricks, Google BigQuery and Amazon Redshift through zero copy. Salesforce advertises more than 200 connectors.
Map Every Source To The Customer 360 Data Model
Raw data lands in data lake objects (DLOs). Transforms clean and reshape it, and mappings place it into data model objects (DMOs) in the standard Customer 360 Data Model, so an "email" from your web store and an "email" from Service Cloud mean the same thing.
Resolve Identities Into Unified Profiles
Identity resolution rulesets use match rules (exact, fuzzy or normalized) to link records about the same individual or account, and reconciliation rules to decide which value wins, by recency, frequency or source priority. The result is a unified profile that still traces back to every source record.
Insights, Segments, Flows, Analytics And Agents
Calculated and streaming insights compute metrics such as lifetime spend. Segments group customers and activate them to marketing, advertising and storage targets. Data actions and Data Cloud-triggered flows react to changes. Unified data also appears in CRM records, reports, Tableau and CRM Analytics, and grounds Agentforce and Prompt Builder.

The Data 360 Building Blocks, In Plain Language
Most of the confusion in a Data 360 project comes from about a dozen terms. These are the ones your team will use every week, with the decision each one forces.
| Term | What it is | Why it matters to you |
|---|---|---|
| Data stream | A connected source feeding Data 360, batch or streaming | Each stream is a cost and maintenance decision; connect what a use case needs, not everything |
| Data bundle | A pre-modeled data set installed when you connect Salesforce data | Gets Sales and Service Cloud data in without hand-mapping |
| Data lake object (DLO) | Where ingested data lands, close to its source shape | Flows cannot read DLOs directly; data must be mapped first |
| Data model object (DMO) | An object in the standard Customer 360 Data Model | The model is highly normalized, so source data often needs reshaping before mapping |
| Data space | A logical container for data, metadata and processes | Separates brands, regions or business units inside one instance |
| Identity resolution ruleset | Match and reconciliation rules that build unified profiles | Too strict misses real matches; too loose merges different people. Every ruleset adds to billable usage |
| Calculated insight | A batch metric, such as customer rank by spend | Powers segments, flows and dashboards |
| Streaming insight | A metric over rolling windows as short as one minute | Drives near-real-time actions; not usable in segmentation or activation |
| Data graph | A precomputed, connected view of profile data (standard or real-time) | Fast lookups for agents, flows and real-time personalization |
| Segment and activation | An audience, and its delivery to a target such as Marketing Cloud Engagement, Google Ads, Meta, LinkedIn or Amazon S3 | A purchased capability; standard segments publish every 12 to 24 hours, rapid segments every 1 to 4 hours |
| Data action | An event sent when DMO or insight data changes | Triggers Platform Events, webhooks, Marketing Cloud Engagement or Amazon Kinesis |
| Search index and retriever | Vector or hybrid indexes over unstructured content, queried by retrievers | How agents and prompts find the right PDF, knowledge article or transcript |
Definitions summarized from Salesforce Help, Trailhead and the Data 360 developer guide. Limits such as segment publish schedules are from Salesforce's Data 360 Limits and Guidelines.
What Is Zero Copy, And When Should You Use It?
Zero copy lets Data 360 work with data that stays in your warehouse or lakehouse instead of copying it in. Federation lets Data 360 read external data, and sharing lets external platforms read Data 360 data. Use it when the warehouse is already your source of truth, but plan for the compute it moves elsewhere.
Salesforce's Zero Copy Partner Network lists AWS, Databricks, Google, Snowflake and Microsoft. Zero copy also works with external systems outside that network. There are three ways to bring data in, and the choice affects latency, cost and which features you can use:
| Approach | How it works | Cost and limits | Use it when |
|---|---|---|---|
| Ingestion (copy) | Data is loaded into Data 360 in batch or streaming | Bringing data in is free; streaming pipelines and processing consume credits | Data is needed for real-time triggers or there is no warehouse |
| Query federation | Queries run on the external system's engine; live by default, with optional caching | May incur compute fees in the external platform; caching is needed for data actions | The source supports nothing else, or freshness matters most |
| File federation | Data 360 reads the storage layer (for example Apache Iceberg tables) with its own compute | No external compute fees; not supported by every system | Salesforce recommends it wherever the source supports it |
| Zero copy sharing | External platforms read unified Data 360 data in place | Consumes Data 360 credits (Zero Copy Sharing-Out) | Data science or BI teams need unified profiles in the warehouse |
Two details catch teams out. Some sources cannot federate across regions: Salesforce's example is a Snowflake instance in an EU region that can federate to an EU Data 360 but not to a US one. And zero copy does not make cost disappear. Query federation shifts compute to the connected platform, so a Snowflake or Databricks bill can rise as Data 360 usage grows. For a deeper look at one pairing, see our guide to Snowflake and Salesforce Data Cloud.
What Can Each Team Do With Data 360?
Data 360 earns its cost when a specific team can do something it could not do before, because the data it needed was in another system. These are the patterns Salesforce documents, translated into the business problem each one solves.
Sales: forecast and cross-sell
Spot cross-sell and upsell opportunities from purchase and product-usage data, prioritize prospects by buyer intent, and give leadership one forecast across business units or orgs.
Service: proactive support
Show agents the full customer history, then act before the customer calls: open a case when a device signal or a calculated insight crosses a threshold, or notify customers about warranties and recalls.
Marketing: segments on behavior
Build audiences from what customers do, not just CRM fields. For example, compute average spend, split customers into tiers, and activate each tier to journeys and ad platforms.
Commerce: personalize and retain
Personalize storefront experiences and loyalty offers from unified order, browsing and service data. A flow can react when a customer's loyalty tier changes or carts are abandoned.
Agentforce: grounded agents
Give AI agents the unified profile, recent behavior and the right documents through search indexes and retrievers, so answers reflect the real customer, not only the CRM record.
Leadership: one view across orgs
After an acquisition or in a multi-org estate, Data Cloud One shares one Data 360 instance from a home org with companion orgs, so leaders see the whole customer base without merging orgs first.
Industry clouds build on the same layer: Salesforce documents a unified client view in Financial Services Cloud and unified health scoring in Health Cloud. If marketing is the first use case, Data 360 also works with Marketing Cloud Next.
Do You Need Data 360 For Agentforce?
Yes, at least provisioned. Salesforce's Trailhead states that Data 360 must be provisioned and enabled for all Agentforce use, and that features such as the Agentforce Data Library and the Einstein Trust Layer do not work without it. Enabling it is not the same as building it out, and the difference decides how good your agents are.
| State | What it means | What your agents can do |
|---|---|---|
| Enabled | Data 360 is provisioned in the org | Agentforce runs; Trust Layer features, audit data and analytics work; agents mostly see CRM records and the knowledge you give them |
| Built out | Sources are connected, mapped, harmonized and unified | Agents work from unified profiles, real-time data, zero-copy warehouse data and custom retrieval (RAG) over your documents |
An agent is only as good as the data it can find. If profiles are incomplete or knowledge content is out of date, the agent answers confidently and wrongly. That is why we treat the Data 360 model and Agentforce data and knowledge integration as part of every Agentforce implementation, not as a separate project.
Data 360 vs. A CDP vs. A Data Warehouse: Side By Side
Data 360 is not a replacement for your warehouse, and it is broader than a classic marketing CDP. A warehouse stores and analyzes everything; a CDP builds marketing audiences; Data 360 unifies customer data so that Salesforce apps, flows and agents can act on it inside the CRM. Many companies run Data 360 alongside a warehouse, joined by zero copy.
| Question | Salesforce Data 360 | Standalone marketing CDP | Data warehouse or lakehouse |
|---|---|---|---|
| Main job | Unify customer data and act on it across Salesforce | Build and activate marketing audiences | Store, transform and analyze all company data |
| Primary users | Sales, service, marketing, commerce, admins, AI agents | Marketing teams | Data engineers, analysts, data scientists |
| Identity resolution | Built in, with rulesets and unified profiles | Built in | Built by your team |
| Acting in the CRM | Native: record enrichment, flows, data actions, Agentforce grounding | Through integrations | Through reverse ETL or integrations |
| Works with | Federates with or shares to the warehouse through zero copy | Often fed by the warehouse | The system of record for analytics |
| Pricing model | Consumption credits or profile-based plans | Varies by vendor | Usually compute and storage consumption |
Data 360 rows reflect Salesforce documentation as of October 2026. CDP and warehouse rows describe the typical category, not a specific vendor.
Is Data 360 Right For Your Company?
Data 360 fits if customer data that would change a decision lives outside your CRM (in a web store, product database, billing system, warehouse or a second Salesforce org), you plan to use Agentforce, or marketing needs segments built on behavior. It fits best when you can name the first use case and the metric it should move.
Wait, or fix the basics first, if your CRM data is unreliable, no one can own the program, or the goal is simply "a single view of the customer" with no action attached. Data 360 is not supported on Professional Edition or in Government Cloud, so check your edition before you plan anything.
Edition and licensing are worth checking early. Salesforce provisions Data 360 automatically on any production org that receives a Data 360 licence (Developer editions excepted). Salesforce also lets customers provision it for free with limited storage and credits, and companies on Salesforce Foundations already have access ready to activate. That makes a small proof of value cheaper than many teams expect.
How To Get Started With Data 360: Five Steps
Start with one owner, one use case and one metric, decide where Data 360 will live, then model only the data that use case needs. Scale once you know what the first use case returned and what it cost in credits. The five steps below are the sequence we recommend to growing and mid-market companies.


Three questions keep the whole program on course: which data needs to be in Data 360, how it needs to be harmonized and unified, and which action it should drive, and why. If a data stream does not serve an answer to the third question, leave it out for now.
Which Metrics Prove Data 360 Is Working?
Measure Data 360 at three levels: whether the data foundation is healthy, whether people and processes use it, and whether a business number moved. Pick two or three metrics that match your first use case, record a baseline before go-live, and add consumption so value is always read against cost.
| Category | Example metrics | What it tells you |
|---|---|---|
| Data quality | Sources integrated; share of records without errors or duplicates; time for new data to appear | Whether the foundation can be trusted |
| Adoption | Active users; time to train; user satisfaction | Whether teams actually work from unified data |
| Business KPIs | Customer lifetime value; segmentation effectiveness; retention rate | Whether customer outcomes improved |
| Marketing | Campaign ROI; lead conversion rate; engagement rates | Whether personalization is paying off |
| Efficiency | Query time; uptime; hours or cost saved | Whether work got faster or cheaper |
| Security | Share of data meeting GDPR, CCPA or other rules; security incidents | Whether governance keeps up with scale |
| Cost to serve | Credits consumed per use case and per usage type | Whether value outpaces consumption |

How Does Data 360 Pricing Work?
Data 360 is consumption-priced: you spend credits for the processing you use, not per user. Salesforce offers credit-based plans (Flex Credits) and profile-based plans priced per thousand profiles. Bringing data in is free, while streaming, transforms, unification, queries, segmentation, activation and unstructured processing consume credits.
| Credit type | What it covers | Good to know |
|---|---|---|
| Flex Credits | Interchangeable across Data 360, Agentforce and other features | Requires Salesforce Foundations; multipliers drop through four monthly volume tiers that reset each month |
| Data Services Credits | Data 360 only, across 21 usage types | Still found in existing contracts; switching to Flex Credits means re-contracting once they are used up |
| Per-profile plans | Profiles or Enterprise Profiles, each with included credits and allowances | Gives more predictable spend when profile counts are known |
The levers Salesforce itself recommends are architecture choices: prefer batch over streaming where minutes do not matter, bring in only relevant data, process less often, and deactivate segments nobody uses. Ingesting from your Salesforce org through the CRM connector consumes no credits, every identity resolution ruleset adds to usage, and even previewing a transform runs billable queries. In a multi-org setup, companion-org activity is billed to the home org. Check current rates on Salesforce's Data 360 pricing page and the credit consumption module on Trailhead.
Where Data 360 Implementations Go Wrong
Most Data 360 problems are design decisions made early and discovered late, once data is already flowing and credits are already being spent. These are the ones we see most often.
How Twopir Implements Data 360
We implement, rescue, optimize, and integrate complex CRM and revenue systems, and Data 360 is where those disciplines meet. At Twopir Consulting we architect before we configure: every engagement starts with a source inventory, the first use cases, identity fragmentation and a twelve-month consumption projection, because the expensive decisions in Data 360 are invisible until data is already flowing.
We design across what we call the three Cs: consistency (a data model and identity rules built for activation and tested on a representative sample of your real records), connectivity (ingestion, zero copy and integrations, including MuleSoft where it fits) and cost (ingestion modes, refresh cadences and activation rules set as governance from week one). Our engagement model runs Assess, Model, Build, Hand over, and a typical engagement takes 8 to 16 weeks. With 12+ years of Salesforce delivery, we build Data 360 for what sits on top of it: Agentforce, Marketing Cloud Next and analytics. See our Salesforce Data 360 implementation services for the full scope.
Find Your First Data 360 Use Case, And What It Will Cost To Run
A 30-minute discovery call with a Twopir Salesforce architect maps where your customer data lives, which use case would pay back first, and which design choices will drive your credit consumption, before anything is switched on.
Schedule a Discovery CallThe Bottom Line
Data 360 finally makes the oldest CRM problem solvable: customer data scattered across systems, now unified and usable where work happens. Salesforce is also building more and more of its platform on it, Agentforce first among them, so it is becoming hard to avoid. But it is a strong investment only when an organization can show a return. Start with a use case you can measure, design for the credits it will consume, and scale on evidence.
- 1
Data 360 is Data Cloud, renamed on October 14, 2025, with the same functionality; expect "Data Cloud" labels in setup and permission sets for some time.
- 2
It works in four stages: connect, harmonize to the Customer 360 Data Model, unify through identity resolution, and act through insights, segments, flows, analytics and agents.
- 3
Agentforce requires Data 360 to be provisioned; agents grounded in unified profiles require it to be implemented.
- 4
Pricing is consumption-based, so ingestion modes, refresh cadence, identity rulesets and the home org are cost decisions as much as technical ones.
- 5
Name one owner, one use case and one metric, then scale only after you have measured the result and the credit burn.
Frequently Asked Questions
Yes. Salesforce rebranded Data Cloud to Data 360 on October 14, 2025, and states that the functionality is unchanged. Some screens, documentation, permission sets and features still use the Data Cloud name, such as Data Cloud Setup and Data Cloud-Triggered Flows.
Data 360 must be provisioned and enabled for any Agentforce use, and features such as the Agentforce Data Library and the Einstein Trust Layer depend on it. To ground agents in unified customer profiles, real-time data and your own documents, Data 360 also needs to be implemented, with data connected, mapped and unified.
Data 360 is consumption-priced. Salesforce offers credit-based plans using Flex Credits and profile-based plans priced per thousand profiles, and existing contracts may use Data Services Credits. Bringing data in is free; processing, queries, segmentation and activation consume credits. Customers can also provision it for free with limited storage and credits.
Data 360 is not supported on Professional Edition orgs or in Government Cloud. It is provisioned automatically on a production org that receives a Data 360 licence, except Developer editions. Salesforce Foundations, which runs on Enterprise, Performance, Unlimited and Developer editions, includes Data 360 access.
Often yes, because they do different jobs. The warehouse stores and analyzes company data, while Data 360 unifies customer profiles and acts on them inside Salesforce. Zero copy federation lets Data 360 use warehouse data without copying it, and zero copy sharing lets the warehouse read unified profiles back.
Salesforce does not publish a standard timeline, because scope depends on the number of sources, data quality and use cases. A typical Twopir Data 360 engagement takes 8 to 16 weeks, running assess, model, build and hand over around a first use case before scaling.
Identity resolution links records about the same person or account into a unified profile. Match rules decide which records belong together, using exact, fuzzy or normalized matching, and reconciliation rules decide which value wins, by recency, frequency or source priority. Each ruleset adds to billable usage.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. Our Salesforce practice covers Data 360, Agentforce, Sales Cloud, Service Cloud and Marketing Cloud, with integration work on MuleSoft, Workato and Celigo, for clients across the US, UK, Australia, UAE and Canada.