We launched this month’s webinar with the Pointer Sisters singing “I’m so excited”. That’s the general mood amongst Eloqua customers as they begin to work with the new Eloqua email Design Editor. This webinar replay walks you through the new editor and provides additional ideas to help you migrate from the Classic Editor to the new Design Editor.
First things first
The existing email Design Editor will now be referred to as the “Classic Design Editor”. The new email Design Editor will be simply called the “Design Editor”. Our focus during this webinar was the Design Editor.
User Group Member Poll Results
We asked User Group members three questions during the webinar. We asked about their usage of the new editor, who builds emails in their team and their confidence in using the new editor. Hover your mouse over the image to pause the scrolling.
The existing email Design Editor will now be referred to as the “Classic Design Editor”. The new email Design Editor will be simply called the “Design Editor”. You essentially have two editors
The Classic Design Editor contains two functions:
- Drag and drop functionality – this will be retired in the coming months.
- HTML source editor – this will continue to function as you need to upload HTML files e.g. via Dreamweaver etc.
The new Design Editor will be the primary editor used by most Eloqua users.
It’s time to make a plan to upgrade.
There are several ways you co do this:
- Extract a Form Submission Overview report from Insight.
- Focus on your “always on” campaigns that send an email once a person submits the form.
- Prioritise those email built in the Classic Design Editor and assign them to a team member to be rebuilt.
With so many email clients and devices e.g. GMAIL – Android, Apple Mail – iPhone, Outlook etc, considerations around Preview Text need to be thought through.
Today, preview text is the same for all recipients with the new email Design Editor, however, Oracle has advised that the ability to insert a Field Merge into your Preview Text is on the Eloqua Roadmap.
The key point with preview text is understanding that you have little to no control over who will actually see it if they see it at all. The end-user controls if and how much preview text is visible on their various devices. Your subject line should continue to contain your primary message or call to action.
Management of your existing email assets.
Oracle will be announcing information about the state of the Classic Email Editor with the 18C (August) release. The key point is that Oracle will never delete customer’s emails.
You will always have access to your assets. Additionally, any assets in current workflows (form processing, campaigns, etc.) will also continue to work. Eventually, customers will not be able to create any new emails in the classic editor but will still be able to send them. More details coming soon.
UPDATE as of 16 April 2019
Important Update from Oracle: 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*.
*NOTE: You will have to login to Topliners to access the Product Notice.
Release 18B – May 2018
In late May Oracle Marketing Cloud released Eloqua 18C with a range of new features including continued functional enhancements for the new Email Design Editor.
New Dashboard & Insight Report
The Contact Database Health dashboard provides a current state snapshot of the contacts in your database. It helps you determine who you can reach in your contact database and who is actively engaged with your emails.
The new Dynamic Content by Campaign Insight report shows the dynamic content rule applied to a unique email open for a campaign in the date range specified. Dynamic Content data is only applied to email open activity. Because this report is based on unique opens, it ignores forwards.
Changing the visibility of landing pages
You can prevent an Oracle Eloqua landing page from being accessed by changing the visibility of the landing page. For example, after an event completes, change the visibility and prevent visitors from signing up. Or change the visibility if you are drafting a landing page and are not ready to make the information publicly available.
Adding images in the Design Editor
About one minute into this video you will see how to add an image as a background item allowing you to place a button or text in front of or on top of the image.
We’re expecting news from the Oracle Marketing Cloud team around August that will share news about a new Landing Page editor, currently under development that provides a similar level of functionality to the email Design Editor. The initial release will be BETA.
What do our clients say?
“On behalf of Fab and myself, I’d like to reiterate our sincere thanks for the workshop. Your expertise matched with a down to earth, practical approach makes for our ideal partner. The day invested to focus on our marketing automation was worthwhile, invigorating actually. We learnt a lot and very much look forward to the next steps (and a Markie!).”
– Lara Worthington, Marketing Support Manager
Dahlsens Building Centres