Data 360

What do you like best about the product?

A native way to bring together all relevant data in an organisation.

What do you dislike about the product?

It still does not feel like a completely stable product, too much change.

What problems is the product solving and how is that benefiting you?

It enables my organisation to bring together data from external sources, create unique entities via identity resolution, and use this data in Salesforce

What do you like best about the product?

What I like most about Data 360 is how it brings data from different sources together and makes it usable inside the Salesforce platform. The ability to unify customer data and apply it across Salesforce opens up a lot of possibilities for segmentation, automation, analytics, and AI.

I also appreciate how tightly Data 360 fits into the broader Salesforce ecosystem. For organizations that have already made a significant investment in Salesforce, being able to work with external data without having to move or duplicate all of it can be especially valuable. And as Salesforce continues to expand its AI capabilities, I expect Data 360 to become even more important as the data foundation behind those solutions.

What do you dislike about the product?

The biggest challenge with Data 360 is the learning curve. Even for someone very familiar with Salesforce, there are many new concepts, terms, and tools to absorb. Data modeling, data streams, identity resolution, calculated insights, and the various ways data can be accessed and activated all take time to understand and feel comfortable using.

It can also be hard to gauge the potential cost and consumption implications of a solution. Since usage can vary significantly depending on the architecture and the specific use case, administrators and architects need to be deliberate in how they design and implement solutions, rather than approaching Data 360 the same way they might approach functionality on the core Salesforce platform.

What problems is the product solving and how is that benefiting you?

Data 360 helps solve the challenge of customer data being scattered across multiple systems and applications. By bringing that information together and making it accessible within Salesforce, it creates a more complete view of the customer without forcing users to jump between different tools.

The biggest benefit is having the data available where users and business processes already operate. This can enable stronger segmentation, clearer reporting, more effective automation, and more personalized customer experiences. It also lays an important foundation for Salesforce’s AI capabilities by giving AI access to a broader, more unified set of business and customer data.

What do you like best about the product?

Helps aggregate and clean our data before we run analytics on it. Allows us to centralize data from multiple sources

What do you dislike about the product?

Setting up data streams with outside sites can be challenging, especially for data from our websites.

What problems is the product solving and how is that benefiting you?

Cleaning outside data so SF AI and other tools can combine outside data with Salesforce data.

What do you like best about the product?

Data 360 seamlessly brings together disparate data from across our entire tech stack into a single, standardized Customer 360 profile, helping break down legacy silos without requiring complex, manual ETL work. Its Zero Copy architecture allows us to access and analyze our external data warehouse, Snowflake, directly within Salesforce. As a result, we avoid data duplication, reduce storage costs, and keep our data pipelines lightweight and easier to manage. With both structured and unstructured data fully integrated inside Data 360, we get immediate contextual grounding for Agentforce and automated workflows, which supports more precise and reliable AI-driven customer interactions. Overall, it strengthens the data feeding into our Agentforce Service and Coworker processes.

What do you dislike about the product?

Configuring Data Spaces, identity resolution rules, and data model objects (DMOs) often requires significant specialized expertise. Administering and maintaining these mapping structures can also be more time-consuming than working with traditional core Salesforce objects. The consumption-based credit model may make quarterly and annual forecasting less predictable, since heavy data ingestion, frequent identity resolution runs, or complex calculated insights can burn through credits much faster than initially expected. Troubleshooting issues across data ingestion pipelines, identity resolution, or flow integrations can be difficult as well. Error messages and audit logs are sometimes opaque, so pinpointing the root cause of sync failures can become a labor-intensive process.

What problems is the product solving and how is that benefiting you?

Siloed Data Across Systems
Problem: Customer data was fragmented across separate platforms, which led to incomplete customer records and duplicated effort across teams.
Benefit: Unifies cross-platform data into a single source of truth within Salesforce, giving teams immediate visibility into complete, up-to-date customer profiles.

Slow, Resource-Heavy Integrations
Problem: Moving data between warehouses and the CRM required custom ETL pipelines that were slow to build, brittle to change, and time-consuming to maintain.
Benefit: Zero Copy architecture and direct data connectors reduce heavy data replication, saving engineering hours and lowering ongoing storage overhead.

Inaccurate or Un-grounded AI Responses
Problem: AI agents and subagents can hallucinate or miss key context when they can’t securely access real-time enterprise data.
Benefit: Grounds Agentforce and automated flows in unified, real-time context, enabling more reliable service automation and more personalized customer interactions.

What do you like best about the product?

I like that it lets me consume large amounts of data from different systems. I like the advanced tools it gives me for mapping data.

What do you dislike about the product?

There’s no native way to support migration from other systems, such as CRM Analytics, which makes adoption harder. On top of that, the required skill set is different, and this has made it difficult for some legacy CRM Analytics users to migrate smoothly.

What problems is the product solving and how is that benefiting you?

It allows us to map data from different systems into a single system of record. So far, adoption has been low, with cost being a factor. It’s a great tool with vector search, but we haven’t seen any benefits yet.