©2024 Oracle Corporation. All rights reserved
85 of 212
HTML guidelines
The code content in the Design Editor is intended for snippets of custom HTML code.
If you need greater control over the email, you should use the Source Editor to create
an HTML email. Learn more about HTML emails.
Here are some guidelines for your HTML code:
l
Write HTML code that is standards compliant. For example, be sure to nest and close
elements correctly and use lowercase element names, attributes, and values.
l
Avoid using the following HTML elements to a code content block: <html>, <head>, <body>,
<script>, <iframe>, <form>. The Design Editor does not support the use of some of these
elements. Others are not supported by many email clients, are often blocked for security
reasons, and if used could cause deliverability issues.
l
Be aware of reserved characters like <, >, and &. These characters make up the HTML
language. If you want them to appear in the content of your email, you must use the entity
name or number instead. For example <, >, and &.
l
Support for CSS properties varies across email clients. Use a CSS compatibility chart to
validate what is supported and test your email against your target email clients.
l
To prevent CSS conflicts with Oracle Eloqua:
l
Avoid the following class names: .body, .ExternalClass, .button.
l
Always name classes to be applied to <table> elements. If you are using tables, note the potential
responsive issues below.
l
If your HTMLcode contains tables or long text strings, a notification appears in the
Design Editor. Tables and long text strings can potentially cause responsive issues,
preventing content from adapting to different screen sizes. Oracle Eloqua doesn't prevent
you from sending an email with these potential issues, but you should test your content on
different screen sizes and against your target email clients.