Data 360 (formerly Salesforce Data Cloud) Reviews & Product Details

What I like best about Data 360 (formerly Data Cloud) is the direct connection it gives us to live account metrics. Replacing the Boomi pipeline with a direct Databricks to Data Cloud connection means the data feeding my dashboards and account metrics isn't sitting in a batch pipeline with lag and translation risk between systems. It's a more direct path from source data to something I can actually build on.

For my work specifically, that matters because I'm the one accountable for whether the numbers in things like account metrics and pipeline reporting are right. A cleaner, more direct pipeline means fewer hours spent chasing down why a number looks off, and more confidence handing that data off to stakeholders across Lyft Ads, churn alerts, and Tableau Next. Review collected by and hosted on G2.com.

My biggest frustration with Data 360 (formerly Data Cloud) is that migrating off our old integration pipeline has surfaced real reliability issues rather than solving cleanliness outright. The Calculated Insights timezone bug, where UTC gets read as EDT and skews time-bounded metrics, is a good example: it's exactly the kind of subtle data integrity problem I'm accountable for catching before it hits a dashboard or a stakeholder.

With this many stakeholders depending on the same pipeline (Lyft Ads, churn alerts, bidirectional sync, Tableau Next), a bug like that doesn't stay contained. It becomes a blocker across multiple workstreams at once, and I end up debugging platform-level data issues instead of doing the account/pricing work that's actually my job. Review collected by and hosted on G2.com.

What I like most is its ability to unify disparate customer data sources into a single, real-time Customer 360 profile. The Zero-Copy feature with data warehouses like Snowflake and BigQuery is a game-changer because it allows querying data without complex ETL pipelines. Additionally, it serves as a strong data foundation to power AI agents across the Salesforce ecosystem. Review collected by and hosted on G2.com.

The platform has a steep learning curve and requires significant architecture planning for identity resolution and data modeling. The consumption-based credit system (Flex Credits) can make costs unpredictable, and debugging failed data ingestion flows or deleting old datasets can be challenging for administrators. Review collected by and hosted on G2.com.

It unifies customer data from multiple sources into a single profile, giving cross functional teams the information they need to be successful. Connects natively with other Salesforce products, offering seamless data flows. Reduces the need to source 3rd party solutions to do this heavy lifting, and allowing the system to function as a suite. Review collected by and hosted on G2.com.

It’s understandably complex - but the hidden cost is ensuring you have the right resourcing during implementation to get it right from the start. As your business scales - so does the volume of data, which increases pricing models. Meticulous data management is critical - if it’s not strictly governed, there is a “garbage in, garbage out” vibe that will eliminate any ROI in the investment in it. Review collected by and hosted on G2.com.

We recently implemented Data 360, and it has completely transformed how we bring our customer data together. The standout features for us so far are the identity resolution and unified customer profiles. Being able to connect fragmented touchpoints across our CRM and web activity into a single, cohesive view without massive manual data wrangling has been incredible. The real-time ingestion and direct integration back into our broader Salesforce ecosystem make activating segments for marketing campaigns faster and far more targeted than anything we could do previously. Review collected by and hosted on G2.com.

There is a noticeable learning curve when first getting started. Mapping data models and understanding the credits/consumption model can feel overwhelming without dedicated onboarding or guidance. It takes careful upfront architecture to ensure data streams are aligned properly, and the administrative documentation could be slightly more beginner-friendly for teams new to enterprise CDPs. Review collected by and hosted on G2.com.

What I like best is the ability to bring data from across the organization together and make it actionable inside Salesforce. For nonprofits and associations especially, that creates a huge opportunity to better understand members, donors, and constituents and use that data to drive more personalized engagement, better decisions, and ultimately greater impact. Review collected by and hosted on G2.com.

The value proposition can still feel more complicated than it needs to be. Between consumption-based pricing, implementation complexity, and understanding which use cases truly require Data 360, it can be difficult for organizations to predict cost and clearly articulate ROI. I’d like to see simpler packaging, more predictable pricing, and clearer paths to value, particularly for nonprofits and associations. Review collected by and hosted on G2.com.

What I like best about Data 360 is its ability to bring data from multiple sources together and create a unified, real-time view of the customer and business data. It makes it easier to connect Salesforce with external systems, activate data across different clouds, and use trusted data for analytics, automation, and AI. This reduces data silos and helps teams make faster, more informed decisions. Review collected by and hosted on G2.com.

