White paper xxvi · Salesforce

Data Cloud. Sized against the buyer’s evidence.

Twenty pages on the Salesforce Data Cloud credit consumption model and commitment design. Profile ingestion sizing, event ingestion sizing, segmentation activation, the Agentforce data dependency, Tableau and MuleSoft adjacencies, the over-commit and under-commit failure modes, and the exit architecture. Written from the buyer’s side. None of it carries reseller margin or referral fee.

FormatWhite paper, gated
Pages20
AudienceCIO, CFO, CMO, CDO, Procurement
PublishedJanuary 2026
UpdatedMay 2026

A senior Admodum advisor will follow up to confirm receipt and offer a private read of the document if you would prefer a guided walkthrough. There is no obligation. The paper is the deliverable.

Contents

Inside the 20 pages.

i.
Why Data Cloud exists
The Salesforce Data Cloud commercial construct, the credit consumption model, the profile-and-event metric and Salesforce’s commercial logic at first sale.
ii.
The credit consumption model
The credit pool, the per-action credit cost, the consumption envelope and the over-consumption mechanic that determines whether the buyer pays through or rolls over.
iii.
Profile and event ingestion sizing
Unified Profile count, profile ingestion volume, event ingestion volume and the sizing methodology against the documented data sources and the trailing-period activity.
iv.
Segmentation activation
Segment-build credit consumption, activation-target credit consumption, the activation channel mix (Marketing Cloud, Advertising, Commerce, Service) and the consumption envelope.
v.
Agentforce data dependency
The Agentforce dependency on Data Cloud profiles, the Einstein 1 platform data layer, the credit consumption inside Agentforce agent invocations and the joint-commitment sizing.
vi.
Tableau and MuleSoft adjacencies
The Tableau-Salesforce Data Cloud connector, the MuleSoft integration pipeline, the data-residency clauses and the rationalisation question against existing data warehouse stacks.
vii.
Exit architecture
The post-Data Cloud position. Profile portability, segmentation export, activation history retention and the residual rights position the buyer carries forward.
viii.
Reading list and references
Companion papers on the Salesforce renewal-defence playbook, the Agentforce commercial scope and the MuleSoft scope-and-licence rationalisation.
Excerpt · Section II

The credit pool is not a sizing. It is a starting position.

Salesforce Data Cloud is sold against a credit consumption model. The buyer commits to an annual credit pool. Every action inside Data Cloud (profile ingestion, event ingestion, segment build, activation, query, identity resolution) consumes a documented quantity of credits. At year-end, the credit pool retires against the documented consumption.

A credit pool sized against the publisher’s default forecast is a credit pool sized against the publisher’s revenue.

The publisher’s framing of the credit pool is the default forecast. The default forecast is built from the Salesforce account team’s estimate of the buyer’s ingestion volume, segment build cadence and activation breadth. The estimate is rarely conservative; it is rarely the buyer’s estimate; and it is rarely supported by the documented use cases the buyer has actually built.

The buyer’s framing of the credit pool is the use-case-by-use-case sizing. The methodology builds a credit pool from the documented use cases (profile ingestion volume, event ingestion volume, segment count, segment-build cadence, activation count, activation cadence), runs the credit-cost arithmetic against the published credit-cost schedule, and produces a credit-pool sizing rooted in the buyer’s actual data flows. The buyer’s sizing is invariably smaller than the publisher’s default; the rest of the methodology is about retaining the smaller sizing through the negotiation.

Request the white paper

Request the 20-page paper.

Corporate email only. The paper is sent by a senior Admodum advisor. No marketing list, no third-party distribution. Submission confirms you have read the independence statement at the foot of this page.

Please enter a corporate email address. Personal addresses (gmail, hotmail, outlook, yahoo, icloud and similar) are not accepted.
Corporate email required · No marketing list · Reply within one business day
Independence
Admodum is not a partner, reseller, or affiliate of Salesforce, or of any other software vendor. No reseller margin, no referral commission, no certified-implementer subcontract.
Software licensing white paper

Bring an advisor to the Data Cloud table.

The Admodum Salesforce practice closes Data Cloud commitments inside the Renewal Programme and the Benchmarking Programme. Engagements run as fixed fee, contingency or annual retainer.