Adding field merges to Classic Design Editor emails

Important: Starting May 2019, you will not be able to create new assets using the Classic Email and Classic Landing Page Design editors. Existing assets will be editable. As of August 2019, all legacy assets will be view-only and not editable. We recommend customers start preparing in advance for this transition by reconfiguring their existing content. Learn more in our product notice.

Add field merges to personalize your emails using information from contact records, events, or custom objects. For example, use a field merge to add a contact's name to an email or to customize email links and images.

Field merges can be an important part of your organizations personalization strategy. If you don't have a strategy yet, have a look at the resources on the Personalization: DIY Marketing Success page.

You can add field merges using any of the email editors.

An animation showing how to insert a field merge

Before you begin:

  • Field merges are maintained in the component library. You can create field merges while you're working on an email, but it is best to plan your field merges, and then create and organize them using the component library.
  • All field merges are HTML encoded by default. This may impact how data from contact records is displayed within your assets. For more information, see Query string validation or contact My Oracle Support for instructions on how to work with encoding on field merge values.

To add a field merge to an email Classic Design Editor or Source Editor:

  1. Navigate to Assets An image of the Assets icon, which is represented by a black pencil., then click Emails.

  2. Open an existing email.
  3. Place your cursor in the location you want to add your field merge.
  4. Click An image of the Field Merge icon. and double-click the field merge.

    Oracle Eloqua highlights field merges so that you can easily identify them.

    An image showing a field merge in the email editor

  5. Test your field merges by previewing the email.

After you finish:

  • Oracle Eloqua converts any spaces or hyphens in the name of the field merge to underscores (_). Only alphanumeric characters (A-Z, 0-9) appear in the field merge. For example, the field merge First Name would appear as First_Name in the email editor.
  • If the field merge added to your email doesn't have exactly the same name as what you saw in the chooser window, this is probably because the field merge was renamed at some point. The original name still appears in the chooser window.
  • If you are familiar with HTML code or you are using the Source Editor, you may notice that Oracle Eloqua inserts the field merge using the following syntax <span class="eloquaemail">Field_merge_name</span>. Oracle Eloqua requires the class attribute to identify the field merge. Do not remove it.
  • In the following cases, Oracle Eloqua converts the <span> syntax mentioned above to an HTML-compliant syntax using tilde (~) characters:
    • If you add the field merge to part of a URL's query parameters:  <a href="http://www.example.com/cta?x=<span class=eloquaemail>Field_merge_name</span>">Call to action</a>
    • If you add the field merge to an image path: <img src="http://www.example.com/img?x=<span class=eloquaemail>Field_merge_name</span>"> or <img src="<span class=eloquaemail>Email_Address1</span>">

    The field merge is not converted to an HTML-compliant syntax if the field merge is a link's URL path (for example, <a href="<span class=eloquaemail>Field_merge_name</span>">Call to action</a> ).


Related

Field merges

Previewing emails

HTML email code requirements

Topliners: Personalization: DIY Marketing Success