One challenge with Data 360 is the overall complexity of setup, data modeling, and integration, especially when working with multiple external data sources. Understanding data ingestion, identity resolution, mappings, and usage-based consumption can take time. I would like to see simpler configuration, clearer monitoring and troubleshooting tools, and more transparent cost and usage visibility. Review collected by and hosted on G2.com.

What I like best about Data 360 is its ability to unify customer data from multiple systems into a single, trusted customer view. As a Salesforce Business Analyst, having a centralized source of customer, sales, service, and operational data helps eliminate silos and provides greater visibility for both business users and leadership.

I also appreciate how closely it integrates with the Salesforce ecosystem. Data can be activated directly within Salesforce applications to support reporting, segmentation, automation, and AI-driven insights, making it easier to turn data into action.

Recent enhancements have made the platform even more valuable, including improved data connectivity, simplified CRM data onboarding, stronger identity resolution capabilities, expanded Zero Copy integrations, and AI-powered features that help organizations gain insights faster and create more personalized customer experiences. These ongoing innovations continue to strengthen Data 360 as a core foundation for customer intelligence and AI initiatives. Review collected by and hosted on G2.com.

While Data 360 is a powerful platform, the biggest challenge is its complexity and learning curve. Concepts such as data modeling, identity resolution, calculated insights, and data governance can be difficult for new administrators and business users to fully understand, especially during initial implementation.

The platform also requires significant planning and data quality management to deliver maximum value. Organizations with multiple source systems may need additional effort to standardize data and establish governance processes before they can fully leverage advanced capabilities.

Another area for improvement is pricing and scalability. While the platform offers extensive functionality, licensing and data consumption considerations can make it difficult for some organizations to quickly expand usage across the enterprise.

That said, Salesforce has made meaningful improvements through recent releases by simplifying CRM data onboarding, expanding integration options, enhancing identity resolution capabilities, and introducing more user-friendly AI and analytics features. These updates have helped reduce some of the complexity, but there is still room to make implementation and administration more accessible for business teams without specialized expertise. Review collected by and hosted on G2.com.

I implement Data 360 for clients as a consultant, mostly in setups where Marketing Cloud Engagement is the activation layer. The biggest win for me is identity resolution. Getting a single unified profile across Contacts, Leads and Individuals is something we used to solve with fragile custom middleware, and now it is configuration. Once the match and reconciliation rules are dialed in, the Unified Individual becomes a genuinely reliable source of truth.

The second thing is consent. Being able to model ContactPointEmail and Contact Point Consent properly, and then use that as a base filter in segmentation, means GDPR compliance is built into the data layer instead of being patched together per campaign. That has saved a lot of nervous conversations with clients.

Native activation into Marketing Cloud Engagement is also a big plus. No custom sync jobs, no middleware to maintain. Review collected by and hosted on G2.com.

The learning curve is steep, and not only for the usual reasons. The data model has several abstraction layers (data streams, DLOs, DMOs, data graphs) and teams coming from core Salesforce often underestimate how different the thinking is. Budget real ramp-up time.

Identity resolution is powerful but unforgiving. A single misconfigured source in a reconciliation rule can quietly break email on the unified profile, and debugging why a profile looks wrong is harder than it should be. Better tooling for tracing how a unified record was assembled would help a lot.

Smaller friction points add up too: the 40-character field name limit forces awkward renaming, and some segment filters require exact text matches with little feedback when you get it wrong.

Finally, the naming. Data Cloud to Data 360 is the latest in a long line of renames, and documentation and community content lag behind every time. Review collected by and hosted on G2.com.

It’s the best way I’ve found to unify customer records without losing data. It handles whatever sources you connect to it, can work with zero copy, and it’s been improving month after month. Review collected by and hosted on G2.com.

It’s not very user-friendly. The first few times you use it, it’s easy to do things wrong, and mistakes on this platform can cost you a lot. Review collected by and hosted on G2.com.

As a strategist who recently built an award-winning autonomous AI agent for healthcare compliance (the MediComm Regulatory Auditor), what I value most about Data 360 is its foundational capability to harmonize structured and unstructured data. It provides the secure, unified data layer required to implement Knowledge RAG effectively, ensuring our AI models have access to grounded, accurate regulatory guidelines without the risk of hallucinations Review collected by and hosted on G2.com.

Because it is the foundational data engine for enterprise AI, the complexity of initial data ingestion and mapping can be a significant hurdle. Connecting disparate legacy systems and defining the rules for data harmonization requires dedicated data architects and a deep understanding of your organization's data governance. It is a powerful engine, but it is not a lightweight integration Review collected by and hosted on G2.com.