Budget credits for a Marketing Cloud Next sandbox before you test
Marketing Cloud Next sandboxes can consume Data 360, messaging and Personalization credits. How to test safely and promote changes without a surprise bill.
Winter '26 introduced sandboxes for Marketing Cloud Next: build and test away from production, then promote changes into production. The release note carries a line that matters more than the feature itself: sandboxes can consume credits for Data 360, messaging and Salesforce Personalization. A test send is still a send.
- Product
- Marketing Cloud Next
- Edition
- edition not stated in the source
- Topic
- Setup
- Confidence
- Medium - shown in a credible source
- Last verified
Who this applies to
- Admins and marketers who test campaigns, segments or personalisation before releasing them
- Anyone who owns the consumption budget for Data 360 or messaging
- Edition: not stated in the release note summary we checked
Why it matters
Teams coming from Marketing Cloud Engagement are used to sandboxes being free of consequence. In Marketing Cloud Next the platform is consumption-priced, and the sandbox draws from the same kinds of credit as production. A developer looping a segment refresh, or a QA run that sends to a thousand test contacts, shows up on the bill.
Try it
- Agree who owns credit consumption and give them visibility of sandbox use as well as production.
- Set a rule for test audiences: a small, named test segment for sends, never a copy of a production segment.
- Limit segment refreshes and personalisation evaluations in the sandbox to what a test actually needs. Turn off scheduled refreshes you set up during a build.
- Use the sandbox for what it is good at: validating a flow, a template or a data mapping before promotion. Do volume or performance testing only with a budget agreed in advance.
- Promote changes to production through the sandbox's promotion path rather than rebuilding by hand, so the thing you tested is the thing that ships.
Example use case
An agency builds a five-step onboarding campaign for a client in the Marketing Cloud Next sandbox. Instead of testing against the client's 40,000-contact welcome segment, the build uses a 25-contact test segment with the same field coverage, runs the flow end to end twice, and promotes. The client's credit report for the month shows the sandbox as a rounding error rather than a surprise.
Prerequisites, limitations and risks
- A Marketing Cloud Next sandbox, available since Winter '26. Whether one is included with your edition or purchased separately is not stated in the source
- The source states that sandboxes can consume credits for Data 360, messaging and Salesforce Personalization. It does not state rates or exemptions
- Test messaging still needs real, consented channels behind it if you send to real numbers or addresses
- Edition and permission requirements are not stated in the summary we used
Documented behaviour above comes from the sources listed below. Availability varies by edition, SKU and region - confirm entitlements in your own org before you rely on a feature.
Sources
Stuck on this in your own org?
Blueport is a Sydney-based Certified Salesforce Consulting Partner with 100+ implementations since 2018. If a step above does not match what you see in Marketing Cloud Next, tell us - it is either an edition difference or a change worth knowing about, and we will find out which.
Talk to our team