Salesforce Data Cloud Licensing: How the Model Works in 2026

From Data Cloud to Data 360: What Changed

In October 2025, Salesforce rebranded Data Cloud as Data 360, placing it under the broader Agentforce 360 platform umbrella. This was more than a naming exercise. Data 360 now functions as the primary data layer powering Salesforce's AI agent infrastructure — it supplies real-time, unified customer and operational data to Agentforce agents across sales, service, marketing, and operations workflows.

For enterprise licensing buyers, the rebranding matters for two reasons. First, it signals that Salesforce intends Data 360 to become a required infrastructure component — not an optional analytics add-on — for any organisation deploying Agentforce at scale. Second, the March 2026 pricing overhaul introduced a completely restructured licensing framework, replacing the previous single-credit system with three co-existing models that must be understood independently before any purchase or renewal decision is made.

Understanding which licensing model governs your Data 360 deployment — and which model Salesforce's field team is proposing — is the first prerequisite for any cost governance conversation in 2026.

The Three Data 360 Licensing Models (March 2026 Onwards)

Effective March 2, 2026, Salesforce restructured Data 360 pricing into three distinct models. Customers signing new agreements or renewing existing ones must explicitly identify which model their contract uses, as the commercial implications differ significantly between each.

Model 1: Credit-Based Consumption

The original Data Cloud model, now consolidated and simplified. Under credit-based consumption, you purchase a pool of credits that are drawn down as your system performs specific data operations. Credits are purchased in packages of 100,000 at $500 per package — equivalent to $0.005 per credit. The pool is fungible: any credit can be used for any qualifying operation, though different operations consume credits at dramatically different rates.

The consolidated model replaced the previous structure where separate credit types existed for segmentation, activation, and data services. Salesforce merged these into a single pool in mid-2025, which simplified administration but did not reduce the underlying cost exposure. Unused credits do not roll over at year end unless you specifically negotiated rollover provisions — a critical contract term many customers omit.

Model 2: Profile-Based SKUs

The profile-based model prices Data 360 by the number of unified customer profiles managed within the platform rather than by operations performed. SKU pricing ranges from approximately $240 to $420 per 1,000 profiles annually, depending on volume tier and the level of AI capabilities included. This model is more predictable for organisations with stable, bounded customer data volumes but becomes expensive quickly for businesses with large or growing customer databases.

Profile-based SKUs are better suited to organisations whose primary Data 360 use case is audience management and activation — for example, marketing teams running segmentation and personalisation against a known customer base. Organisations using Data 360 primarily for real-time AI agent grounding, where the operational intensity is high but the profile volume may be modest, often find the credit model more cost-effective.

Model 3: Flex Credits

Introduced in May 2025 and incorporated into the March 2026 restructure, Flex Credits are the most strategically significant change to Data 360 licensing. Flex Credits are fungible units of consumption that can be used across Data 360, Agentforce, Slack, and other Salesforce services. Each unit of action within Agentforce consumes 20 Flex Credits at $0.10 per action, with packages priced at $500 for 100,000 credits — structurally mirroring the Data 360 credit pricing.

The significance of Flex Credits is that they create a shared pool across the Salesforce platform. An organisation that over-commits on Data 360 credits can redeploy unspent Flex Credits to Agentforce conversations. Conversely, unexpectedly high Agentforce usage can draw down a shared Flex Credit pool faster than anticipated, creating overages across Data 360 as well.

When modelling Flex Credit requirements, always include both Data 360 operations and Agentforce conversation volumes. Salesforce's Agentforce platform prices AI agent interactions at approximately $2 per conversation — each 24-hour agent session with a customer or employee counts as one conversation — and this consumption feeds into the same Flex Credit economy for organisations on the pooled model.

What Consumes Credits: The Operation Cost Hierarchy

One of the most important pieces of information for Data 360 licence governance is the relative cost of different operations. Not all Data 360 activities consume credits at the same rate. The disparity is significant enough that the mix of operations you perform — not just the volume of data — determines your total credit consumption.

Based on Salesforce's published documentation and analysis from Redress Compliance engagements, the approximate credit consumption hierarchy for major Data 360 operations is:

• Identity Resolution: 100,000 credits per million rows processed — the single most expensive operation in Data 360. Identity resolution matches and merges data from disparate sources into unified profiles. Many organisations run identity resolution repeatedly as new data arrives, creating ongoing credit consumption that compounds quickly.
• External Data Ingestion: approximately 2,000 credits per million rows — making it 50 times cheaper than identity resolution per row. Bringing in external (non-Salesforce) data is relatively affordable; it is what you do with that data after ingestion that drives cost.
• Segmentation and Activation: Credits vary by segment size and activation frequency. Historically priced separately before the 2025 consolidation, segmentation and activation are now drawn from the same pool and should be modelled based on your segment count and refresh schedule.
• AI Agent Grounding: When Agentforce agents query Data 360 for context to personalise responses, each grounding call consumes credits. High-volume customer service or sales deployments where agents handle thousands of conversations per day can generate substantial grounding credit consumption that is rarely accounted for in initial deployment models.
• Salesforce Native Data Ingestion: Bringing in structured data from other Salesforce products (Sales Cloud, Service Cloud, Marketing Cloud) is now free under the simplified 2025 model. This is a genuine improvement over the previous pricing structure and a lever buyers can use to reduce overall credit consumption by maximising Salesforce-native data usage before pulling from external sources.

The AELA Option: When Does It Make Sense?

