Navigating Risks and Optimisation in Salesforce Consumption Based Licensing

Executive Summary:

As Salesforce increasingly offers Consumption Based Licensing (CBL) across products like Data Cloud, Messaging, API usage, and MuleSoft, organisations are transitioning from fixed licenses to pay-as-you-go pricing. While this model provides flexibility and scalability, it introduces new complexities, particularly around cost control, monitoring, and predictability.

This whitepaper outlines the key risks associated with CBL, actionable risk mitigation strategies, and Salesforce specific tools and techniques that help organisations optimise their consumption model effectively and avoid financial surprises.

1. Understanding Consumption Based Licensing in Salesforce

CBL shifts traditional licensing models from static user-based pricing to dynamic, usage-based pricing, it is like paying your power bill as you are charged based on usage. Instead of paying for capacity upfront, customers are billed for what they use commonly referred to as “units of consumption”, such as:

• API calls

• Outbound messages (e.g., SMS, emails)

• Customer Data Platform (CDP) profiles

• MuleSoft transactions

Use Cases:

• High volume messaging campaigns

• API heavy integrations with external systems

• Real time personalisation and profile management using Data Cloud

It is worth remembering that CBL is not exactly new. Cloud providers like AWS and Microsoft Azure have been using this model for years, letting businesses pay only for the infrastructure they actually use. That approach has worked well, and it is now influencing how enterprise software platforms like Salesforce structure their pricing.

Today, this model is gaining real momentum in the Software as a Service (SaaS) world because the way businesses operate is changing. Flexibility and scalability aren’t just nice to have anymore as they are essential. As organisations embrace digital transformation and rely more on API-driven systems, the old way of licensing static, upfront costs, often just does not make sense. It can lead to paying more than you use, or worse, hitting limitations right when your business needs to scale.

With cost pressures mounting, especially in uncertain economic times, many organisations are rethinking how they buy software. They want pricing that reflects actual value, not theoretical capacity. That is where CBL fits in. It allows teams to pay based on what they truly use, no more, no less.

We are also seeing this shift accelerate with the rise of real-time data platforms like Salesforce Data Cloud and Customer Data Platforms (CDPs), where the value is driven by data processed, not just the number of users.

In the end, CBL is more than just a pricing model, it is a strategic enabler. It fosters innovation by allowing teams to experiment, scale, and adapt without being constrained by rigid contracts. For organisations facing seasonal demand, rapid growth, or unpredictable usage patterns, CBL delivers a level of agility that traditional licensing simply cannot match. It is especially well-suited for businesses with elastic needs and expanding digital footprints but with that agility comes a new kind of responsibility to monitor usage carefully and manage costs wisely.

2. Risks of Consumption Based Licensing

2.1 Cost Overruns

A single misconfigured workflow or ungoverned campaign can significantly inflate usage and rapidly drive costs beyond planned budgets. Systems designed for flexibility can become financially vulnerable without proper oversight. Uncontrolled usage spikes, particularly from unexpected campaigns or integration errors, pose a serious risk to budget stability.

2.2 Lack of Visibility

Many organisations realise they have over consumed only after the invoice lands. Real-time insights are often missing or underused.

2.3 Misconfigured Automations

Salesforce automation and integrations can become problematic if not carefully designed, with misconfigured Flows, Apex triggers, or unstable external callouts leading to excessive API calls, performance issues, and potential outages. Even simple actions like a field update can cascade into major resource consumption. With the rise of Salesforce Data Cloud, teams also need to pay close attention to profile unification design. While it enables powerful data consolidation, poor setup can increase complexity and costs. Additionally, misconfigured Calculated Insights and Activation Rules can cause unintentional automation loops or excessive processing, further impacting system performance. Both automation and data strategies require intentional planning to avoid hidden risks and ensure efficient, scalable performance.

2.4 Forecasting Challenges

Usage patterns remain highly variable, influenced by factors like marketing campaigns, seasonal demand, and data processing complexity. Unlike steady growth, usage does not always follow a predictable curve and neither will yours. This unpredictability makes it difficult to accurately forecast costs, especially since understanding how usage credits translate into actual dollars can be complex. Customers often struggle with pricing transparency, as spikes in automation, calculated insights, or data activations can quickly drive-up credit consumption and thus expenses beyond initial expectations.

2.5 Vendor Lock-In

Once you are deeply integrated with CBL backed services, reversing courses can become both technically and contractually expensive. The deeper the integration, the more cost prohibitive it becomes to decouple, often requiring significant reengineering and renegotiation.

3. Mitigation Strategies and Optimisation Techniques

3.1 Monitor Usage Like a Hawk

