Data Cloud Credit Consumption Guide for Marketing Cloud Next

Data Cloud is a credit-based platform. Your Marketing Cloud Next licence includes a credit allocation, and certain activities consume credits as they run. Most marketing teams do not think about credit consumption until they receive a low-balance alert or hit a usage cap — at which point they are scrambling to understand what they are running.

This guide explains how Data Cloud credits work, what consumes them, and how to design your programme to stay within your allocation without constraining your marketing operations.

What Data Cloud Credits Are

Data Cloud credits are a unit of computational and storage resource. They are consumed by the operations that Data Cloud runs on your behalf: data ingestion, identity resolution, segmentation, and activation.

Your credit allocation is included in your Marketing Cloud Next licence. Growth Edition and Advanced Edition have different default allocations; additional credits can be purchased if needed.

Credits refresh on your annual contract cycle — unused credits do not roll over. This means organisations that significantly under-consume credits may be paying for capacity they are not using; organisations that over-consume may face overage charges.

What Consumes Data Cloud Credits

Record Storage (Unified Individuals)

The largest driver of credit consumption for most organisations is Unified Individual count — the number of deduplicated person profiles in your Data Cloud. Your licence includes a Unified Individual entitlement; each Unified Individual above that threshold consumes additional credits.

For Growth Edition, the standard entitlement is typically in the range of 10,000–25,000 Unified Individuals (exact figures are contract-specific). For Advanced Edition, the entitlement is higher.

This is the primary reason data hygiene matters for credit management: contacts who will never receive a campaign (inactive for 3+ years, incomplete records, test accounts) consume the same credits as active, engaged contacts.

[Screenshot: Unified Individual count monitor showing allocation vs actual]

The Data Cloud admin usage panel showing Unified Individual allocation (20,000 included) vs current count (16,840), with a 30-day trend chart showing slow growth and a projection line

id: unified-individual-count-monitor

Data Ingestion

Every record processed through a data stream consumes a small credit amount. The consumption rate depends on:

• Stream type: Real-time streams consume more credits than batch streams for the same record count, due to the continuous processing overhead
• Record volume: Higher volumes consume proportionally more credits
• Refresh frequency: A batch stream refreshing hourly consumes more credits than one refreshing daily

For the Salesforce CRM data stream on a typical mid-market organisation (50,000–200,000 Contact records), ingestion credit consumption is usually modest compared to Unified Individual storage.

Identity Resolution

Each identity resolution run consumes credits based on the number of Individual records processed and the complexity of your matching rules. For most organisations with static databases, the ongoing credit consumption from identity resolution after the initial run is low — resolution runs incrementally on changed records, not the full database each time.

The initial resolution run (when you first activate a ruleset against your full database) is the highest-consumption event. For organisations with very large databases (1M+ records), planning the initial run timing and ensuring credit availability before activation is important.

Segmentation (Data 360 Segments)

Segment queries consume credits each time they are evaluated. The consumption rate depends on:

• Segment complexity: More conditions, more object joins, more sub-queries = higher credit consumption per evaluation
• Evaluation frequency: Segments evaluated in real-time consume credits continuously; segments evaluated on a schedule consume credits at the evaluation interval
• Segment count: The more active segments you maintain, the higher the aggregate evaluation cost

For most Marketing Cloud Next programmes with 20–50 active segments, segmentation credit consumption is manageable. Problems arise when teams create hundreds of segments (often leftover from testing) that continue consuming credits while providing no programme value.

[Screenshot: Credit consumption breakdown by activity type]

A pie chart showing credit consumption breakdown: Unified Individual storage (62%), Data Ingestion (18%), Segmentation (12%), Identity Resolution (5%), Activation (3%) — illustrating that storage dominates and ingestion/segmentation are secondary drivers

id: credit-consumption-breakdown

Activation

Activating segments to marketing channels (email send, flow entry) also consumes a small credit amount per activation event. Activation credit consumption is typically the smallest category for marketing use cases.

How to Monitor Credit Usage

Navigate to Setup → Data Cloud → Data Cloud Admin → Usage to access the credit monitoring dashboard.

Key metrics to track:

• Current allocation vs current consumption: How much of your annual credit allocation have you used so far?
• Daily consumption trend: Is consumption increasing, decreasing, or flat?
• Unified Individual count vs entitlement: How close are you to your Unified Individual limit?
• Consumption by activity type: Which activity category is the largest consumer?

