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:
- 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?
- 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,
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.