Keep a close eye on your consumption to avoid surprises. Use Salesforce’s Usage Metrics Reports and Event Monitoring to track activity across your organisation. Regularly check the System Overview to monitor API limits and prevent hitting thresholds. For Data Cloud specifically, enable Consumption Reports, and leverage the Digital Wallet dashboard as these tools provide real-time insight into data processing and credit usage, helping you catch spikes before they become costly.

• Use Salesforce Usage Metrics Reports and Event Monitoring to track consumption

• Check System Overview regularly to monitor API limits and avoid hitting thresholds

• Enable Consumption Reports and use the Digital Wallet dashboard for real-time usage insights for Data Cloud

3.2 Set Limits and Guardrails

Prevent runaway automation and unexpected consumption by setting clear limits. Use Apex and Flow guardrails (like check limits, loop controls and error handling) to avoid recursive or high-volume executions. For external integrations, use an API gateway (e.g., AWS, MuleSoft) to apply quotas and rate limits, helping prevent overuse or credit spikes. While Named Credentials help centralize and secure access to external systems, they should be combined with external control mechanisms for throttling. This is especially critical for Data Cloud features like Calculated Insights and Activation Rules, which can quickly scale up usage if left unchecked.

• Apply limits in Apex and Flows to prevent runaway automation

• Use quotas and rate limits via API gateways to control external integrations

• Pay special attention to Data Cloud features like Calculated Insights and Activation Rules to avoid unexpected credit spikes

3.3 Refactor and Batch Your Work

Optimize how you handle data processing. Instead of updating records multiple times, consolidate logic to perform updates once when possible. Batch your API calls or messages, sending one bulk request instead of many smaller ones reduces load and consumption. These practices boost performance and keep credit usage lower, which is critical for large Data Cloud workloads or complex automations.

• Consolidate logic to minimize repeated record updates

• Batch API calls and messages to reduce the number of individual transactions

3.4 Use External Systems Wisely

Offload heavy data processing whenever possible. Move demanding tasks like ETL or complex transformations to external platforms such as Heroku, AWS Lambda, or MuleSoft to keep your Salesforce and Data Cloud environment efficient. Also consider Salesforce Functions, which provide scalable, serverless compute power within the Salesforce ecosystem. This approach reduces strain on your core system and helps control consumption costs without sacrificing performance.

• Offload heavy processing tasks (ETL, data transformation) to 3rd party platforms that are often cheaper than processing the same workload inside Salesforce's environment

• Utilize Salesforce Functions for scalable, serverless computing within the Salesforce ecosystem

4. Salesforce Tools to Assist with CBL

Salesforce offers several powerful tools to help organisations effectively manage and optimize CBL as listed below and additionally, you can use the Salesforce Optimizer which can identifies inefficiencies and usage trends across the organisation, recommending actions to reduce unnecessary consumption and maximize value. Together, these tools empower organisations to transparently manage their consumption-based licenses, control costs, and align usage with business needs.

4.1 Salesforce Digital Wallet

The Digital Wallet which is a hidden asset that provides a centralised way to track and allocate usage credits in real time, ensuring precise control over license consumption. It provides an intuitive interface to view detailed usage data by day and period, making it easier to track consumption trends and identify potential overages. It also supports configurable Consumption Threshold Alerts to notify your team when usage exceeds set limits, along with automated Monthly Account Summary emails that give a clear overview of past usage. Additionally, it handles complex calculations for consumption, including scenarios involving multiple contracts, ensuring accurate and transparent license management across your organisation.

• Real-time credit tracking and allocation with an intuitive, time-based usage view

• Configurable consumption alerts and Monthly Account Summary emails

• Complex consumption calculations including multi-contract scenarios

4.2 Rate Cards

Salesforce Rate Cards define how Data Cloud Credits such as those for Data Services, Segments, and Activations are allocated and consumed. These credits are included with specific services as outlined in the applicable Order Form and must be used before the stated Order End Date, as rollover is not permitted. Usage is calculated based on predefined multiplier rates that vary by usage type, which Salesforce may update periodically. When credits span multiple products (e.g., Marketing Cloud and Tableau), they are pooled and tracked collectively. Consumption is applied first to credits from the earliest-expiring Order Form. If total usage exceeds the available credits, the lowest applicable overage rate across active Order Forms is used. These cards specify the resources offered by each product and define what constitutes a single unit of usage, aiding in planning and budgeting. Work with your account executive to find a solution that meets your goals.

• Data Cloud Platform Services Rate Card: https://www.salesforce.com/en-us/wp-content/uploads/sites/4/documents/platform/data-cloud-platform-services-rate-sheet.pdf

• Segments and Activations Rate Card: https://www.salesforce.com/en-us/wp-content/uploads/sites/4/assets/pdf/misc/segment-and-activation-rate-card.pdf

