Email Footer Best Practices - Social Icons | Community
Skip to main content
S_D1
S_D1
Level 3
Mar 31, 2021 10:05 PM UTC
Solved

Email Footer Best Practices - Social Icons

Hi,

 

Is there any best practices around email footers? Do we absolutely need social icons?

 

Thanks,

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Dave_Roberts
Dave_RobertsAccepted solution
Level 10
Apr 1, 2021 2:55 AM UTC

I don't think you need social icons, but most of the business email and landing page footers I've seen have them in there somehow. 

 

In terms of best practices, you'll want to include:

1) an unsubscribe link

2) a physical business address

3) links to privacy policy, terms of use, etc (legalese) 

 

In terms of implementation, I'd recommend using snippets for the header and footer modules so that you can quickly update the snippet and make one-to-many changes when things need to get updated (like a rebrand, or new social channel, etc). Snippets also come in handy for translations if you're working across different geos.

View reply

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
Apr 1, 2021 3:58 AM UTC

Agreed with Dave that there certainly is no "absolute need" at all.

 

But one thing to remember, if you do include social links, is mail scanners will simulate Clicked Link on the links. And (like with all 3rd-party links) you won't have a subsequent Visit Web Page, let alone Filled Out Form, to have a reference point for how many were human clicks. So don't take clicks on these links as significant. You may even want to set them to untracked.

Translate
    Dave_Roberts
    Dave_RobertsAccepted solution
    Level 10
    Apr 1, 2021 2:55 AM UTC

    I don't think you need social icons, but most of the business email and landing page footers I've seen have them in there somehow. 

     

    In terms of best practices, you'll want to include:

    1) an unsubscribe link

    2) a physical business address

    3) links to privacy policy, terms of use, etc (legalese) 

     

    In terms of implementation, I'd recommend using snippets for the header and footer modules so that you can quickly update the snippet and make one-to-many changes when things need to get updated (like a rebrand, or new social channel, etc). Snippets also come in handy for translations if you're working across different geos.

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...