Skip to main content
Featured group

* MC Account Engagement (fka Pardot) *

Welcome! This group is dedicated to your success with Salesforce Marketing Cloud Account Engagement. 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
Discuss this in Slack for faster answers and real-time help.

Hi there! 

I need guidance for triggering an Account Engagement (Pardot) email when a Service Cloud Case is closed. The email template includes details for the Contact on the Case to rate their experience.

  

 I have created a new custom object in Sales Cloud 'Case Communications' and imported that into Account Engagement. The custom object has lookup fields to Contact and Case. A new record triggered flow has been created in Salesforce to trigger in Case closure and various other criteria to create a record of the Case Communications object with a boolean flag that will be set to true when the communication needs to be sent out. A segmentation list and an automation rule has been created in Account Engagement. I am finding it difficult to proceed with the next steps on the engagement studio. 

  

 Note: 

 This is being implemented directly in our Production environment therefore the Salesforce flow has been setup to trigger only for a test account.

Hi There,    I was trying to create a B2BMA Dashboard with Prospect Engagement metrics, mainly the page visits info like URL or page title that we get on Activity in Pardot and Engagement in CRM. I tried using Engagement And Prospect Activity Datasets to get this but it doesn't seems like pulling this info. What I get it the Activity= visit and Asset= website. Not sure how can I get the url details :( Kindly Help 🙏🏼🙏🏼   Following this one https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007W5odOSAR  @* MC Account Engagement (fka Pardot) * #Pardot B2b Marketing Automation

4 answers

I want to limit how many new prospects enter an Engagement Studio program each day. Is there a native way to cap daily enrollment, or a recommended workaround using automation rules or lists? The goal is to control new program entries per day while allowing prospects already enrolled to continue through the program.  

 

Thanks in advance!

1 answer
  1. Oct 27, 4:33 PM

    I think there’s no native daily enrollment cap in Engagement Studio. The recommended approach is to control entry through the program’s recipient list and add prospects to that list in controlled daily batches. Prospects already enrolled can continue through the program normally. Automation rules can help manage eligibility/list membership, but they don’t provide a true “X prospects per day” throttle. For a strict numerical daily cap, you’ll need an additional batching mechanism upstream of Engagement Studio.

Hi all -- does anyone know the latest on dropping HTML from a 3rd party email builder into the "New Email Experience" / Marketing Cloud Next Email Builder. I remember seeing some workarounds/tips about a year ago, but I can't seem to find them...and perhaps it's been updated since then.

1 answer
  1. Oct 28, 4:34 PM

    Hi Luke, I haven't seen a reliable way to import a full HTML email directly into the new builder yet. You may be able to paste HTML into individual code blocks, but that's not quite the same thing. I'd also test the output carefully, especially mobile layouts and tracking links. 

Since i started working at my current company in Salesforce - I wandered for far too long 'Why dont we have a 'leads' object and only 'Prospects' in sales cloud of salesforce (not MCAE).  

 

I recently found out that our Leads table was renamed to 'Prospects' about 5 years ago by an individual who no longer works for the company. They went into 'Rename Tabs and Labels' settings and did this which made the labels appear ootb showing 'Prospects' in Sales cloud wherever i was expecting to see 'Leads'.  

 

My question now - to clean things up so we can have a better structure of MCAE "Prospects" to "leads" to "Contacts" - i am planning to reset the rename of the Leads BACK to "Leads" and not "Prospects". I have done this in 2 of our sandboxes and everything seems to be pretty fluid and relatively quick depending on how much data you have.  

 

Could there would there be any API field name issues when thinking about integrations if i were to go in and rename the "leads" back to "LEADS"? 

 

Thanks!!! 

 

@Who owes me a beer?!? @Admin Group, Dallas, US @Trailblazer Community Cove @Salesforce.org System Administrators @* MC Account Engagement (fka Pardot) * @Reports & Dashboards 

3 answers
  1. Oct 27, 8:49 PM

    You're good to go unless something was terribly designed (integration or automation wise).   Standard practice shoudl be to refer to everything by API name vs the label.   The previous admin would not be able to rename a standard object API name. 

     

     

    Cheers!

We have a Text field in MCAE having Record and display multiple responses.

Syncing with Lead object in Salesforce, that is Long Text field. But the issue is that in Salesforce only latest updated value synced and override from MCAE. We need all multiple responses in salesforce as well. 

Then what we need to do. 

Thank you 

Sumit

2 answers
  1. Oct 23, 5:35 PM

    To preserve all historical form submissions and responses in Salesforce rather than letting them get overridden, you should implement one of these two standard architectural workarounds: switch to custom append flow

Hi everyone,   

I am running into a frustrating issue with the Lightning Email Builder (New Email Experience) in Account Engagement (Pardot) regarding a Custom Preference Center, and I would love to get your insights or alternative solutions.   

The Problem: It seems the new Email Builder strictly forces merge tags to point either to Data Cloud or the default Pardot Preference Center. Whenever I try to insert my custom preference center link or modify the merge tag with the custom center token, the system throws an error and prevents me from saving the email.   

The Proposed Workaround: I raised a ticket with Salesforce Support, and the technician suggested the following workaround:

