Email production

Tables

When coding an HTML email, most developers prefer to work with tables. Tables are easier to troubleshoot during the QA process and work better with most email clients. The type of table used will depend on the developer, as some prefer to use stacked tables while others prefer to use nested tables. Stacked tables are generally recommended, as the code is more flexible and works better with email clients.

To ensure that layouts are consistent across email clients, we recommend using the following inline properties:

• cellpadding = 0
• cellspacing = 0
• border = 0

We also recommend adding the following code inside the <style> tag that serves as an additional global CSS reset to ensure consistency:

• table { border-collapse:collapse; mso-table-lspace:0pt; mso-table-rspace:0pt; padding:0;}
• table td {border-collapse: collapse;}

Preheader Text

One of the best practices of developing HTML emails is to include preheader text above the initial design. This is the text that will be included in the preview section that most email clients show. Some developers disguise this text in the body of the email by changing the font color to transparent or having it blend in with the background. You don’t want your email open rates to be negatively affected by not including this crucial text above the design.