Data 360, the product Salesforce previously called Data Cloud, sits underneath much of its AI strategy. Agents need accurate customer data, and Data 360 is where Salesforce wants that data to be unified, segmented and activated. Because it is priced by consumption rather than by user, it is also one of the harder Salesforce products to forecast.
This article explains the current Data 360 pricing options, how credits are consumed, and the steps that help organisations keep Data 360 costs predictable.
We also cover who should own Data 360 spending, and the contract terms worth agreeing before you commit.
Three ways to buy Salesforce Data 360
Salesforce’s Data 360 pricing page sets out two current pricing models alongside the older Data Services model. The first is Flex Credits, priced at $500 per 100,000 credits, which can be used for any Data 360 action and bought on a pre-purchase, pay-as-you-go or pre-commit basis.
The second is profile-based pricing. Profiles are listed at $240 per 1,000 profiles per year and include one Flex Credit per profile, while Enterprise Profiles are listed at $420 per 1,000 profiles per year with two credits per profile and additional actions included. Profile-based pricing bundles common profile-building actions into a flat cost, while Flex Credits are still used for other work such as querying data or processing unstructured data for AI agents.
Customers on the older Data Services credit model can stay on it. Salesforce says there is no forced migration, but if you want to move to Flex Credits or profile pricing, you need to swap all of your existing Data Services credits.
How Data 360 credits are consumed
Every Data 360 action consumes credits at a rate set out in Salesforce’s Flex Credits rate card. The rate depends on the type of usage, such as data preparation, unification, segmentation, activation or queries, and the unit is usually a million rows processed.
The rate card also uses volume tiers. In production, the multiplier for each usage type falls as your consumption rises through defined bands, starting with a base tier for the first 300,000 credits. A separate multiplier applies to sandboxes and other pre-production environments, so testing is not free.
One rule matters for budgeting: credits must be used before the order end date shown on your order form, and there is no rollover. Buying more than you need is therefore a direct cost, not a reserve for next year. Under the current Flex Credits and profile models, ingestion is listed as free, so most consumption comes from what you do with the data once it is in Data 360.
Because the multipliers differ so widely between usage types, two organisations with similar data volumes can have very different bills. One that mainly runs queries may consume relatively few credits, while one that runs frequent unification and segmentation across large data sets may consume many times more. Understanding your own mix is therefore more useful than comparing totals with other companies.
Data 360 Flex Credits shared with Agentforce
Flex Credits are not limited to Data 360. Salesforce allows them to be transferred between Data 360 and Agentforce, which means a single pool can fund both data processing and agent actions. That flexibility is useful, but it also means one team’s heavy usage can drain capacity another team was relying on.
The new Salesforce editions add to this. Futurum Research’s analysis of the September 2026 editions notes that Flex Credit allocations scale by tier, with 500,000 for Core, 1 million for Advanced and 2.75 million for Max.
As Subscription Insider pointed out, those allocations are per organisation per year. A large enterprise and a small team on the same edition receive the same pool, so the allocation will go much further in some organisations than in others.
We cover the edition changes in more depth in our article on Salesforce retiring Enterprise and Unlimited.
Why Data 360 usage is growing quickly
Data 360 volumes are rising fast across Salesforce’s customer base. In its fiscal 2026 results, Salesforce reported that Data 360 ingested 112 trillion records during the year, including 53 trillion through Zero Copy, and that annual recurring revenue across Agentforce and Data 360 exceeded $2.9 billion.
Those numbers show how central Data 360 has become, and they also explain why consumption can surprise customers. As more agents and processes depend on unified data, the same data is segmented, queried and activated more often. Each of those steps consumes credits.
Zero Copy, which lets Data 360 work with data held in external platforms without moving it, can reduce ingestion and storage, but queries and processing still have a cost. Understanding which actions run, how often and against how much data is the key to understanding the bill.
Data 360 Flex Credits vs profile-based pricing
Profile-based pricing suits organisations whose main use of Data 360 is building and maintaining unified customer profiles for marketing or service, where the number of profiles is known and stable. The flat cost makes budgeting simpler, and common profile actions are included.
Flex Credits suit organisations with variable or broader usage, especially those that also use Agentforce and want one pool to cover both. They offer more flexibility but require more active monitoring.
Whichever you choose, model it against your real data volumes. Salesforce provides a pricing calculator, and your account team can produce an estimate, but the most reliable forecast comes from a period of measured usage in your own environment.
How to control Data 360 costs
A few habits make a significant difference to Data 360 costs. Keep segments focused and avoid unnecessarily long look-back windows, because processing more rows than needed increases consumption without improving results. Review scheduled jobs regularly and switch off any that no longer serve a purpose.
Use the Digital Wallet and consumption reports to see which usage types and which teams consume the most. Set alerts so that unusual spikes are investigated quickly. Agree internally who can create new data streams, calculated insights and activations, since each one adds ongoing consumption.
Finally, remember the sandbox multiplier. Development and testing consume credits too, so build test data sets that are large enough to be useful but no larger.
Data 360 contract terms to agree
Because Data 360 is consumption-based, contract terms matter as much as price. Confirm which rate card your order form refers to and whether multipliers can change during the term. Check the order end date for your credits and plan usage around it.
If you are moving from Data Services credits to Flex Credits or profiles, ask for a comparison based on your actual usage over a recent period, not on a generic example. Some usage types are cheaper under the new model and some are not, so the overall effect depends on your mix.
If you are committing to a large volume, ask for flexibility, such as the ability to apply unused credits to other products or to adjust the commitment at renewal if usage is lower than forecast.
If you would like an independent view of your Data 360 commitment, our Salesforce licence optimisation services include consumption reviews and renewal support.
Data 360 cost example
Consider an organisation that builds a weekly marketing segment across a large customer base. If the segment looks back over three years of engagement data when one year would give the same result, each run processes far more rows than necessary. Repeated every week, that difference compounds into a significant share of the annual credit pool.
The same organisation might also have calculated insights scheduled to refresh daily when weekly would be enough, and old data streams that nobody uses but that still run. None of these choices is unusual, and none is visible on a pricing page. They only show up in consumption reports.
This is why regular reviews matter. A quarterly look at the largest consumers of credits often finds savings that require no change to what the business actually receives.
Who should own Data 360 spending
Because Data 360 is consumption-based and shared across teams, ownership is often unclear. Marketing may build segments, service may rely on unified profiles, data teams may manage pipelines and AI projects may draw on the same credit pool. When nobody owns the total, costs can rise without anyone noticing until the credits run out.
A practical approach is to give one person or team overall accountability for the Data 360 budget, supported by a simple allocation of consumption to the teams that drive it. Consumption reports can show which usage types are growing, and regular reviews can link that growth to specific projects.
Some organisations go further and set internal budgets for each team, with alerts when a team approaches its share. This encourages teams to think about the cost of new segments, insights and activations before they create them, rather than after.
Ownership also matters at renewal. The person accountable for Data 360 spending should be involved in sizing any new commitment, because they will understand both past consumption and planned projects. Without that input, commitments tend to be based on vendor estimates rather than real plans.
Clear ownership does not need to slow anything down. It simply ensures that someone is watching the total and can explain where the credits are going.
Salesforce Data 360 pricing FAQs
What is Salesforce Data 360? It is the current name for the product previously called Data Cloud, which Salesforce uses to unify, segment and activate customer data across its platform.
How much do Data 360 Flex Credits cost? Salesforce lists Flex Credits at $500 per 100,000 credits. Profile-based plans are listed at $240 or $420 per 1,000 profiles per year, depending on the tier.
Is data ingestion charged? Under the current Flex Credits and profile-based models, Salesforce lists ingestion as free. Other actions, such as unification, segmentation, activation and queries, consume credits.
Do I have to move off Data Services credits? No. Salesforce says there is no forced migration, although moving to Flex Credits or profiles requires swapping all existing Data Services credits.
Can Data 360 credits be used for Agentforce? Yes. Salesforce allows Flex Credits to be transferred between Data 360 and Agentforce, so one pool can fund both data processing and agent actions.
Do sandboxes consume Data 360 credits? Yes. Salesforce’s rate card applies a separate multiplier to sandboxes and other pre-production environments, so development and testing consume credits as well as production.
Conclusion
Data 360 is now central to how Salesforce delivers AI, and its consumption-based pricing reflects that. Flex Credits, profile-based plans and legacy Data Services credits each have their place, but none of them is predictable without good monitoring and a clear understanding of how credits are consumed.
Measure before you commit, keep segments and jobs under review, decide who controls the shared credit pool, and make sure your contract terms match how your usage really behaves. That approach keeps Data 360 valuable without letting its costs drift.
If you would like independent advice on Data 360 or your wider Salesforce agreement, get in touch with 2Data.