Skip to main content

#Marketing Cloud88 debatiendo

 A workflow challenge our marketing team keeps running into when managing campaigns in Salesforce Marketing Cloud is sourcing original quality Instagram media for use inside Content Builder. Many brands build their visual library primarily on Instagram but no longer have the source files saved locally once they are published. Instagram provides no built in export option which means those assets are inaccessible in original resolution through the platform itself. Low quality screenshots are not suitable for professional email campaigns or landing pages built in Content Builder. I found that indown mobi

 works well as a browser based solution that retrieves original quality files from public Instagram post URLs with no installation required. The retrieved files can then be uploaded directly into Marketing Cloud Content Builder as managed assets. Has anyone built a more automated flow using Marketing Cloud APIs that pulls Instagram media directly into Content Builder without manual retrieval as an intermediate step.  

 

@* Marketing Cloud Engagement * 

1 respuesta
0/9000

Our marketing team has been historically creating a new lead for each and every time a person "raises their hand" for a specific product -- like if they filled out a form online or attended a webinar or visited a both, etc. This has resulted in duplicate leads. We are working on correcting this, doing some de-duplication efforts, and making use of campaigns and campaign members to record what marketing interactions a person engaged with. This works but the sticking point is how do we track product interest

-- for example prospect was interested in Product A in January and Product B in July. Could be a current customer or someone we've never done business with before. 

 

My gut reaction is that we use opportunities for this -- every interest in a product is it's own opportunity record that they can work through all the stages -- however sometimes the sales person, account manager, BDR, or Solution Engineer finds out quickly that they are not actually qualified for that product and DQ the "lead" -- if we use opportunities like I was thinking -- we'd have a ton of "garbage" opportunities. 

 

We are migrating from Marketing Cloud Engagment (fka Exact-Target) TO Marketing Cloud Account Engagement (fka Pardot) -- so we are using this as an opportunity to clean house and fix processes 

 

Thoughts/Ideas on how to handle this? 

 

#Marketing Cloud  #Pardot B2b Marketing Automation

1 respuesta
0/9000
4 respuestas
  1. Hoy, 9:45

    Yes, that’s the expected behaviour. Furthermore, you need to grant access only to the intended Business Unit (BU), which will help ensure compliance with the least-privilege policy.

0/9000

Hello,

We manage a Marketing Cloud Business Unit that sends emails for multiple brands. We created a new Sender Profile for one of them (Brand B) with:

This Sender Profile is correctly assigned to the Send Classification and to the Email Activity in the corresponding Journey.

When sending a real test through the Journey, the From address correctly shows as Brand B, but the Reply-To address in the received email still shows the Reply Mail Management address configured at the account level (reply@mkt.brandaparent.com), instead of the Reply Email defined in the Sender Profile.

Questions:

  1. When Reply Mail Management is active at the account level, does it take priority over the Reply Email defined in an individual Sender Profile?
  2. If so, is there any way for a specific Sender Profile to use its own Reply-To address without needing to purchase an additional Private Domain?
  3. If this is not possible without a Private Domain, could you please confirm so we can document it internally?

Thank you. 

 

#Marketing Cloud

2 respuestas
  1. Hoy, 9:20

    Hi Himanshu,  

     

    Thanks for the help — the fix worked. Reply-To now shows correctly through the custom RMM settings on the Sender Profile. 

     

    Thanks again for the quick support. 

    Best regards, Juan Carlos

0/9000

Hi Trailblazer Community, 

 

I'm trying to start the badge Marketing Cloud Next Email Sending Essentials under the Data 360: Develop and Build Solutions trail, but I'm unable to create the required playground org.

Whenever I click on Create Playground, I get the following error message:

Error creating playground for Marketing Cloud Next Email Sending Essentials badge

 

 

I tried refreshing and waiting, but the issue persists. Has anyone else encountered this problem or found a fix? 

 

Thanks for your help!  

 

#Trailhead  #Trailhead Challenges  #Data360  #Marketing Cloud  #Trailhead Playground  #Trailhead Playground Management

5 respuestas
  1. Hoy, 2:10

    Hi @Santosh Gund

     

     

    I opened a case and received the following response. I think the only option is to wait until the matter is resolved. 

     

    Please be informed that the team is working internally to add more capacity to spin up the orgs related to orgfarm orgs related to the Trailhead. 

0/9000

Hi all,

What is the best way to add a real-time countdown timer to In-App Messaging in Salesforce Marketing Cloud (MobilePush)

for flash sales/limited-time offers? 

 

 

#Marketing Cloud  #Mobile  #In-App Guidance  #Campaigns

2 respuestas
0/9000

Please suggest the modules of Salesforce Marketing cloud which consist of hands-on tasks instead of MCQs. 

 

Please lemme know if anyone found it. 

 

#Trailhead Challenges  #Learning  #Marketing Cloud

1 respuesta
  1. Eric Burté (DEVOTEAM) Forum Ambassador
    15 ago, 21:57
0/9000

Hi, there we are trying out Distributed Marketing for Marketing Cloud Engagement in our Salesforce CRM Sandbox. 

 

The package has been installed, connect to Marketing Cloud Engagement, and a Journey is active in the correct Business Unit. 

 

I have also added the MCDM Campaign Message Component to a new tab on the Campaign record. Once Saved, I connect the Campaign to the Journey in SFMCE - I can search for it and select it, then Save. 

 

However, the Component simply tries to load and load, but nothing happens - see image attached. 

 

Any ideas why the MCDM Campaign Message Component just buffers?? 

Distributed Marketing > Campaign Message Component Buffering

 

Any help is very much appreciated. Thanks, Ian 

 

#Marketing Cloud

1 respuesta
0/9000

Not able to use CMS Image in HTML content block (for Landing Page).  Tried creating public URL with Content key, Org ID, Channel Id, and domain but still image is not loading on published page and preview page.   

3 respuestas
  1. Nobuyuki Watanabe (NAC / FPT Japan Holdings Group) Forum Ambassador
    12 ago, 22:43

    Normally, this kind of configuration shouldn’t be necessary. However, if the image doesn’t appear in the preview, try adding the domain of the image URL to your Trusted URLs.

    If that still doesn’t resolve the issue, I recommend opening a support case with Salesforce.

    https://medium.com/@marketingcloudtips/b3e1e8c9576f

0/9000

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 respuesta
  1. 12 ago, 14:14

    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