Salesforce Marketing Cloud Send-Credit Costs Explained

Marketing Cloud Engagement doesn’t price like the rest of the Salesforce ecosystem. Sales and Service Cloud bill per named user; Marketing Cloud Engagement bundles a contact allowance and a pool of send credits — email, SMS, push, and increasingly Data 360 credits — into each edition, then charges overage once you exceed either. That’s a different cost-reduction problem than a per-seat license, and it catches teams off guard when a campaign push or a database-growth spurt runs the meter faster than headcount ever would.
What actually drives the bill
- Contact volume, not user count. Every edition caps how many marketing contacts you can hold before triggering a tier increase — a growing subscriber list moves the bill even if the marketing team hasn’t added a single new user.
- Send credits by channel. Email, SMS, and push each draw from their own allowance; a heavier send cadence in one channel — more frequency, more journeys, more re-engagement campaigns — burns that channel’s credits faster regardless of list size.
- Overage once allowances are exhausted. Exceeding the bundled contact or send allowance triggers additional charges outside the base subscription, and a seasonal campaign push (a holiday send calendar, a product launch) can spike usage well past a typical month’s baseline.
- Data 360 credits riding along. Newer packaging bundles data-platform credits into the same allowance pool that email and mobile sends draw from, so AI-driven personalization and journey features can quietly compete with core sends for the same budget.
Why the seat-based playbook doesn’t transfer
The standard Salesforce cost-reduction move — audit who’s logged in, reclaim dormant licenses, move light users to a portal — targets per-user billing. Marketing Cloud Engagement isn’t counting logins; it’s counting contacts and credits consumed. Reducing the number of marketers with platform access does nothing to a bill driven by list size and send volume, which is why this deserves its own audit separate from the rest of a Salesforce license review.
Where the spend actually needs scrutiny
| Cost driver | Common overspend pattern |
|---|---|
| Contact allowance | Stale, unengaged, or duplicate contacts counted against the tier long after they stopped opening anything |
| Send credits | Sending every segment every campaign instead of targeting the subset likely to engage |
| Seasonal spikes | Holiday or launch calendars planned without checking remaining allowance first |
| Data 360 credits | AI personalization features left running against full volume after a pilot ends |
Where a custom-built layer fits instead
Not every send needs to go through the full Marketing Cloud Engagement pipeline. For a narrow, well-defined notification — a transactional status update, a single triggered reminder tied to one workflow — a custom-built notification layer reading from your existing systems can handle that specific case on a flat monthly fee, without routing it through consumption-priced contact and send allowances it doesn’t need. See how to reduce CRM licensing costs for the seat-based version of this same over-provisioning pattern, and Salesforce Data Cloud’s consumption-credit model for a closely related mechanic — both bill by activity rather than by user.
Frequently asked questions
Does reducing Marketing Cloud user count lower this bill?
Not directly. Contact volume and send credits are the meter here, not named users — a smaller marketing team can still be sitting on a large, stale contact database driving tier cost.
Is Marketing Cloud Engagement the same product as Marketing Cloud Account Engagement (Pardot)?
No — they’re separate products with separate pricing models. Account Engagement is priced by edition and contact tier for B2B lead-nurture use cases; Engagement is the consumer-scale, credit-based platform this article covers.
Can we forecast send-credit consumption before a campaign push?
Salesforce provides usage-reporting tools inside the platform to check remaining allowance before a major send — worth checking ahead of any seasonal calendar, since overage rates apply once you’re past it.
Related articles
- Salesforce Account Engagement (Pardot) Cost Tiers
Account Engagement (Pardot) pricing jumps by tier and contact limit, not just by seat. Where the real cost sits and how…
- Salesforce Government Cloud Plus: The Premium Explained
Government Cloud Plus adds a reported percentage surcharge on top of standard product spend, not a separate per-seat pri…
- Salesforce Net Zero Cloud: Edition Pricing Explained
Net Zero Cloud bills as a flat per-org edition fee with a bundled license count, not per-seat pricing. What that means p…
- Salesforce Voice: Where Per-Minute Costs Stack on Seats
Salesforce Voice (formerly Service Cloud Voice) bills a per-user seat plus metered telephony minutes on top. How the two…