Email Compliance List Unsubscribe Header Assumptions & Limitations

There are some assumptions and limitations to be aware of when using the List Unsubscribe Header.

• Merge Fields
  • Merge fields from the contact object are supported and need to be entered with the syntax {!Contact.FIELD}
    • EX: https://unsub.example.com/unsub/me?contact={!Contact.Id}&name={!Contact.Name}
  • For long values over 255 characters, the value should be placed in a field/formula on the contact object and specified as a merge field
• {!Contact.Id} will be resolved to the 15 character Salesforce Id. To use the 18 character Salesforce Id, use {!CASESAFEID(Contact.Id)}
• Different email clients A Company is the organization where the contact works. This can also be called the Client. can handle the unsubscribe headers differently and might only support one, or both URL and mail-to implementations. Check with the email providers to see what they support.
• List-Unsubscribe header will not be added if the 2020 Email Editor Send as a single email to all recipients checkbox is enabled.
• Adding List Unsubscribe Header to emails is only supported for emails sent out to Contacts A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact). entered in the email To field.