For the largest Salesforce deployments, the Agentic Enterprise Licensing Agreement (AELA) is Salesforce's alternative to consumption-based pricing. Under an AELA, customers receive unlimited use of Agentforce and Data 360 in exchange for a negotiated, committed spend amount anchored to the overall enterprise relationship.

AELA structures look and feel like traditional enterprise licence agreements — a negotiated total value commitment rather than a pay-per-use model. Salesforce has actively promoted AELA to customers whose Agentforce and Data 360 consumption is projected to be high, because it provides Salesforce with revenue predictability while appearing to offer customers unlimited access.

Whether an AELA delivers value depends entirely on your projected consumption. If your modelled three-year Agentforce conversation volume and Data 360 credit consumption would, at standard rates, exceed the AELA commitment price, then AELA is advantageous. If your actual consumption falls short — as frequently occurs in the first 12–18 months of an AI agent deployment before adoption matures — you will have overpaid significantly.

Redress Compliance's recommendation for clients considering AELA: build a three-year consumption model before any commercial discussion, stress-test the assumptions with your internal IT and operations teams, and negotiate a consumption ramp-up period within the AELA structure that allows you to avoid overpaying in the early deployment phase. Never sign an AELA without a rollover provision for unused entitlements.

Compliance Obligations and Audit Exposure

Data 360 does not have the same traditional named-user audit exposure as Sales Cloud or Service Cloud, but it carries its own compliance obligations that enterprise buyers must actively manage. The primary compliance risk in Data Cloud licensing is overage consumption — deploying Data 360 in ways that generate credit consumption beyond your contracted volume, particularly through automated workflows that trigger credit-consuming operations without governance controls.

Common overage triggers Redress Compliance has observed in enterprise deployments include: identity resolution jobs running more frequently than scheduled due to integration configuration errors; Agentforce agents making repeated grounding calls for the same customer record within a single session; marketing automation workflows activating the same segment multiple times daily; and ETL processes ingesting external data into Data 360 at higher volumes than projected at contract time.

Salesforce temporarily suspended overage billing for early Data Cloud customers in 2025, acknowledging that the consumption model was new and that accidental overruns were occurring. That grace period is effectively closed. Enterprise buyers should assume that overages will be billed at standard rates or at a negotiated overage rate specified in the contract — and that rate is typically higher than the committed credit price.

Governance controls that reduce overage risk include: monthly credit consumption monitoring with alerts at 70% and 90% of committed volume; approval gates for any new Data 360 integration that triggers identity resolution; review of Agentforce agent conversation volume against credit projections quarterly; and a named Data 360 licence administrator who owns consumption governance.

The Annual Uplift Trap in Data 360 Agreements

Salesforce Order Forms for Data 360 contain the same standard annual price escalation clause applied across the Salesforce platform: an 8–10% annual uplift on contracted pricing at each renewal. For credit-based and profile-based agreements, this means the price per credit or per 1,000 profiles increases each year unless explicitly capped in the contract addendum.

For organisations with growing Data 360 usage — and most are growing usage as Agentforce deployments scale — the combination of increasing consumption volume and increasing per-unit prices creates a compounding cost escalation that is extremely difficult to control in year two and beyond without proactive contract management.

Salesforce's fiscal year ends January 31. The Q4 window (November–January) is when Salesforce's sales teams face the most internal pressure to close agreements, creating the best environment for buyers to negotiate uplift caps, rollover provisions, and overage rate commitments. Agreements renewed in February–April, just after Salesforce's fiscal year closes, typically carry the least flexibility.

Key Contract Terms to Negotiate for Data 360

Before signing or renewing any Data 360 agreement, enterprise buyers should ensure the following provisions are explicitly addressed in the contract:

• Uplift cap: Maximum 3% annual increase on per-credit or per-profile pricing, locked for the full contract term
• Credit rollover: Unused credits carry forward to the next contract year, at least partially (50–100% depending on negotiating leverage)
• Overage rate protection: Any overage credits purchased during the contract term are priced at the same contracted rate as your committed credits, not at standard list price
• Overage buffer: A 10–15% overage buffer at no additional charge before billing kicks in, particularly for the first year of a new deployment
• Flex Credit pooling terms: If using Flex Credits across Data 360 and Agentforce, confirm the allocation between the two products and what happens to the pool if one product's usage dramatically exceeds the other
• Free Salesforce data ingestion: Explicitly confirm in writing that ingesting data from other Salesforce products remains free for the duration of the contract term
• AELA exit provisions: If signing an AELA, ensure there is a right to convert to consumption-based pricing if actual usage falls significantly below the AELA commitment

Our Salesforce licensing advisory specialists review Data 360 agreements before signature — identifying missing rollover provisions, uncapped uplifts, and overage exposure before they cost you.

Summary: What Enterprise Data 360 Buyers Must Know

Salesforce Data 360 is a powerful platform with a licensing model that has grown progressively more complex with each annual overhaul. The March 2026 restructure introduced three co-existing models — credit-based, profile-based, and flex credits — each suited to different usage profiles. Choosing the wrong model at contract signing can result in significant overpayment or overage exposure before the first renewal.

The identity resolution cost premium (50 times more expensive than data ingestion per row) means that any deployment where identity resolution runs at high frequency must be explicitly modelled in the credit budget before contract signing. The Flex Credit pooling mechanism that links Data 360 and Agentforce means that AI agent deployment decisions can directly affect your data platform credit exposure — a dependency that was not present in previous contract structures.

Governance, contract protections, and accurate consumption modelling before signing are the three non-negotiable prerequisites for managing Data 360 costs effectively. Redress Compliance provides independent pre-signature reviews that address all three.