4.3 Data Cloud Reports and Dashboards

Data Cloud Reports and Dashboards give you clear, actionable insights into how your data is being used, helping you make smarter decisions and optimize consumption. You can easily create standard reports on one or more related Data Model Objects (DMOs) or use Calculated Insights (CIs) to highlight key focus areas for your business. For more tailored analysis, build custom report types to zero in on the fields and records that matter most. Reports can be grouped, filtered, and summarized, and run with near real-time data. You can also share them with your team and visualize key metrics and trends through dashboards, so you can act quickly and confidently.

• Get clear insights into data consumption to make informed, optimized decisions

• Create standard or custom reports using DMOs and CIs

• Access near real-time data with flexible grouping, filtering, and summarizing options

• Visualize key trends and KPIs in dashboards to support faster, data-driven decisions

4.4 Agentforce & Data Cloud Consumption Estimator (Beta)

The Agentforce and Data Cloud Consumption Estimator (Beta) is an upcoming tool designed to help organisations forecast their usage of Data Cloud and Agentforce credits. It provides forward-looking estimates based on your current setup and expected usage, helping you plan ahead, avoid overages, and align consumption with business goals. While still in early beta, this tool is positioned to complement the Digital Wallet by offering predictive insights alongside real-time tracking.

• Currently in early beta: https://www.datacloudcalculator.com/

• Forecast your consumption

• Gain spending visibility

5. Forecasting Consumption Based Licensing Cost

Forecasting is not about making guesses, it is about using data to tell a clear, disciplined story that helps keep costs predictable and budgets on track. This forecasting approach is based on Data Cloud credit consumption as defined in the Data Cloud Platform Services Rate Card.

5.1 Step by Step Forecasting Approach

To estimate credit consumption, start by identifying the applicable usage type multiplier and the volume of data either current or forecasted. Each usage type has a distinct credit consumption rate, as outlined in the Data Cloud Platform Services Rate Card referenced in the previous section. Once both the usage type multiplier and data volume are known, apply them using the formula provided below to forecast credit usage. This approach enables more accurate planning of credit requirements and associated costs based on anticipated usage type, typically provided in your contract documentation or by your Salesforce Account Executive (SAE).

• Identify the usage type and its credit multiplier

• Determine the data volume involved (Actual or Forecasted)

• Apply the forecast formula (Listed below)

• Use this to project future credit usage and estimate costs accurately (Provided in your Contract or by your SAE)

• Supports planning and budgeting

5.2 Forecast Formula

(d for data processed and m for usage type multiplier)

Credits consumed = (d ÷ 1,000,000) × m

5.3 Usage Cost Calculation and Forecast

Calculation: To get a sense of how much it might cost to use Salesforce Data Cloud, we can apply the formula mentioned above. Let us look at a practical example. Imagine you are building a batch Calculated Insight (CI) based on a dataset with 2 million rows. For this type of activity, the multiplier (m) is set to 15.

30 credits = (2,000,000 ÷ 1,000,000) × 15

If your CI is set to refresh daily, credits are consumed again with each refresh. Now imagine your data grows to 2.2 million rows by the next day:

33 credits = (2,200,000 ÷ 1,000,000) × 15

(2,200,000 ÷ 1,000,000) × 15 = 2.2 × 15 = 33 credits

For further clarification on actual costs, we reached out to Andrea Mainzer, Data Cloud Lead, Public Sector & Education ANZ at Salesforce. Andrea mentioned that Data Services credits are sold in bundles of 100,000 for $700 (AUD). To give a real-world sense of pricing, she shared that profile unification for 500,000 rows would consume 50,000 credits, costing around $350 (AUD).

• Credits are sold in bundles of 100,000 for $700 (AUD)

• Therefore, 1 credit = $0.007 (AUD)

She also explained that credit usage varies depending on the activity and it is not a flat rate. For example, ingesting 1.5 million rows through an internal data pipeline would use 750 credits (500 credits for the first million rows and 250 for the next 500,000), costing about $5.25 (AUD).

• 750 × $0.007 = $5.25 (AUD)

Forecast: Let us take an example and forecast it for the next 3 years: assuming data grows by 20% annually, the credit cost for internal data pipeline ingestion will increase from $5.25 (AUD) to about $9.07 (AUD) over three years, reflecting a total increase of around 73% over that period.

Usage cost calculation and forecast

Forecasting Tips

• Start with historical usage patterns

• Build a model using known drivers (campaign volume, traffic, users)

• Add 10–20% contingency for surprises

6. Recommendations