Set up usage alerts: Data Cloud can notify administrators via email when consumption reaches a defined percentage of the annual allocation (commonly 75% and 90%).

[Screenshot: Data Cloud credit usage dashboard in admin settings]

The Data Cloud usage dashboard showing annual credit allocation (500,000 credits), YTD consumption (187,000), projected annual consumption (312,000), and a monthly consumption chart with the largest single-month spike coinciding with the initial identity resolution run

id: data-cloud-usage-dashboard

Credit Optimisation Strategies

Audit and Remove Inactive Segments

Every active segment is evaluated on its configured schedule. Segments created for one-time campaigns, testing, or exploratory analysis that are no longer needed continue consuming credits indefinitely if not deactivated.

Establish a segment governance process:

1. Monthly review of all active segments
2. Deactivate any segment with no associated active campaign
3. Archive segments from completed campaigns after 90 days

A typical organisation with undisciplined segment management accumulates 100–200 inactive segments within a year. Deactivating these can reduce segmentation credit consumption by 30–50%.

Use Batch Streams for Non-Time-Sensitive Data

Not every data source requires real-time processing. Time-sensitive data (website events, form submissions) warrants real-time streams. Historical data (CRM Contact full-sync, Account data, historical opportunity records) does not.

Configure non-time-sensitive CRM fields on a daily batch refresh instead of real-time Change Data Capture. The marketing impact is minimal (knowing a company's employee count as of yesterday vs right now makes no practical difference for segmentation); the credit savings are meaningful.

[Screenshot: Data stream batch vs real-time configuration for credit optimisation]

The data stream configuration comparison showing two CRM streams: one for Contact core fields (First Name, Last Name, Email, Title) configured as real-time CDC, and one for Contact secondary fields (custom fields, legacy fields) configured as daily batch — illustrating selective real-time processing

id: data-stream-processing-config

Suppress Inactive Contacts

Contacts who have not engaged in 24+ months and show no commercial relationship in CRM are consuming Unified Individual entitlement with no marketing value. Implementing a suppression process — either removing them from CRM (if legally permissible) or excluding them from Data Cloud ingestion — reduces your Unified Individual count and frees entitlement for active contacts.

Before suppressing, check for any compliance requirements in your jurisdiction regarding data retention for legal hold or audit purposes.

Simplify Complex Segments

Segments with 10+ conditions across 4+ objects are expensive to evaluate. If a complex segment can be approximated with a simpler one that captures 95% of the same audience with 3–4 conditions and 2 objects, the simpler segment will consume significantly fewer credits.

Review your most-used segments for complexity reduction opportunities. The precision trade-off is usually minimal; the credit savings can be significant.

Batch Campaign Sends Rather Than One-Per-Contact Sends

For campaigns where immediate send timing is not important (newsletters, quarterly updates, batch nurture sequences), schedule sends as a batch at a fixed time rather than triggering individual sends per contact. Batch processing is more credit-efficient than thousands of individual activation events.

Planning for Credit Consumption Before Major Events

Certain planned activities consume significantly more credits than normal operations:

Initial identity resolution run: The first run against your full database is the highest-consumption event in the platform lifecycle. Plan this during a period when you have sufficient credit headroom — not at the end of your contract year.

Major database import: Importing a large purchased list or event attendance database temporarily increases Unified Individual count and ingestion consumption.

Calculated Insight full recomputation: Running a new Calculated Insight across your full database for the first time is computationally intensive. Schedule large recomputation jobs during off-peak periods.

For each planned major event, review your current credit balance before proceeding. If you are within 20% of your annual limit, contact your Salesforce account team to discuss your options before the event runs.

Summary

Data Cloud credit management is a background operational task that becomes urgent only when it is neglected. The organisations that manage it well are those that build a monitoring habit (monthly usage review), maintain segment hygiene (deactivate unused segments), and design their data architecture with credit efficiency in mind from the start.

For most mid-market B2B organisations on Marketing Cloud Next, the standard credit allocation is sufficient for a well-designed programme. Over-consumption typically signals either an over-large Unified Individual population (data hygiene opportunity) or accumulated inactive segments (governance opportunity) — both of which are fixable.

Need help auditing your Data Cloud credit consumption or optimising your programme design? Pardive provides Data Cloud administration reviews and credit optimisation recommendations. Book a free Data Cloud audit.