Send classifications define parameters for an email job in a central location. The account can reuse those parameters for multiple email send definitions. For example, you can create a send classification that’s used every time a message is sent to make sure that it always uses the appropriate parameters. Select a send classification, together with content information and audience information, when you define a message send by creating a message interaction.
Send classifications include these components.
- Delivery Profile
- Sender Profile
- CAN-SPAM (Controlling the Assault of Non-Solicited Pornography and Marketing) classification
You create the delivery profile and sender profile separately before you create the send classification. You can override the delivery profile and sender profile on the send classification when you include the send classification in a message interaction.
Define the CAN-SPAM classification as Commercial or Transactional.
- The CAN-SPAM Act defines a Commercial email message as "any electronic mail message the primary purpose of which is the commercial advertisement or promotion of a commercial product or service." Commercial messages must include a mechanism to unsubscribe, the physical mailing address of the sender, and a notice of advertisement if unsolicited. For commercial messages, we check for the presence of an unsubscribe link.
- Transactional messages, per CAN-SPAM, are primarily emails that "facilitate, complete, or confirm a commercial transaction that the recipient has previously agreed to enter into with the sender." Per the FTC, to be considered "transactional" per CAN-SPAM, the subject line must be transactional in nature and non-promotional. Also, the email body must present the "transactional content" before the commercial content. For transactional messages, we don’t check for the presence of an unsubscribe link. If you’re unsure of the classification, we recommend that you check "commercial" and provide an unsubscribe link. This information isn’t legal advice. Talk to your legal counsel for the proper application for your organization.
Salesforce requires that all Engagement messages comply with CAN-SPAM, regardless of the sender or recipient destination country. Because Salesforce is headquartered in the United States, messages sent from Engagement must comply with US law. Also, US-based ISPs with a strong international presence, such as Yahoo and Hotmail, similarly require that messages received comply with the law. These guidelines comply with best practice standards applied by most ISPs and email receivers worldwide.
Create a transactional send classification, then choose whether sends using that send classification honor the opt-out list associated with your chosen list. If you decide to honor the opt-out list, the system doesn’t send messages according to this logic.
- User-initiated sends to a list don’t include subscribers who opted out of the list.
- Global and business unit unsubscribes don’t affect the publication list for transactional sends.
- User-initiated sends to a data extension don’t include subscribers who opted out of the related publication list.
- Triggered sends with an associated list don’t include subscribers who opted out of the list.
- Triggered sends with an associated list and data extension don’t include subscribers who opted out of the list.
- Triggered sends with no associated list can’t track unsubscribe requests, regardless of whether there's an associated data extension. These sends can’t exclude unsubscribed subscribers from the send.
- Journey Builder triggered sends with a Publication List of All Subscribers can’t track unsubscribe requests. These sends can’t exclude unsubscribed subscribers from the send.
If you decide not to honor the opt-out list, emails that use the send classification don’t include an unsubscribe link.
Use a send classification to save time and effort and avoid the risk of human error. If the parameters included in the send classification don’t change, you don’t need to repeat the steps in the wizard process for each send.
The send classification also provides a greater degree of control, letting you perform tasks yourself rather than request intervention from Salesforce.
- Default
- Channel
- Owner
- Or a name that starts with User:
- Sender Profile
A sender profile specifies the From information for a send in a central location. Email Studio reuses that information across multiple sends without requiring selection each time. The sender profile contains the name and address that the message appears to be from in the subscriber's email client. - Create a Sender Profile
Follow these steps to create a sender profile in Marketing Cloud Engagement Setup. - Delivery Profiles
A delivery profile in Marketing Cloud Engagement Setup specifies the delivery information for a message in a central location. Engagement reuses the information across multiple sends without requiring selection of the information each time. - Create a Delivery Profile
Follow these steps to create a delivery profile in Marketing Cloud Engagement. - Create a Send Classification
Follow these steps to create a send classification within Marketing Cloud Engagement Setup. - Sender Header Support in the Sender Profile
A sender header helps sender deliverability for those users sending on behalf of someone else. You can enable Sender Header in your Sender Profile feature to store a header name and address. Your sender header name and address can use static or dynamic values. For static sender header information, enter the values into the fields. To use dynamic sender information, include a personalization string in the fields. You can use sender headers with Reply Mail Management in Marketing Cloud Engagement. - Send Email Messages from Multiple Addresses Via Sender Profiles and Data Extensions
It's possible to send a single email and direct all replies directed to a subscriber's individual representative with Marketing Cloud Engagement. You can also create multiple sender profiles to handle different aspects of your business email sends. For example, you can use one sender profile can handle normal commercial email, another for transactional, and a third one for special offers. This method maintains your corporate branding and makes sure that information sent out remains consistent. You can also use list attributes to populate substitution strings for enhanced sender profiles instead of data extensions.