Managing Salesforce on a CBL model can feel a bit like keeping an eye on your energy bill, stay on top of it, and you are in control, ignore it, and surprises can creep in. As more organisations shift towards flexible, usage-based plans, it is essential to understand how to monitor, manage, and optimise your credit usage across Salesforce services like APIs, messaging, Data Cloud, and AI. Below are some practical, people first recommendations to help you get the most value from your licensing, avoid unexpected costs, and ensure your setup continues to support your business as it grows.

6.1 Understand Your Entitlements and Limits

• Know Your Contract: Fully understand your purchased entitlements like number of credits, API call limits, messaging credits, and what triggers overage charges.

• Regularly Review Usage & Limits: Monitor Salesforce Setup sections like “Usage and Limits,” “Company Information,” and cloud-specific dashboards (Digital Wallet) for current consumption.

6.2 Monitor Consumption Proactively

• Create Dashboards & Reports: Build admin dashboards to track real-time and historical usage of API calls, messaging, Data Cloud credits, and AI services.

• Set Alerts & Notifications: Configure automatic alerts via Salesforce tools (Flows, Process Builder) or external monitoring systems to notify when usage approaches limits.

• Leverage Salesforce Optimizer & Health Check: Regularly run these to detect underused features and identify inefficient resource consumption.

6.3 Control and Govern Usage

• Limit Permissions: Restrict access to high-consumption actions (e.g., bulk messaging, heavy Flows, integrations) through profiles and permission sets.

• Monitor Integrations: Keep an eye on third-party APIs and external integrations that often contribute the most to credit consumption.

• Establish Usage Policies: Define organisational guidelines on when and how to use features that consume credits, including Data Cloud activations and Calculated Insights.

6.4 Optimize Your Processes

• Refactor Automations: Continuously review and improve Flows, Apex classes and triggers, and processes to minimize redundant or excessive executions.

• Target Messaging: Use segmentation and suppress unnecessary or duplicate messages to conserve credits.

• Batch Operations: Where possible, use bulk APIs and schedule heavy workloads during off-peak hours to reduce consumption spikes.
• Data Cleansing: Regular data cleansing is key to running efficiently in a consumption-based model. By removing outdated or low-value records, organizations can streamline data, cut down on processing, and lower costs, especially in Salesforce Data Cloud, where volume affects pricing. It also boosts performance and ensures focus stays on high-quality, useful data.

6.5 Plan for Scaling and Forecasting

• Forecast Usage: Use historical data and business drivers (seasonality, campaigns, growth) to predict future credit consumption.

• Engage Salesforce Account Executives Early: Discuss expected needs and explore volume discounts or contract adjustments before hitting limits.

6.6 Integrate Licensing into IT Governance

• Centralize Monitoring (Digital Wallet + custom reporting/dashboarding): Incorporate consumption metrics into enterprise IT dashboards alongside other SaaS and cloud spend reports.

• Collaborate Across Teams: Foster cooperation between IT, finance, and business units to ensure licensing spend aligns with actual business value.

6.7 Educate Your Teams

• Train Users and Admins: Educate stakeholders on which actions consume credits and how to use features responsibly.

• Onboard with Licensing Awareness: Include CBL impacts and best practices in onboarding processes for new Salesforce admins and developers.

6.8 Respond Quickly to Overages

• Develop Contingency Plans: Define actions to take if limits are reached, such as temporarily pausing automations or acquiring additional capacity swiftly.

• Maintain Flexible Budgets: Allocate contingency funds to cover unexpected usage spikes.

6.9 Align Licensing with Business Needs

• Assess Usage Patterns: Regularly analyse real and forecasted consumption to ensure licensing matches actual requirements.

• Right-Size Licensing: Choose or adjust consumption tiers to avoid paying for unused capacity or suffering unexpected overages.

• Pilot Consumption Models: Run proofs of concept to understand consumption behaviour before full rollout.

6.10 Manage Overages and Cost Controls

• Understand Overage Pricing: Know the costs associated with exceeding license limits and how to quickly procure additional credits.

• Implement Automated Controls: Use throttling or limits in automations and integrations to prevent runaway consumption.

Would you be interested in more recommendations?

• Make usage reviews part of sprint planning.

• Train admins and developers on best practices for efficiency.

• Combine digital tooling (like Optimizer) with governance policies.

• Use the Digital Wallet to reduce friction and consumption.

• Model your forecasts and then review them quarterly.

Conclusion

Consumption Based Licensing offers Salesforce customers incredible flexibility, but it also comes with some challenges. To avoid unexpected costs and keep budgets on track, companies need to stay on top of their usage, set clear limits, plan ahead, and make smart use of Salesforce’s built-in tools and other helpful solutions. When done right, teams can enjoy all the benefits of CBL like agility, scalability, and better cost control while steering clear of common pitfalls.

It is all about being proactive and thoughtful with how you manage consumption.