Data Cloud is Salesforce's fastest-growing product and its most opaque pricing model. Unlike per-user licences, Data Cloud bills by consumption: credits that tick down with every ingestion, query, and segment refresh. This guide decodes the mechanics so your procurement team can forecast, negotiate, and control costs before they spiral.
Data Cloud (rebranded as Data 360 in late 2025) operates on a fundamentally different commercial model from every other Salesforce product. There are no per-user seats. Costs are driven by data volume, processing frequency, and compute intensity. A single misconfigured identity resolution job can burn through 30% of an annual credit allocation in weeks. Unused credits do not roll over at contract expiry. This guide breaks down every cost component and provides the commercial strategies for forecasting, negotiating, and controlling Data Cloud costs. See also: AI, Einstein & Data Cloud Pillar Guide and Salesforce Pricing 2026.
| Cost Layer | How It Works | Key Risk |
|---|---|---|
| Consumption credits | Every action (ingesting records, running identity resolution, refreshing segments, executing queries, publishing insights) consumes credits from a prepaid pool. Sold in bundles of 100,000 at $500/100K list. Credits are fungible across all features since the September 2025 unification. | Credits are consumed every time a process runs, not just during initial setup. A nightly calculated insight across 15M rows consumes credits every single night. Organisations model the initial setup but fail to account for ongoing operational burn. |
| Data storage | Charged separately per terabyte per month. Independent of the credit system. Billed on actual stored volume, not record count. Storage accumulates as you ingest records, create unified profiles, and generate derived objects. | A single rich customer profile (purchase history, web interactions, email engagement, mobile events) consumes far more storage than a simple CRM contact. Organisations migrating from CRM-only deployments underestimate storage requirements by 40-60%. |
| Premium add-ons | Optional features with fixed-cost pricing separate from credits and storage. Ad Audiences (~$2,400/audience/year), Real-Time Profiles (~$750/10K profiles), Data Cloud One ($60K/instance), Data Spaces (contract-dependent). | Ad Audiences is the most common surprise. Activation to internal channels (email, Sales Cloud) uses credits only. Activation to external ad platforms (Google Ads, Meta) requires the separate Ad Audiences add-on at a per-audience annual fee outside the credit model. |
Unused credits expire at the end of the contract term. There is no automatic rollover. If your organisation purchases 5 million credits annually and consumes only 3 million, those 2 million surplus credits are lost. Conversely, exceeding the allocation triggers overage charges at a higher per-credit rate unless you have negotiated overage pricing in advance. This makes accurate consumption forecasting a commercial imperative.
The relationship between a Data Cloud action and its credit cost is governed by multipliers: published rate cards that define how many credits are consumed per million rows processed for each action type. These multipliers are the single most important variable in any cost forecast.
| Action Type | Credit Multiplier (per 1M rows) | Cost Impact |
|---|---|---|
| Batch data ingestion (external sources) | ~2,000 | Low to moderate. |
| Batch data ingestion (Salesforce connectors) | 0 (free since Aug 2025) | None. Structured data from CRM, Marketing Cloud Engagement, Marketing Cloud Personalization, and Commerce Cloud ingested at zero credit cost. |
| Streaming data ingestion | ~5,000-10,000 | High. 3-5x more expensive than batch for the same data volume. |
| Identity resolution (profile unification) | ~50,000-100,000 | Very high. 25-50x higher than batch ingestion. Single most expensive feature. Typically accounts for 70-90% of total credit consumption. |
| Calculated insights | ~1,000 | Moderate. Accumulates with nightly or daily refresh schedules. |
| Segmentation (batch) | ~500-1,000 | Low to moderate. |
| Activation (to internal channels) | ~500-1,000 | Low to moderate. |
| Queries / Data Explorer | ~100-500 | Low individually but accumulates with frequent ad-hoc usage. |
A profile unification run across 5 million records can consume 250,000-500,000 credits in a single execution. If that ruleset refreshes daily, annual credit consumption from identity resolution alone can reach 90-180 million credits, far exceeding what most organisations budget for. Organisations must make deliberate architectural decisions about which data sources participate in identity resolution, how frequently rulesets refresh, and whether incremental (changed-records-only) processing can replace full refreshes. These are million-dollar architectural decisions that must be made jointly by IT, marketing, and procurement.
| Change | What Happened | Impact |
|---|---|---|
| Free Salesforce data ingestion | Structured data from four Salesforce connectors (CRM/Sales/Service Cloud, Marketing Cloud Engagement, Marketing Cloud Personalization, Commerce Cloud) ingested at zero credit cost. | Removes a significant upfront cost barrier. Organisations can ground Agentforce AI agents in structured Salesforce data without consuming credits. Non-Salesforce external source ingestion still consumes credits at standard rates. |
| Unified credit type | Four separate credit categories (Data Services, Segmentation & Activation, sandbox, production) consolidated into one fungible credit. | Eliminates waste from mismatched pool allocations. A single credit can be used for any action across any environment. Sandbox environments consume credits at a 20% discount vs production. |
| Enhanced Digital Wallet | Granular usage-tagging insights at the feature level. Custom reports, consumption threshold alerts, near real-time tracking. | Significant improvement over the previous model where customers had to request consumption reports from their AE. Enables proactive governance. |
| Segmentation included | The separate Segmentation & Activation add-on licence retired. All Data Cloud licences now include segmentation and activation features. | Segmentation and activation actions consume credits from the unified pool rather than requiring a separate entitlement. Simplifies procurement. |
| SKU | List Price | Included Credits | Target Audience |
|---|---|---|---|
| Data 360 Provisioning (Everywhere) | $0 | Limited (varies by base product). | Existing Salesforce customers whose other products depend on Data Cloud functionality. Provides limited credits and storage, enough for basic operations but not enterprise-scale unification. |
| Data 360 Starter | $60,000/year | Initial credit allocation plus storage (quantities vary by negotiation). | Organisations with dedicated Data Cloud use cases. Standard paid entry point. Most enterprise deployments require additional credit packs within 6-12 months. |
| Included in Agentforce 1 Editions | Part of $550/user/month | 2.5M Data Services Credits/org/year. | Enterprises deploying Agentforce at scale. 2.5M credits may be sufficient for small-to-mid-scale AI deployments but will be consumed within months at enterprise scale. |
| Additional credit packs | $500/100K credits | As purchased. | Top-up when allocation is exceeded. Volume discounts negotiable. |
| Scenario | Process | Calculation | Annual Credits |
|---|---|---|---|
| Mid-size retailer 2M profiles, weekly segmentation, batch ingestion | Batch ingestion (external) | 2M records x 2,000/1M = 4,000 credits/refresh x 52 weeks | 208,000 |
| Identity resolution | 2M profiles x 50,000/1M = 100,000 credits/run x 52 weeks | 5,200,000 | |
| Segmentation (5 segments) | 2M profiles x 5 segments x 500/1M = 5,000 credits/cycle x 52 weeks | 260,000 | |
| Total | ~5.7M credits = ~$28,500/year in credits + $60K Starter + storage | ~5,668,000 | |
| Enterprise financial services 10M profiles, daily resolution, streaming ingestion | Streaming ingestion | 500K events/day x 10,000/1M = 5,000/day x 365 | 1,825,000 |
| Identity resolution (daily) | 10M profiles x 75,000/1M = 750,000/run x 365 | 273,750,000 | |
| Calculated insights (daily) | 10M rows x 1,000/1M = 10,000/day x 365 | 3,650,000 | |
| Total | ~279M credits = ~$1.39M/year in credits alone. Shifting to weekly resolution saves $1.18M/year. | ~279,225,000 |
The choice between daily and weekly identity resolution, between streaming and batch ingestion, between full and incremental refreshes: these are million-dollar architectural decisions that must be made jointly by IT, marketing, and procurement. Data Cloud procurement cannot be delegated to technical teams alone. See Negotiating Salesforce AI and Data Cloud Licensing.
| Strategy | What to Negotiate | Why It Matters |
|---|---|---|
| Negotiate overage pricing upfront | Negotiate a tiered overage rate (15-25% below list). Require automatic notification at 75% and 90% of the allocated pool. | Standard contracts charge overages at list price ($500/100K). Given the unpredictability of consumption models, overages are near-certain. Without protections, organisations discover overages only when the invoice arrives. |
| Build a credit buffer | Model expected consumption then add 25-40% buffer to the initial credit purchase at a negotiated volume discount. | First-year deployments almost universally underestimate consumption. Configuration, testing, identity resolution tuning, and iterative segment development all consume credits including in sandbox (at 20% discount). |
| Demand Flex Agreement terms | Negotiate the right to convert unused per-seat entitlements into Data Cloud credits and vice versa at renewal. | Prevents the common scenario where credits expire unused in one contract while another contract faces overages. Particularly valuable for enterprises deploying both Agentforce and standalone Data Cloud. |
| Pin down the rate card | Lock the credit multipliers applicable at contract signing for the full contract term. If Salesforce adjusts multipliers mid-term, your organisation should not bear the increased cost. | Salesforce has modified multipliers in previous rate card updates. A change in the identity resolution multiplier, even a modest increase, has outsized impact on annual spend. |
| Separate Data Cloud from CRM renewal | Insist on separate line items and where possible separate contract schedules for Data Cloud vs core CRM (Sales, Service, Experience Cloud). | Bundling obscures individual cost components. Separate schedules preserve your ability to renegotiate or right-size Data Cloud independently at the next renewal. See CIO Playbook: Salesforce Contract Negotiation. |
| Optimisation Practice | What to Do | Savings Impact |
|---|---|---|
| Minimise identity resolution scope | Ingest only active profiles (exclude records inactive for 12-18+ months). Apply data filters at the data lake object level. Validate match rules against sample datasets before full population runs. Use incremental processing (changed records only) rather than full refreshes. | Organisations implementing all four practices typically reduce identity resolution credit consumption by 50-70%. On a 10M-profile deployment, this can save $500K-$800K+ per year. |
| Batch over streaming | Before enabling streaming for any data source, challenge the business requirement. Does this use case genuinely require sub-minute freshness, or would hourly or daily batch deliver equivalent outcomes? | Streaming consumes 3-5x more credits than batch for the same data volume. In most enterprise deployments, fewer than 20% of data streams actually require real-time. The remaining 80% can run in batch at a fraction of the cost. |
| Optimise segment refresh schedules | Move segments from hourly to daily refresh where the business impact is negligible (most batch campaign use cases). Review every active segment quarterly. Deactivate segments no longer associated with live campaigns. | Moving a segment from hourly to daily refresh reduces credit consumption by up to 96%. Dormant segments still consume credits on their configured schedule. |
| Pre-transform data before ingestion | If your organisation has existing ETL infrastructure (MuleSoft, Informatica, dbt, custom pipelines), perform cleansing, deduplication, and transformation before ingesting into Data Cloud. | Reduces both the volume of records ingested and the compute cost of in-platform transformations. Particularly significant for large-scale data migrations where cleaning externally before bulk load saves hundreds of thousands of credits. |
Data Cloud is the data foundation for Agentforce. Every Agentforce agent that retrieves customer context, grounds responses in historical data, or personalises interactions draws from Data Cloud. This dependency means organisations deploying Agentforce must factor Data Cloud credit consumption into their AI cost model.
| Agentforce Consideration | Detail |
|---|---|
| Included credits | Agentforce 1 edition ($550/user/month) includes 2.5 million Data Services Credits per org per year. For small-to-mid-scale AI deployments, this may be sufficient. For enterprises running agents across sales, service, and marketing at scale, 2.5 million credits will be consumed within months. |
| Separate credit systems | Data Cloud credits (Data Services Credits) pay for data ingestion, unification, segmentation, and activation. Agentforce Flex Credits pay for AI agent actions ($0.10 per action). When Agentforce agents query Data Cloud to retrieve customer context, that query consumes Data Cloud credits. Organisations must model both credit pools. |
| Strategic advice | Model Data Cloud credit consumption for Agentforce use cases before committing to Agentforce licences. The base Agentforce licence cost is visible. The Data Cloud credit tail is where budgets overrun. Use a total cost of ownership analysis that includes both per-user and consumption-based costs. See Einstein & Agentforce AI CIO Playbook and Salesforce TCO Calculator. |
| Governance Element | What to Implement |
|---|---|
| Digital Wallet monitoring | Configure consumption threshold alerts at 50%, 75%, and 90% of annual allocation. Build custom reports by feature, data stream, and process type. Review near real-time consumption visibility. |
| Tenant Billing Events | Salesforce exposes billing events via Platform Events. Consume these with custom Apex triggers, MuleSoft, or external monitoring systems to build automated governance workflows and even automated responses (pausing non-critical processes when consumption exceeds thresholds). |
| Governance ownership | Assign to a specific role (Salesforce Centre of Excellence lead or IT Asset Management). Review weekly consumption reports. Approve any new data streams or process schedules that increase credit consumption. Conduct quarterly reconciliation between actual consumption and contracted allocation. |
| Integration with licence optimisation | Integrate Data Cloud monitoring into your broader Salesforce licence optimisation practice. Consumption-based and per-seat costs should be tracked in a unified governance framework. See Salesforce Licence Optimisation Playbook. |
$500 per 100,000 credits at list price. Credits are sold in bundles and are fungible across all Data Cloud features. Volume discounts are available for large purchases, and negotiated rates of 15-30% below list are common in enterprise contracts. Always negotiate overage pricing separately to avoid paying list rates when you exceed your allocation.
Yes, since August 2025. Structured data from four Salesforce connectors (CRM/Sales/Service Cloud, Marketing Cloud Engagement, Marketing Cloud Personalization, and Commerce Cloud) is ingested at zero credit cost. Data from non-Salesforce external sources (databases, data warehouses, third-party APIs, Snowflake, BigQuery) still consumes credits at standard batch or streaming multiplier rates.
Identity resolution (profile unification) by a wide margin. The credit multiplier is approximately 50,000-100,000 credits per million rows, which is 25-50x higher than batch data ingestion. For organisations with large customer databases, identity resolution typically accounts for 70-90% of total credit consumption. Reducing the scope and frequency of identity resolution is the single most impactful cost optimisation lever.
No, not by default. Credits expire at the end of the contract term. However, rollover provisions can be negotiated into the contract. Additionally, the Flex Agreement framework allows conversion of unused credits to other Salesforce entitlements (and vice versa). Both provisions must be explicitly negotiated. They are not standard terms.
Data 360 is the rebranded name for Data Cloud, introduced in late 2025. The product functionality is unchanged. Salesforce rebranded as part of a broader naming consolidation. Contractual references may still use "Data Cloud" depending on when the agreement was signed. The SKUs (Data 360 Starter, Data 360 Provisioning) reflect the new naming convention.
They are separate credit systems. Data Cloud credits (Data Services Credits) pay for data ingestion, unification, segmentation, and activation. Agentforce Flex Credits pay for AI agent actions ($0.10 per action, 20 Flex Credits per action). However, when Agentforce agents query Data Cloud to retrieve customer context, that query consumes Data Cloud credits. Organisations must model both credit pools to forecast total AI and data costs. See Salesforce AI Credits Consumption Model.
Near real-time, via the Digital Wallet. Salesforce's Digital Wallet provides feature-level consumption insights, out-of-the-box reports, custom report builders, and configurable threshold alerts. For deeper monitoring, Tenant Billing Events (Platform Events) can be consumed by custom Apex triggers, MuleSoft, or external monitoring systems to build automated governance workflows.
Volume discounts on credit purchases, discounted overage rates, and rate-card lock-in are all achievable. Enterprise contracts with annual credit commitments exceeding $100,000 typically secure 15-30% below list price. Multi-year commitments and bundling with core CRM renewals provide additional leverage. The most valuable negotiated term is often rate-card stability: locking the credit multipliers for the full contract duration to prevent mid-term cost increases. See Salesforce Contract Negotiation Service.
Redress Compliance provides independent Data Cloud consumption forecasting, contract negotiation, credit optimisation, and governance framework implementation. No Salesforce partnerships, reseller relationships, or referral arrangements. Fixed-fee engagements.
Salesforce Contract Negotiation ServiceIndependent consumption forecasting, contract negotiation, credit optimisation, and governance. Fixed-fee engagements. No vendor conflicts.