My Concerns:

  1. Deliverability & Phishing Risks: I am deeply concerned that email clients might flag the email as phishing or spam due to the hidden HTML text/links. Has anyone used this workaround in production? Did it impact your deliverability?
  2. Data Cloud Alternative: I know I could potentially build the preference center within Data Cloud, but due to current bandwidth and timeline constraints, this would take way too much time right now.

Has anyone found a cleaner way to bypass this validator in the new builder without risking deliverability?     Any advice or best practices would be greatly appreciated!   

Thanks in advance,   

 

@* MC Account Engagement (fka Pardot) * 

4 answers
  1. Oct 15, 2:54 PM

    Yes, Luke. What I had to do was add two subscription management buttons to the email. One is the global unsubscribe button, which is a little less prominent and intuitive visually, but it's still visible if you pay attention. 

     

    Then I added a much more prominent button to m 

    Yes, Luke. What I had to do was add two subscription management buttons to the email.

     

    anage subscriptions at the list level. This button redirects users to a custom preference center that only displays the subscription lists associated with the specific brand featured in that email.

    So, for both brands, I've configured the email templates with a footer that links to their respective brand-specific preference centers. 

     

    The global unsubscribe option, on the other hand, prevents contacts from receiving any further marketing communications from our entire Salesforce instance.

We are planning to do mass delete contact records in 'inactive' status in Salesforce. 

We want also related pardot prospect to be deleted.

Do you know how we can achive that?

 

@* MC Account Engagement (fka Pardot) * 

3 answers
  1. François Perret (Bamsoo) Forum Ambassador
    Jun 22, 2023, 8:11 PM

    @Dominika Purwin

    Hi Dominika,

    Deleting Leads or Contacts from Salesforce will put the synced Pardot Prospect Record into the Recycle bin. Hence you have nothing to do, just mass delete in Salesforce, Pardot will follow. Later on you may want to empty the Recycle Bin by permanently deleting the Prospect.

    Hope this helps 😎

    #SharingIsLearning #AccountEngagement

    François.

How can I create a report with a prospect's first touch campaign?  

The custom report type Campaigns with Influenced Opportunities (Customizable Campaign Influence) seems to be related to Opportunities

2 answers
  1. Oct 12, 6:07 AM

    Hi @Sheeba Baig, 

     

    You can achieve this by using B2B Marketing Analytics (B2BMA) inside the Analytics Studio

    tab: 

     

    1. Multi-Touch Attribution Dashboard: Out of the box, B2BMA includes a Multi-Touch Attribution dashboard where you can apply filters to select the First-Touch Attribution Model alongside other dimensions.
    2. Advanced Customization (Advanced/Premium Editions): If you need custom fields or logic, open Data Manager in Analytics Studio. From there, you can modify Data Assets, Recipes, and Dataflows/Datasets to tailor the attribution metrics to your business needs.

    For step-by-step guidance, check out the official Salesforce documentation on B2B Marketing Analytics Setup

    . 

     

    If this helps resolve your question, please mark it as helpful/upvoted!  

     

    Cheers!

Hello experts, 

 

We're starting to plan our move from Marketing Cloud Account Engagement to Marketing Cloud Next, and I would love to hear from teams who are a few steps ahead. :) 

 

What's the recommended approach to migrate and what key considerations should we keep in mind around data, consent, automation, and running both platforms in parallel? Any lessons learned from teams who've been through it would be really helpful. Also any supported process documentations would be helpful as well. 

 

Our current setup: 

 

  • Account Engagement Enterprise Edition, Connector v2, a single production business unit, and a 2M+ prospect database.
  • Engagement Studio, scoring and grading automation rules and External Activities are core to how we operate today.
  • Data 360 and Agentforce are already enabled and configured, so we aren't starting from zero on the data foundation.
  • Connected Campaigns is only partially enabled.
  • Marketing Data Kits Still needs an upgrade

 

Thank you so much in advance! :)

6 answers
  1. Oct 11, 5:01 PM

    Lakshit, 

    What you read matches what I've found. To ensure deliverability you do not want the same domain authorized in 2 different systems with different DNS records.  So I'd plan on authenticating a second sending domain in Next. I am using a new subdomain.  The IP is a separate question from the domain. Next starts you on shared IPs and moves you to dedicated ones automatically as your volume grows, so I wouldn't count on your MCAE IP reputation coming with you either. 

     

    Before you commit to a plan, I'd get your AE and a Salesforce deliverability specialist to confirm in writing what's possible for your exact domain. Then run both side by side for a while. Keep MCAE sending the way it is, stand up Next on its own subdomain, start with your most engaged people, and ramp up slowly. Grab your current bounce and complaint numbers first so you have a baseline to compare against. 

     

    Regarding your mention of "partial connected campaigns" What do you mean by partial?  I believe only necessary if you want to retain the campaign history. If you some campaigns are old and do not matter, no need to make them connected now.  

     

    I would 

    1. List the unconnected campaigns and sort them: keep, merge, or ignore (old tests, duplicates).
    2. Connect the keepers. A few can be done by hand; many can be matched in bulk
    3. Check campaign record types, since campaigns with a record type that isn’t set to sync won’t come across.
    4. Then decide on “Use Salesforce to manage all campaigns,” which makes Pardot campaigns read-only. The prerequisites page doesn’t list this setting as required for Next, so I’d treat it as recommended, not mandatory.

    I'm working through Next alongside Account Engagement right now, so I'm happy to compare notes if that would help.