Troubleshooting HTML rendering in test emails
If your Test Email looks off, we recommend that you…
Check HTML setup
First, confirm with your developers that your HTML is set up properly.
Certain Chrome extensions will cause issues with Braze’s email editor (one example is Grammarly). If you’re using one of these, you should either:
- edit Braze emails in a browser that does not have Grammarly
- contact your Braze account manager and ask to flip your email editors to HTML only/plain text.
NB plain text view removes your
WYSIWYG (what you see is what you get) editor, so you should first ensure that all team members are comfortable with HTML before making this request.
Emails render differently on different browsers and email clients. Record which browsers and email clients you’re experiencing issues with.
Once you’ve identified which browsers/email clients are causing issues, let your developer team know that they’ll need to modify their HTML and make edits to accommodate those browsers/email clients.
Switch CSS in-lining
There are times when the preview in Email on Acid or Litmus still does not match what is sent via the Braze dashboard. One possible cause for this is the CSS in-lining that is performed by Braze may differ from the CSS in-lining performed by other tools. If you suspect that this is the case, contact your Braze account manager to ask for CSS in-lining to be turned off.
Still need help? Open a support ticket or leave feedback below.
Last updated on December 12, 2019