Data 360

What do you like best about the product?

The ability to create connections in a multi-tenant instance is amazing and helps with data visibility and metrics.

What do you dislike about the product?

Some of the updates that slide us backwards because it doesn't feel as if it's been full tested.

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

The ability to see, share, and make informed decisions across our enterprise.

What do you like best about the product?

Zero-copy connections, along with using DMOs in Salesforce internal automations, have made my life a lot easier.

What do you dislike about the product?

The credit consultation calculations are a bit hard to understand, and every time we plan a project we need to spend quite a bit of time beforehand figuring them out.

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

Once again, we’re using DataCloud primarily for agent/model training. This is new for us—we didn’t have this before—and it’s helping us make better use of the AI capabilities in our CRM. We’re also planning to use it for identity resolution.

What do you like best about the product?

It solves the technological gap we had in our data: we sometimes aren’t able to define a „golden record“ but rather need to manage multiple existing realities into one managed individual.

What do you dislike about the product?

I think matching rules and how an individual gets unified could be more transparent

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

Bridging a technological gap we had in our data: sometimes there‘s no „one reality“ or golden record

What do you like best about the product?

It is a real-time data engine and customer data platform built directly into the Salesforce ecosystem

What do you dislike about the product?

It contains high costs, difficult initial setup and rigid data models

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

real-time data engine and customer data platform built directly into the Salesforce ecosystem

What do you like best about the product?

It’s very easy to use and also very easy to integrate. We use Data 360 embedded in Agentofrce, and it has allowed us to deliver much better performance by improving Agentofrce’s context.

What do you dislike about the product?

I think overall it is a very easy to use, and useful product

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

It is providing context to our agentforce implementation.

What do you like best about the product?

It lets me manage data consistently across multiple source systems without having to move it.

What do you dislike about the product?

It can feel complex, depending on the specific use case.

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

Profile unification and activation for use in Salesforce and Agentforce.

What do you like best about the product?

We like the potential of Data 360 to bring customer and prospect data from multiple systems into a more unified view. As we evaluate it, the ability to improve audience segmentation, data quality, and personalized engagement across Salesforce and marketing platforms is especially appealing.

What do you dislike about the product?

Because we are still evaluating Data 360, the main concern is the complexity of implementation. It requires clear data governance, thoughtful integration planning, and a strong understanding of usage-based costs before we can determine the full value for our organization.

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

We are evaluating Data 360 to address fragmented customer and prospect data across systems. It could help create more complete customer profiles, improve audience segmentation and data quality, and support more relevant, personalized marketing and sales engagement.

What do you like best about the product?

Ability to bring together data from multiple systems and report on it in one easy place.

What do you dislike about the product?

The preset Id mapping that is incorrect in transformations

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

Multiple systems not all on Salesforce and how best to get a single view of the customer

What do you like best about the product?

What I like most about Data 360 is that it addresses one of the most persistent problems I’ve encountered in Salesforce architecture: everyone wants a 360-degree view of the customer, but the data rarely lives in one place.

I’ve worked with environments where different Salesforce orgs and external systems each hold a piece of the customer journey. What I find particularly powerful about Data 360 is the ability to connect those pieces without forcing the entire enterprise to consolidate onto a single system.

As an architect, I also like that it goes beyond data consolidation. Once data is unified, I can think about how to activate it—feeding it into Sales, Service, Agentforce, Marketing, analytics, or downstream processes. That makes Data 360 feel less like another data platform and more like an intelligence layer connecting the enterprise to the Salesforce ecosystem.

That shift—from simply integrating data to making it contextual, actionable, and available at the point of decision—is what makes Data 360 particularly interesting to me.

What do you dislike about the product?

What I find most challenging about Data 360 is that the promise of a unified customer view can be much easier than achieving it in a real enterprise environment.

In the multi-org and integration architectures I’ve worked with, the complexity often sits upstream—data quality, identity resolution, conflicting customer identifiers, inconsistent data models, and real-time vs. batch requirements. Data 360 can bring the data together, but it doesn’t eliminate those underlying architecture problems; in some cases, it makes them more visible.

I also find the platform can have a steep learning curve. Understanding ingestion, data modeling, identity resolution, calculated insights, activation, governance, and consumption patterns requires a fairly broad skill set. I’d like to see more simplicity around end-to-end lineage, troubleshooting, cost/consumption visibility, and managing complex multi-org implementations.

For me, the biggest opportunity is making Data 360 easier to operate at enterprise scale without requiring architects and data teams to understand so many underlying platform concepts.

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

For me, Data 360 is solving a problem I’ve encountered repeatedly in enterprise Salesforce architecture: customer data is fragmented across Salesforce orgs, legacy systems, data warehouses, and external applications, while the business still expects a single, trusted view of the customer.

The value is that I can connect and harmonize those different data sources without requiring the entire enterprise to move onto Salesforce. Identity resolution and a common data model help turn fragmented records into a more meaningful customer profile, while real-time data and activation make that information usable by Sales, Service, Marketing, Agentforce, and other channels.

The biggest benefit for me as an architect is that it changes the conversation from “How do we integrate these systems?” to “What can we do with the unified data?”. It gives me a foundation for building more contextual experiences, better segmentation and insights, and AI-driven use cases while reducing the need to replicate customer data across multiple systems.

What do you like best about the product?

It helps me organize my core data effectively

What do you dislike about the product?

There is nothing that I dislike about this product.

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

Keeping track of my core data within the platform