Hot answers tagged

5

When you schedule an email in SFMC, the following process is done: Email Content (HTML and AMPScript from all associated content areas or other assets) is stored in a 'snapshot' at time of schedule. All associated Properties (subjectline, preheader, deliveryprofile, audience,etc.) are stored inside job 'snapshot' similar to content Although the Sendable ...


4

Go to Email Studio > Admin > Account Settings and find the Headers and Footers section. You can turn it on and off there: Click on "Edit" and choose whether you want to use the system footer, your own or none. EDIT One more place where you can enable/disable headers and footers, is Email Studio > Delivery Profiles > Default - in each deliver profile, you ...


2

You do this with Auto-Response rules: https://help.salesforce.com/apex/HTViewHelpDoc?id=creating_auto-response_rules.htm Setup --> Case Auto-Response Rules You can check here to see if you have any existing rules. You can create a new rule and then rule entries. The entries act in an order and when the incoming case comes in it goes through these until it ...


2

Salesforce is aware of this, and I have been told a fix will be implemented, allowing you to use RedirectTo with an anchor tag in near future. Currently, you can have tracking parameters appended correctly with an anchor tag at the end, if you use standard links without RedirectTo, or use the dirty hack of jake314159


2

This is definitely hacky, but it has worked for me in the past. You'll need to open a ticket with SFMC Support to request an update to your WAC string, so that the very last parameter name in your query string can be used your very last Additional Email Attribute. So if you already have and use 5 AdditionalEmailAttribute's, then this solution won't work. ...


2

Adding here as I spent a few hours trying to figure this same issue out last night. As this answer states, you do need to set up the send definition using REST API. You cannot use the UI to set up the send definition for transaction API driven emails. It's called out here: https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/...


2

I haven't encountered this problem - however regarding "good practice" you have made the right decision to use a value that is not an email address for the recommendations. The IGO identifies a user by whatever value you give it during the "Set User Info" call in the Collect Tracking Code configuration. Note that "SubscriberKey" can sometimes render as an ...


1

It doesn't appear so in Lightning as I experience the same functionality you are seeing on accounts. This was in the Winter 20 Release Notes where it seems to give what you're asking for, but only on the email publisher on Cases in Service Console. Looking at the documentation for sending an email from a record in Lightning, it doesn't seem to specify ...


1

This is not possible. Formula fields have no stored value - their values are calculated at the time of accessing the data. There is no change event to which you can react for formula fields. You'd need to build your automation to react to changes to the fields that themselves drive the value of your formula field. You could potentially implement "ignoring ...


1

I ran into this on our fresh instance of the NPSP. I got the same useless error message when I followed documentation to send the acknowledgment email. I figured out that the "Opportunity Email Acknowledgment" Workflow Rule was Disabled by default. Steps: • Go to Classic Setup and do a search for "Opportunity Email Acknowledgment". • Select the ...


1

Reference This will not send any emails to Community users. The records are simply replicated into your partial sandbox and the user's email will appended with .invalid. Contact emails will not be changed, however, so those will need to be updated if you have any workflows or processes that may email them. Email Deliverability is set to "System Email Only" ...


Only top voted, non community-wiki answers of a minimum length are eligible