🌐 Also available in: 🇫🇷 Français
Original source: Adobe Marketo Engage User Groups
This article is an editorial summary and interpretation of that content. The ideas belong to the original authors; the selection and writing are by Marketo Ops Radar.
This video from Adobe Marketo Engage User Groups covered a lot of ground. Marketo Ops Radar selected 6 key moments and summarises them here. Everything below links directly to the timestamp in the original video.
Are you struggling with the limited column width controls in Marketo's Email Editor 3.0? Discover a direct method to achieve pixel-perfect layouts for your email designs.
Achieve Precise Column Widths in Email Editor 3.0 with Browser Inspector
Email Editor 3.0's column width sliders only offer percentage-based adjustments, limiting precise design control. A practitioner demonstrated a workaround using the browser's developer tools (F12 inspector) to directly edit the CSS width property of column elements. This method allows users to input exact pixel values or more precise percentages, enabling a level of control over email layout that isn't natively available through the Marketo interface. It's a crucial tip for maintaining pixel-perfect designs.
"You can edit those directly in the inspector and then you'll be able to get the exact widths that you want."
Prioritize Fragments and Themes; Avoid Template Migration Tool in Email Editor 3.0
For Email Editor 3.0, a practitioner strongly advocates for building out email modules as fragments and leveraging themes for efficiency and reusability. The template migration tool from Email Editor 2.0 is not recommended due to issues with variables not carrying over and inflexible CSS, often necessitating a complete rebuild. This approach ensures cleaner code, better control over design, and improved long-term maintainability, even if it requires more upfront development. The lack of variables in the new editor means more specialized fragments are often needed to achieve the same flexibility.
"We built everything from scratch because there are some gotchas with using the template migration feature."
Navigating Email Editor 3.0 Governance: Fragments, Inheritance, and CSS Challenges
Email Editor 3.0 shifts governance from templates to fragments, emphasizing inheritance for consistency. Practitioners must understand the implications of 'breaking inheritance,' especially for evergreen emails, as updates won't propagate. Themes can standardize brand guidelines at the email level, supporting multiple brand variations. However, a significant limitation is that custom CSS changes made to a template do not automatically flow down to existing email assets built from it. This necessitates careful planning for CSS management, with fragments being proposed as a more effective container for module-specific styling.
"When you break inheritance, there is no more connection from a parent fragment to a child email."
Strategic Adoption of Email Editor 3.0: Templates, Inheritance & Governance
One marketing operations team is adopting Email Editor 3.0 by creating more specialized templates to simplify email creation for marketers, aiming to provide a closer-to-final starting point. A key focus is extensive enablement on fragment inheritance and its consequences, especially discouraging breaking inheritance for evergreen nurture emails. This strategy also involves leveraging multiple themes for brand consistency and implementing robust governance through fragment and content locking. The presenter emphasized the ongoing need for detailed training and access to external resources to navigate the editor's complexities.
"I'm really trying to ease that burden of my campaign operations team."
Phased Rollout Strategy for Email Editor 3.0: Start Simple, Train Extensively
A practitioner outlined a phased rollout strategy for Email Editor 3.0, prioritizing simple, frequently sent emails like webinar invites as initial use cases. This approach aims to ease the learning curve for marketing teams by starting with less complex tasks. Key to this strategy is creating a comprehensive learning path, including videos and one-on-one training, particularly for regional teams. This acknowledges the significant shift from Email Editor 2.0 and prepares users for future integrations with AI and Gen Studio.
"The thing that I'm keeping in mind is not only are we migrating emails but we're also enabling the team on a brand new tool."
Implementing Marketo's New Email Designer: A Phased Roadmap
Implementing Marketo's new email designer requires a structured approach, starting with an audit of existing email assets to identify what to migrate or refresh. A phased rollout strategy includes collaborating with design teams to build new templates and branding guides, then piloting with a small group for feedback before a full team launch. This methodical roadmap, encompassing auditing, design, piloting, and comprehensive training with diverse documentation, helps manage the learning curve and upfront effort required for a successful transition, emphasizing the benefits of drag-and-drop functionality and template locking.
"I kind of created like this implementation road map, I guess."
Also mentioned in this video
- Stephanie details the key differences and advantages of Email Editor 3.0 over… (13:19)
- Stephanie and Jay discuss the current lack of an autosave feature in Email… (18:47)
- The process for sending sample emails in the new email designer, noting that… (27:06)
- The advanced email editor, mentioning the lack of official guides for its… (28:29)
- A rumor about Adobe deprecating Email Editor 2.0, confirming that while a date… (55:32)
Summarised from Adobe Marketo Engage User Groups · 1:02:43. All credit belongs to the original creators. Marketo Ops Radar summarises publicly available video content.
