* MC Account Engagement (fka Pardot) *

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 

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.

@Dominika A

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.

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!

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.

@Charlotte Fabb

Those [PD-SYS] Proofpoint filters are system-managed by Salesforce, so the 1 April 2019 date is simply when they were provisioned to your account when you got Pardot — a static date is normal for system filters and doesn't mean they've gone stale or that you need to maintain them. The key point though: visitor filters only suppress website Visitor activity (page views recorded by your tracking code), not email link clicks — so they were never going to stop the bot clicks you're seeing against prospects. Those clicks come from email security gateways (Proofpoint URL Defense, Mimecast, Microsoft Safe Links) and university spam-protection tools that pre-scan every link before delivery; it's an industry-wide email issue that no visitor filter removes. Practical way to handle it: don't treat a single email click as a qualifying, scoring, or sales-alert trigger on its own — scanner clicks have tells (they fire within seconds of the send and usually hit every link in the email), so lean on those signals and require corroborating engagement (a form submission, or repeat visits across separate sessions) before you act on a click. If you use clicks in Engagement Studio or automation/completion actions, add a short time delay or a 'clicked 2+ distinct links' style guard so scanner traffic doesn't push prospects down the funnel. if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

Hi! I am on the same boat. I don't think is possible at the moment in MCAE to remove the tracking based on consent. Seems is an "all or no one" approach at the moment. That is at least what I understand from here  Tracking Pixels in Marketing Email Communications | Salesforce Help

Can someone confirm or deny? It can't be that salesforce module is not technicaly capable to follow current regulations... This was known already from April. 

Some help community? 

Thank you

An external action might suit you best here. 

Pass into the External Action the CRM ID (implies you've synced this Prospect to Salesforce) and the field that stores the desired sales rep.  The Autolaunched Flow that powers your External Action can then make the assignment with no issue.  For the form, you could have a completion action of assigning to a temporary queue until the Flow runs (typically 45s later)