Matik Mail now allows for sender dynamic content. This content can be used to populate the "From:" field in a Matik Mail template. Sender dynamic content is unique in that it must return three specific columns:
- From_name: the name to display for the sender
- From_email: the email address the message should be sent from
- Reply-to_email: the email address where replies should be sent to
If you’re using an API form to set up your dynamic content, we’ll automatically prompt you to specify which fields from your data source to use to populate the "From: Name", "From: Email", and Reply to Email:
If you’re using a SQL query, make sure that your query returns the 3 required columns.
Creating Recipient Dynamic Content
Recipient dynamic content can be used to populate the:
- To: field
- CC: field
- and/or BCC
Recipients' Dynamic Content must return data as a single column, with each email address represented as a new row.
Email Template Setup
Start by navigating to the Settings tab to configure your email.
Adding Recipients
Start by selecting the Recipient's dynamic content you would like to use. (If you haven’t created a list of dynamic recipients yet, click on “+ Create New Dynamic Content” to create a new list).
Once you’ve selected your recipient's dynamic content, you can specify whether to personalize your email on an input.
- If you select None: all recipients will receive the same content
- If you select an input: each recipient’s email will be personalized based on the corresponding value of that input.
You can only personalize an input that is used in your recipient's dynamic content. (If your recipient's dynamic content does not contain any inputs, then each recipient will have to receive the same content).
Example:
Adding CC or BCC
As a new option, you can add recipients to CC and/or BCC. Your email’s CC and BCC can be either static or dynamic.
Static
Manually input email(s) to CC/BCC. All recipients will have the same CC/BCC.
Dynamic
Use the Recipient's dynamic content to populate the CC/BCC. You will need to decide whether you want to personalize the CC/BCC settings for each recipient, or use the same CC/BCC settings for all recipients:
-
Personalize based on input:
- This option is only available if the recipient DC you’ve selected to populate the To: field contains an input to personalize on.
- Select DC that uses the input you’re personalizing on. The CC/BCC field will then be personalized for each recipient based on the value of the input.
- Same for all recipients: the email addresses returned by the selected DC will be used to populate the CC/BCC for all recipients.
Email to Salesforce
One use case for the BCC field is to send your emails to Salesforce, allowing you to log Matik Mail activity within your CRM. To do this:
- first ensure that the ‘Email to Salesforce’ feature is set up and configured at your org. See Salesforce’s documentation here: https://help.salesforce.com/s/articleView?id=sf.email_my_email_2_sfdc_landing_page.htm&type=5. You’ll need to configure the following in Salesforce:
- Turning on the “Email to Salesforce” feature
- Enable unique Send to Salesforce emails for desired users
- Deciding how emails should be displayed and mapped to Objects in Salesforce once sent
- Then, set the BCC field in your Matik Mail template to populate with the relevant ‘Email to Salesforce’ address
If desired, you can use Dynamic Content to retrieve relevant ‘Email to Salesforce’ email addresses from your Salesforce org. To do this:
- Create 1 piece of Dynamic Content that retrieves the unique ‘Email to Salesforce’ domains from your SFDC
- Create a new Data-Driven piece of Dynamic Content, using Salesforce as your data source.
- Set up your DC to pull the following:
- From Source API = Objects
- From Salesforce Object = EmailServicesAddress
- With the Fields to Return: Email Address Domain
- Filtering on Function: Email Service Name = EmailToSalesforce
- Apply any desired filters. (For example, filtering for the ‘Email to Salesforce’ address of a particular CSM, based on an input).
- Then, create a second piece of Recipient's dynamic content to concatenate the parts of the email into an email address.
- Create a Google Sheet, where:
- One cell will accept the Email Address Domain from Salesforce
- One cell will concatenate that with ‘emailtosalesforce@’
- Create a Google Sheet, where:
- Create Recipients DC based on this Google Sheet, returning the concatenated full Salesforce email
You can now use this Recipients DC in the BCC field to send the Matik Mail emails to Salesforce.
Adding a Sender
This is where you configure who your emails should be sent from. Your sender settings can be Static or Dynamic.
Static
Manually input your sender settings:
- From Name: the name that should appear in the From field
- From Email: the email address the message should be sent from
- Reply-to Email: the email address that replies should be sent to
These settings will be applied across all recipients.
Dynamic
You can also use Sender dynamic content to populate the From field. As with the CC: and BCC: fields, you can choose to personalize the Sender settings for each recipient or use the same Sender for all.
-
Personalize based on input:
- This option is only available if the recipient DC you’ve selected to populate the To: field contains an input to personalize on.
- Select the Sender DC that uses the input you’re personalizing. The From field will then be personalized for each recipient based on the value of the input.
- Same for all recipients: the senders returned by the selected DC will be used to populate the From field for all recipients.
NOTE: If you opt to use Dynamic Sender, your end users will not be able to edit the From field on their side.
In addition, you will also need to decide how to handle cases where the Sender DC returns an email that is not an authenticated email address for your org:
- If you choose not to specify a Fallback Sender: emails with that sender will not be sent, and Matik will throw an error you know that this is due to an Invalid Sender
- If you choose to use a Fallback Sender: you’ll need to select an authenticated email address to use as your fall sender. Then, if your Sender DC returns a non-authenticated value, we’ll still send the email, but populate the From field with your Fallback Sender.
Comments
0 comments
Please sign in to leave a comment.