Skip to main content
Featured group

* Marketing Cloud Growth & Advanced *

Welcome! This group is dedicated to your success with Salesforce Marketing Cloud Growth & Advanced Editions. Join the conversation here to stay up to date on the product, learn best practices, and everything in between. Use this group to review resources, ask questions, help each other, and share experiences. --------------------------------------- This group is maintained and moderated by Salesforce employees. The content received in this group falls under the official Forward-Looking Statement: http://investor.salesforce.com/about-us/investor/forward-looking-statements/default.aspx

I’m currently working on Salesforce Marketing Cloud Next in a sandbox environment and I’m trying to understand the best approach for moving the entire setup and configuration to a UAT environment.    My questions are:

   

  • Can this be automated using VS Code + Salesforce CLI / metadata deployment?

   

  • Which types of configurations and assets can be migrated automatically, and which ones need to be recreated manually?

   

  • Are there any best practices for promoting configurations from sandbox → UAT → production in Marketing Cloud Next?

   

I’d also love to hear how you approached this in real projects and what tools or processes you used for deployment and version control.

   

Thanks!   

 

@* Marketing Cloud Growth & Advanced * @* Salesforce Developers * 

1 answer
  1. Aug 12, 2:14 PM

    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: 

      

    Dev Sandbox → Git/PR → Validate Deployment → UAT → Functional Testing/Approval → Production

     

     

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

    Metadata API deployable, API deployable, or manual/environment-specific

    . 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

    Marketing Cloud Next

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

     

0/9000

My client wants to send emails with PDF invoice attachments. Invoices are not static and unique per order. They will be housed in CRM. I know you can attach as PDF's in Marketing Cloud Engagement but are there any workarounds / custom solutions for Marketing Cloud Next? 

2 answers
0/9000

Subject: Domain configuration question - Marketing Cloud Advanced (MCA) implementation  Additional Information:

  • Environment: Production / Sandbox
  • Product: Marketing Cloud Advanced (MCA)
  • Priority: Medium
  • Project phase: Ongoing implementation

Description:  Summary:    Question about domain configuration during Marketing Cloud Advanced (MCA) implementation.  Details:    Hello, I am opening a ticket with Salesforce regarding an implementation I am carrying out in my organization. I am implementing Marketing Cloud Advanced (MCA) in my organization and I have a few questions.    My organization has two domains, which are mkt.dabelle.com.br and mkt.eico.com.br. I would like to know if it would be possible to continue using our current domains with Marketing Cloud Advanced, and how many domains are supported for registration?  Specific questions:

  1. Can we continue using our current domains (mkt.dabelle.com.br and mkt.eico.com.br) with Marketing Cloud Advanced?
  2. What is the maximum number of domains supported for registration in MCA?

Expected outcome:    Confirmation on domain compatibility/support and domain limits so we can proceed with the implementation planning.    

 

@* Marketing Cloud Growth & Advanced * 

1 answer
0/9000

After installation of Package and Kits, can we add one whatsapp number of sandbox(for testing) and then on production instance?  does this cause any issues? 

 

Also can we test this on my personal business account with SDO org?  I have been trying to connect but unable to connect with WABA since WABA requires verification.. 

Any insight on this? 

  

#MarketingCloudNext #MarketingCloudGrowth @* Marketing Cloud Growth & Advanced *

0/9000
7 answers
0/9000

Hi all,    We are on Marketing Cloud Engagement (ExactTarget) and we need to start sending RCS messages to customers.    I have checked our instance and I cannot find any RCS channel anywhere:  - Mobile Studio only shows MobileConnect, WhatsApp, MobilePush and GroupConnect.  - Journey Builder message activities are: Email, In-App Message, Inbox, LINE Message, Push Notification, SMS, WhatsApp and WhatsApp Session Transfer.  - No messaging connector under Installed Packages.    My questions:  1. Can anyone confirm that RCS is NOT a native channel in Marketing Cloud Engagement, and that it only arrives natively with Marketing Cloud Next?  2. If that is correct, what is the supported way to send RCS from Engagement today? I assume a third-party connector (Sinch, Infobip, Vonage, etc.) plus a Google-approved RBM agent. Is that right?  3. For anyone who has done this: does the connector need two-way messaging enabled to capture inbound replies? We need to capture an opt-out keyword that customers reply with, and write it to a suppression Data Extension.    Context: Google requires an opt-out option to approve the RCS agent. We already have the SMS side working natively with MobileConnect STOP keywords, and the opt-outs are synced to a shared suppression Data Extension. We want to reuse that same list for RCS.    Any confirmation or experience would be really helpful. Thanks!   

 

@* Marketing Cloud Engagement * @* Marketing Cloud Growth & Advanced * 

