* MC Account Engagement (fka Pardot) *

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)

@ishwarya k

Good news - that Pardot Developer Edition org does include Account Engagement, it just has to be switched on first. Steps: 

1. Gear icon (top right) > Marketing Setup, then set yourself as a Business Unit admin (assign your user to the Pardot Business Unit). 

2. In Marketing Setup, under 'Go Beyond the Basics', find 'Turn on Pardot Lightning App in Salesforce' and enable it. 

3. Then open the App Launcher (waffle icon, top-left) and search 'Pardot' (a.k.a. Account Engagement / B2B Marketing Automation) - it will be there. 

If it still does not show, confirm your user has the Pardot/Account Engagement permission set assigned. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!

Hi Mia,  

We have seen similar behaviour. Here are the most effective fixes and workarounds for this behaviour: 

Clear Session Locks:

Have the user open another email record, enter the builder, click Save & Exit, then return. Lingering session tokens often cause user-specific locks. 

Disable Browser Extensions:

Open the editor in an Incognito / Private window with extensions (especially ad blockers or Salesforce extensions) disabled, as they often block click events on nested layouts. 

Reset Browser Zoom:

Set zoom strictly to 100% (Ctrl + 0 / Cmd + 0); display scaling frequently breaks click targets in multi-column rows. 

Clone the Email:

Clone the affected Email Content record—this immediately clears corrupted layout DOM metadata and usually restores editability. 

Verify CMS/File Access:

Ensure the user has contributor permissions to any Salesforce CMS workspace or Asset Library folder used by the images inside that row. 

Thanks 

Siva

Hi Saad

Yes, there is. Under Marketing > Emails > Sent, click on the Name of the email you've sent. On the top right of the page that just opened, there's a "View Report" button. Click on that. Then you will see the report of the email sent, including Unique HTML Opens which are all the unique prospects that opened your email. 

If the email was sent as an email template, you could search for it through Reports > Marketing Assets > Email Templates. Then Navigate to Unique HTML Opens and click the hyperlink. This will take you to the page of all the prospects that opened your email template. 

@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 🙂