Data 360

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

What do you like best about the product?

I like that you don't have to have all of your data in one place and it doesn't have to be formatted the same in order to be utilized. Data360 is able to harmonize the data to be used in Salesforce like it was formatted specifically for our needs from the jump.

What do you dislike about the product?

It takes some time to get set up right, but really, if that is the biggest problem, Data 360 is doing it right!

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

Admittedly, my experience with Data 360 is quite limited, but from what I have used, it was able to harmonize the data and that's all you can ask for as that is what its supposed to do.

What do you like best about the product?

Data 360 is native to Salesforce, which makes it easier to use than connecting another API to our org.

What do you dislike about the product?

Requires a higher level of technical skills to manage, versus what a standard Administrator is capable of- which can add to the cost if you need a partner to config for you.

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

Having all of our data in one place has been really helpful. We previously had multiple systems that weren’t connected, but now everything is unified in a single space for us, which makes it much easier to work with.