Salesforce Data 360 credit consumption is the metering model for Data 360, Salesforce’s customer data platform, formerly called Data Cloud. Data 360 is not licensed per user. Each service a customer runs, such as ingesting, transforming, unifying, querying, segmenting or activating data, produces a usage event with a usage type. The event consumes credits equal to the units processed multiplied by that usage type’s multiplier.[4] Credits come in two currencies. Data Services Credits can be spent only on Data 360 and follow a fixed rate card.[1] Flex Credits can also be spent on Agentforce, Slackbot and other Salesforce services, and for Data 360 their multipliers fall in monthly volume tiers.[2]
The rate cards themselves still say “Data Cloud”. Salesforce’s newer documents use “Data 360”.
Editions
Salesforce’s rate cards list no Data 360 editions. The credit quantity included with a Service is stated on the Order Form, in the Usage Details table.[1] Three credit instruments are described in current documents:
| Credit | Spendable on | Rate structure | Source |
|---|---|---|---|
| Data Services Credits (and Data Services Credits for Sandbox) | Data 360 only | Fixed multiplier per usage type; Production and Sandbox columns; batch and streaming variants | Customer Data Cloud Rate Card |
| Segments and Activations Credits | Segmentation and activation | Fixed multiplier (three usage types) | Segments and Activations Rate Card |
| Flex Credits | Data 360, Agentforce, Slackbot, Speech Foundations, Personalization and more | Data 360: four volume tiers per usage type in Production, flat Sandbox rate | Flex Credits Rate Card |
Trailhead states that Data Services Credits are split into 21 usage types, and that Flex Credits have 11 usage types for Data 360 alongside usage types for generative AI and prompts. An org that holds both credit types must re-contract to switch to Flex Credits once its Data Services Credits are used up (rule).[4]
Metrics
The basic formula, as Trailhead gives it, is
Credits consumed = (d/u) × m
where d is the amount of data processed, u the unit (one million rows for most usage types) and m the multiplier for the usage type (rule). Trailhead’s example is a batch calculated insight run on 20 million rows at a multiplier of 15, which consumes 300 credits. When the insight refreshes the next day over 20.2 million rows, it consumes 303 credits.[4] Every refresh consumes credits again, so the cost grows as the data grows.
Data Services Credits rate card
Selected multipliers from the Customer Data Cloud Rate Card, in credits per unit:[1]
| Usage type | Unit | Production | Sandbox |
|---|---|---|---|
| Internal Data Pipeline | 1M rows processed | Included (0) | Included (0) |
| (External) Data Pipeline, batch / streaming | 1M rows processed | 2,000 / 5,000 | 1,600 / 4,000 |
| Data Transforms, batch / streaming | 1M rows processed | 400 / 5,000 | 320 / 4,000 |
| Unstructured Data Processed | 1 MB processed | 60 | 48 |
| Intelligent Processing | 1 MB processed | 750 | 600 |
| Data Federation or Sharing Rows Accessed | 1M rows accessed | 70 | 56 |
| Data Share Rows Shared (Data Out) | 1M rows shared | 800 | 640 |
| Private Connect Data Processed | 1 GB processed | 500 | 400 |
| Profile Unification | 1M rows processed | 100,000 | 80,000 |
| Sub-second Real-Time Events | 1M combined events, API and actions | 70,000 | 56,000 |
| Calculated Insights, batch / streaming | 1M rows processed | 15 / 800 | 12 / 640 |
| Inferences | 1M inferences | 3,500 | 2,800 |
| Data Queries | 1M rows processed | 2 | 1.6 |
| Streaming Actions (including lookups) | 1M rows processed | 800 | 640 |
| Segment Rows Processed | 1M rows processed | 20 | 16 |
| Batch Activation | 1M rows processed | 10 | 8 |
| Activate DMO - Streaming | 1M rows processed | 1,600 | 1,280 |
| Code Extension | Compute unit | 40 | 32 |
Identity resolution stands out: Profile Unification costs 100,000 credits per million rows in Production, while internal pipelines are included at zero (rule). The separate Segments and Activations Rate Card uses the same three segmentation and activation multipliers (20, 10 and 1,600 in Production) for its own credit type.[3]
Flex Credits for Data 360
On Flex Credits, Data 360 usage types are priced in four volume tiers per usage type:[2]
| Usage type | Unit | Base (up to 300k credits) | Tier 2 (300k to 1.5M) | Tier 3 (1.5M to 12.5M) | Tier 4 (after 12.5M) | Sandbox |
|---|---|---|---|---|---|---|
| Data 360 Prep | 1M rows | 40 | 32 | 16 | 8 | 32 |
| Data 360 Unification | 1M rows | 75,000 | 60,000 | 30,000 | 15,000 | 60,000 |
| Data 360 Segmentation | 1M rows | 50 | 40 | 20 | 10 | 40 |
| Data 360 Activation | 1M rows | 60 | 48 | 24 | 12 | 48 |
| Data 360 Zero-Copy Sharing-Out | 1M rows shared | 60 | 48 | 24 | 12 | 48 |
| Data 360 Queries | 1M rows | 3 | 2.4 | 1.2 | 0.6 | 2.4 |
| Data 360 Unstructured Processing | 1 MB | 150 | 120 | 60 | 30 | 120 |
| Data 360 Intelligent Processing | 1 MB | 600 | 480 | 240 | 120 | 480 |
| Data 360 Streaming Pipeline | 1M rows | 3,500 | 2,800 | 1,400 | 700 | 2,800 |
| Data 360 Real-Time Pipeline | 1M events, API and actions | 250,000 | 200,000 | 100,000 | 50,000 | 200,000 |
| Data 360 Code Extension | Compute unit | 40 | 32 | 16 | 8 | 32 |
Trailhead maps each Data Services usage type to its Flex counterpart. Batch Data Transforms and batch Calculated Insights both become Data 360 Prep. Streaming Data Pipeline, streaming transforms, streaming Calculated Insights and Streaming Actions all become Data 360 Streaming Pipeline. Batch Data Pipeline, Data Federation, Data Share and Private Connect have no Flex counterpart.[4]
Counting / floors
- No rollover. Data Cloud Credits must be used before the Order End Date shown in the Usage Details table of the Order Form, and no rollover is permitted (rule).[1] The Flex Credits Rate Card applies the same condition to Flex Credits.[2]
- Monthly tiers per usage type. Flex tier multipliers are calculated separately for each usage type and reset on the first day of each calendar month. The thresholds include their upper limit, so Tier 2 runs up to the 1,500,000th credit and Tier 3 starts at credit 1,500,001 (rule).[2] Heavy use of one usage type therefore does not lower the rate charged for another.
- Sandboxes. Data 360 in Sandbox environments does not use tiered multipliers (rule). For Flex Credits in general, the Sandbox multiplier applies to all pre-production environments, including scratch orgs (rule).[2]
- Free ingestion from Salesforce orgs. Ingesting data from a Salesforce org through the Salesforce CRM connector, Agentforce Marketing connector, Agentforce Commerce connector or Agentforce Marketing Personalization connector does not consume credits (rule).[4]
- Multiple usage types per feature. One feature can consume credits under more than one usage type. Trailhead’s example: previewing a data transform consumes Data Queries credits as well as transform credits.[4]
- Pilots and changes. Pilot features may consume credits where their pilot terms say so. Salesforce may update usage types, tiers and multipliers from time to time, and tier changes are treated as multiplier changes.[2]
Other Flex Credit usage types
The Flex Credits Rate Card of 31 August 2026 also prices usage outside Data 360:[2]
| Category | Usage type | Production | Sandbox |
|---|---|---|---|
| Agentforce Actions | Standard Action; Custom Action | 20 | 16 |
| Agentforce Voice Actions | Standard Voice Action; Custom Voice Action | 30 | 24 |
| Prompts | Starter; Basic; Standard; Advanced | 2; 2; 4; 16 | 2; 2; 4; 16 |
| Help Agent Resolutions | Help Agent Resolutions | 400 | 0 |
| Customer Engagement | Leads Worked | 400 | 320 |
| Speech Foundations | Speech to Text (per hour); Text to Speech (per 1M characters); Translation (per 1M characters) | 150; 6,000; 4,000 | same |
| Personalization | Personalization Decisioning (per 1,000 decisions) | 100 | 100 |
| Slackbot Actions (per Slack workspace) | Slackbot Standard Action; Slackbot Advanced Action | 40; 200 | not stated |
Agentforce Actions are consumed by all product types (rule). The prompt multipliers apply to Agentforce 1 Edition customers, Agentforce for Sales, Service and Industries customers, and other products that no longer use Einstein Requests. Slackbot multipliers apply per Slack workspace (rule).[2] The Customer 360 Platform (Headless 360) usage type is listed with its multiplier “TBA”.
Virtualization & partitioning
Not applicable. Data 360 is a Salesforce-hosted service metered by data volume and events, with no server, core or hypervisor metric.
Cloud / BYOL
Data 360 runs only as a Salesforce cloud service. On Data Services Credits, data accessed through federation or sharing is metered as Data Federation or Sharing Rows Accessed, and data shared out as Data Share Rows Shared (Data Out). On Flex Credits, Trailhead maps Sharing Rows Accessed to Data 360 Zero-Copy Sharing-Out.[4] Private Connect traffic on Data Services Credits is metered per gigabyte.[1] No bring-your-own-license arrangement is published.
Programs
Flex Credits are bought under the buying models described in Salesforce User and consumption licensing: pay-as-you-go, pre-commit and pre-purchase, plus the fixed-price Agentic Enterprise License Agreement, which has no overages. Data Services Credits are bought as quantities on the Order Form.[1]
Out of scope
- Data 360 storage allowances and add-on licenses, which the rate cards do not price.
- Einstein Requests, the older generative AI metric, covered in Salesforce User and consumption licensing.
- Marketing Cloud contact and message metrics.
- Credit prices. The Flex Credit Calculator on salesforce.com is an estimating tool, not a price list.