#Marketing Cloud91 personnes en discutent

Hi @Aline Bin Cardoso

As you correctly write, there is no native way to do this, and I will also advise against automating this. And why so? Different channels have different purposes.  

An email is best suited for longer formats, showcasing most recent product launches, giving a tour of your latest holiday destinations, or allowing the recipient to look through an entire agenda for an event. This is not something you will do in a text message.  

Text messages are IMHO best suited as a more transactional and concise channel. It can be to notify you about an upcoming appointment, a package being delivered or similar. This is a very efficient channel, seeing high engagement rates, but hence also the most intrusive one, as a text message received often results in instant notification on the recipient's phone - while most email clients nowadays receive the emails more discretely. 

App push is relying on the user having the app installed, and similar to text messages, is best suited for small short messages - which also often refer to features being supported in the app, and not just a simple CTA opening a landing page in the browser. 

Let me know should you have any questions, Aline.

Good question, and one I'd like to answer properly, but the honest answer is that the shape of what you build changes completely depending on a few things you haven't told us yet. So let me ask rather than guess. 

First, a snag in the input list. You've got conversion rate, AOV and revenue generated as separate inputs. Those can't all be independent, either revenue is derived (contacts × CR × AOV) or it's measured from actual order data. If both, the calculator can disagree with itself on day one. Which is it meant to be? 

Is this a forecast or a scorecard? A pre-launch business case with sliders and ranges, and a post-launch "what did this actually earn us" report, are two different artefacts. Same formulas, completely different data sources and completely different build. Most of these tools get abandoned because they try to be both. 

Are your journeys always-on or campaign-shaped? For an always-on journey, ROI isn't a number, it's a curve. Contacts keep entering, conversion rate drifts, build cost is sunk and shrinking per contact over time. You'd need entry cohorts and a payback view, not a single figure. 

Do you already have holdouts running? This is the big one. Without a control group you're not measuring incremental anything, and no amount of formula design fixes that. If you do have them: are they persisted per contact, or re-rolled with Random Split on each entry? And is there a global holdout as well as per-journey ones? (Per-journey lifts don't sum to portfolio lift, and the gap matters.)

Where do revenue and cost data actually live? MCE has neither revenue nor margin nor cost of goods. That pushes the actuals half of this toward Data 360 / your warehouse / Tableau, with MCE contributing engagement and holdout membership. Is that available to you, or are you constrained to build inside MCE? 

Who owns the cost-avoidance assumptions? Cost avoidance is where business cases go to get manufactured. If Finance hasn't signed off on "cost per deflected call," it's a soft number and should be flagged as one. 

One last thing, said kindly: most of this question isn't really MCE-specific. Incrementality design, control-group methodology, margin vs revenue, cost-avoidance taxonomy: that's marketing measurement, and it would be true if you were running Braze or a spreadsheet. The genuinely MCE-shaped slice is narrow: how to persist a holdout flag so it survives re-entry, how to get engagement data out into something that can join it to orders, and whether a Cloud Page + assumptions DE is a sane place to put the front end. Happy to go deep on that slice here, since that's what this group is good at. 

For the measurement-design half you'll get better answers where the analytics and architecture folks hang out. The Marketing Architects group, or a Data 360 / Tableau group. Genuinely worth cross-posting; it's a good question, just a two-venue one. 

Tell me which of these apply and I'll happily go into the formulas with you.

Yes, you can automate part of the Sandbox → UAT → Production promotion, but I wouldn’t treat Marketing Cloud Next as a “deploy the entire org with one metadata package” scenario yet. 

My approach would be: 

1. Use Salesforce CLI / VS Code + source control for components that are exposed through Salesforce Metadata APIs and are supported for deployment.
2. Keep all deployable metadata in Git and promote the same version through Sandbox → UAT → Production rather than rebuilding it separately in each environment.
3. For Marketing Cloud Next-specific assets/configurations, first verify whether that particular component is exposed as deployable metadata. Some configuration, connections, credentials, environment-specific settings, and certain marketing assets may still require manual configuration or a separate API/process.
4. Maintain an environment configuration checklist for anything that cannot be source-controlled, especially authentication, endpoints, integrations, permissions, and environment-specific IDs.
5. After deployment, run validation/smoke testing in UAT before promoting the same release to Production.

For a real project, I’d structure the pipeline roughly as: 

The important part is to inventory the Marketing Cloud Next components first and classify each one as

. That prevents surprises when trying to promote the complete setup. 

I’d also be interested to hear if anyone has implemented a fully automated CI/CD pipeline specifically for

, particularly which newer MC Next assets they’ve successfully managed through Salesforce CLI/Metadata API. 

1. Are all these new contacts some which have opted in to campaigns (the list seems quite big)?
2. Why are you importing them manually? You must maintain a system of record for their consent.
3. If the contacts share the same contact key as your existing ones, they will not create duplicate/additional billable contacts.

I have so many questions to your way of working, before advising on how to solve the problem with overage on contacts. Normally you will have a quite stable volume of contacts which will increase gradually over time. If you suddenly bring 200k new records in, my alarm bells start ringing.

Hi @Ivan Sholok

-  

Have you looked at this already:

Thanks

Your Salesforce AE should be on top of which SKUs are to be included here, as this can change quite frequently. The bottom line is, the MCE+ SKU is free of charge, but only includes very basic consumption. Once you start ingesting data to Data 360, running identity resolutions and unifications, as well as segmentations, the cost can quickly go up. So it is important to move slowly, and keep an eye on your Digital Wallet in Data 360, which gives you an insight about how many credits you are spending. 

It is always a good idea to purchase these flex credits beforehand, as you will otherwise be paying a premium price due to overage.