Data 360 Tools

External data lakes, visualized.

Your customer data already lives in a data lake such as Snowflake or Databricks. Salesforce Data 360 (formerly Data Cloud) can copy it, query it where it lives, or read its files directly. Here's what each option actually does.

Choose an option to see what's involved and how the data moves:

External data lake such as Snowflake or Databricks
ComputeThe lake's query engine
StorageOrder history tables, stored as files
Data 360
Stored copyA full copy, refreshed on each sync
CacheA temporary copy, refreshed incrementally
Data modelHarmonized objects: the same either way
Segments · Identity resolution · AgentsEverything that uses the data

In use involved in this option · Faded not used

↑ Back to top

You choose per data stream, not per data lake. One lake can feed a heavily used loyalty table through acceleration and a rarely used archive through query federation.

↑ Back to top

The rule of thumb: federation pays for every row, every time it's read. Copying pays for each row once, plus changes. So the question is how many times each row gets read, and how often it changes. Query federation also runs on the lake's compute, which is billed separately. Answer five questions about one table.

Credit rates change over time and vary by contract. The comparisons below are relative, not quotes. Consult your contract for current rates.

Credit consumption rates change. Consult your Salesforce contract for current rates. The relative costs here are based on Salesforce's published list rates as of 2026 (pricing example, zero copy lessons, decision guide). A starting point, not a quote: rates vary by contract, and the lake's compute is billed separately. Model both sides with real query volumes.

↑ Back to top

Zero copy works both ways. Data 360 can also share unified profiles, segments, and insights back to the lake without copying them, so the data team works with the same results.

Harmonization protects you from lake changes. Whatever the option, the data maps onto Data 360's data model before segments or agents use it. If a team renames a column in the lake, you fix one mapping instead of every segment. See data harmonization, visualized →

↑ Back to top

Simplified for learning, and capabilities change often: check current documentation for your platform. An independent tool, not affiliated with Salesforce. More Data 360 tools