3 answers
  1. Jul 17, 3:33 PM

    Native RCS in Marketing Cloud Next (Summer 26) is a real capability, but it's worth being clear on what it actually gives you versus what people assume it gives you. 

     

    What it does: RCS as its own content type in CMS, sender ID authentication, rich cards and media. What it doesn't do: automatic capability detection. RCS coverage is still limited to a handful of countries, and even within a supported country you have no guarantee the recipient's device or carrier will render RCS. Native SFMC doesn't currently give you a single send that checks device capability and degrades gracefully. If you want that behavior today, you're building it yourself, meaning a decision split in Journey Builder with an RCS path and an SMS path, and some way to know which contacts can actually receive RCS before you route them. 

     

    That last part is the hard piece. Journey Builder branching logic is easy. Knowing capability ahead of the send is not, since SFMC has no native way to check that.

    This is the gap that third party connectors are built around. A few vendors (Sinch, Vonage, Vibes, Solutions by Text among them) layer transcoding and automatic fallback on top of SFMC specifically to solve this: one message activity, the platform decides RCS vs SMS at send time, no manual branching. Full disclosure... I work for Sinch, so take the specific example with that in mind, but the pattern holds across vendors, not just us: Sinch Omnichannel Connector

    works this way through Sinch's Conversation API sitting underneath Journey Builder. 

     

    If you're evaluating this for real, the questions worth asking any vendor are the same regardless of who you pick: how do they determine capability before send, what's the fallback latency, and do you keep unified reporting across the RCS and SMS legs or does it fork into two datasets.

0/9000

Hi Team, 

 

Thank you for response and clarification on Mc on core. 

 

As I'm currently exploring Consent Management in Salesforce, I came across the following objects:

  • Communication Subscription
  • Communication Subscription Consent
  • Communication Subscription Channel Type
  • Communication Subscription Timing
  • Engagement Channel Type

While I understood the purpose and usage of each object, I would like to get more clarity on the end-to-end data flow involved, particularly in the opt-in/opt-out scenarios.

For example:

  • If we are managing leads or contacts and a user opts out of a marketing communication subscription through the preference center, how exactly is the flow handled in the backend?
  • As per my understanding, MC1 Core doesn't provide a fully automated consent configuration, and inserting a consent record shows the status (e.g., opt-in/opt-out) at the record level, but the backend process and record updates aren't very clear.

Could you please help explain:

  1. When a user opts in to a communication subscription, what records are created or updated in the background?
  2. Similarly, when a user opts out via the preference center, what exact changes should we expect in the backend?
  3. Is there any automation or custom logic required to complete this flow, or is there a recommended standard implementation?

Looking forward to your guidance to better understand the complete flow and best practices for implementing consent management.

4 answers
  1. François Perret (Bamsoo) Forum Ambassador
    Jul 29, 2025, 2:30 PM

    @Aishwarya Pawar

     

    Hi, 

    First note that Salesforce Object are not used as it pertains to Consent Management in MCGA. Only the DMOs in Data Cloud are used. 

    The main DMO is Communication Subscription Consent which stores the Status as Records for a given Subscription and a given Email Address (for Email Channels). 

    In that DMO, you may have several records for a given Subscription and Email Address: the status of the latest record is used. If no records are found then the Status is opt out be default. 

    The Preference center handles autonomously the update / record creation in Communication Subscription Consent. 

    You can also manage Consent using an Import File, by hand on Leads and Contact (provided you added the Privacy Component) and by Flows. 

     

    Hope this helps 😎 

    #SharingIsLearning #MarketingCloudGrowth

     

    François. 

     

    PS : In order other Trailblazers to be pointed directly the most helpful answer, please do not forget to click “Accept this answer” below it.

0/9000

Hi, is there a sendlogging capability in Marketing Cloud Advanced?   

Would like to create a generic email used by multiple locales, and report on the volumes by locale. So (ideally) need to log the sendtime locale attribute (+ other attributes) to support reporting.  

Thanks  

1 answer
  1. François Perret (Bamsoo) Forum Ambassador
    Jul 9, 1:34 PM

    @David Agnew

     

    Hio David, 

    Not sure if the locale is stored, but all the informations related to email engagements (send, open, click, etc..) are stored in the Email Engagement DMO.

0/9000

We have a transactional email send use case and the calling application will not know the required SF IndividualId and/or the contact may not exist in SF yet. 

 

Documentation states requirement to provide IndividualId   

Send Transactional Messages Through On-Demand Flow | Manage Transactional Messages | Marketing Cloud Next | Salesforce Developers 

{ "inputs" : [ {   "EmailAddress" : "XXXXXXXXXXXXXXX@XXXXXXXX",   "IndividualId" : "XXXXXXXXXXXXXXXXXX"   } ] }

 

As per Nobuyuki Watanabe @marketingcloudtips - 

SFMC Tips #182 : Marketing Cloud Next: On-Demand Flows with REST API | by Nobuyuki Watanabe @marketingcloudtips | Medium

 "Note: Use an 18-digit Salesforce ID for the IndividualId. If you enter an ID that does not correspond to an existing CRM record, an error will occur during flow execution." 

Is there a way to bypass the IndividualId? and/or what alternative options are there?  

Thanks

3 answers
  1. François Perret (Bamsoo) Forum Ambassador
    Jun 26, 2:25 PM

    @David Agnew

     

    It will be reported at the dummy Individual level.

0/9000

Hello everyone,

Could you please help me with the following issue?

I'm using an Automation Event-Triggered Flow that is triggered whenever a Lead is created. The goal is to send a personalized message including the Lead's Name, Car Brand, and Vehicle Model.

For Email, I was able to achieve this by using an Apex Class, and it worked as expected. However, I now need to send the same personalized message through WhatsApp, and I haven't been able to make it work.

I also tried using Data Graph, but the WhatsApp message is not being personalized correctly, which is why I ended up using Apex for the email implementation.

Could you please advise on the recommended approach for sending personalized WhatsApp messages in this scenario? Is there a way to achieve this using Apex or another supported method?

Thank you very much for your help! 

 

@* Marketing Cloud Growth & Advanced *

1 answer
0/9000