Marketo New Email Editor

Transcript

Everybody welcome.

Yeah, I think so.

All right. Hey everybody.

We are past 830 right now, so I’m going to get started.

Welcome. My name is John Matos. Welcome to the Field Engineering webinar on the Marketo new email designer. I have a few people from Field Engineering with me. If you have any questions as we go, please put your questions into the chat and Susanna, Kat and Wyatt will answer your questions as we go. We have a lot of slides to get through.

All right, here’s our agenda for today. Like I said, if you have any questions, please put them in the chat. So we’re going to cover the new email designer. Of course, that’s why you’re here. We’ll talk about building emails, building templates, building fragments, governance features like content locking. We’ll talk about brand consistency and styling.

We’ll talk about tokens and velocity scripting.

Recently finally re-enabled feature inside the new email designer, thankfully. And we’ll talk a little bit about the Gen AI features and then we will go into a demo and then not on the list, but assuming we have time, we will go into Q&A. Hopefully we’ll have time for Q&A, but hopefully there won’t be any questions left because you will get them all answered in the chat.

All right. So let’s start with the new email designer. So it is a new and re-imagined design first approach to email creation inside Marketo. And as of today, for the holidays, I would say we are pretty much at feature parody with the legacy email editor, which is amazing. Nobody was sure that was going to happen, but we are basically there with all the new features. So it is an active development and being improved with every product release cycle. So you can definitely expect further enhancements. It’s meant to be simple to learn and very easy to use. It’s focused on the drag and drop creation of assets. So HTML experience is not necessary to build your great on brand designs. That’s the focus. We also have AI features in the new editor for things that are…

Is everyone seeing my screen? I think if folks can’t see this screen, please try dropping and rejoining. Maybe it was just a little bit of a glitch. Thanks.

Okay. I saw a bunch of thumbs ups, so that’s good. If you can’t, let me know.

Okay. I’m gonna keep going.

Okay. So when you’re creating assets inside the new designer, you have a bunch of ways to do it. You can generally, and this is gonna be similar across all the different types of assets. You can import the HTML. Maybe you get HTML from an agency or a partner, or you develop it internally. You can create an email from scratch. That’s always an option. It’s a great usable interface for doing that. Or you can work off an approved on brand template, and that’s gonna include a standard template, template converted from an old legacy template from the old Marketo editor, or a template generated from a design image. And I have an example of that that I can show. And I’ll show a couple of different flows through this. There’s a whole bunch of different paths to create all of the different assets inside of the new designer. So I will show a couple of those, but I definitely encourage you to play with it as much as possible to get comfortable with the different options.

As far as roles and permissions in the new email designer, we carry over the permissions from the old email designer, but now we allow for permissions to better facilitate workflow. Things like edit, approve, delete email, edit, approve, delete, generate email template. So that’s gonna allow you to control your roles and access at a much more granular level in your organization to help with governance. And as far as AI permissions, those are turned off for users by default. You see the little window there, that’s what it looks like. And those are then selectively enabled by the Marketo admin on a user by user basis. In order to use those, of course, you need to send the Gen AI Rider to the contract, which your account team can always help you with. So this allows the prevention of misuse of assets, things like that.

Inside of our new email designer, the very basis for all that we are doing here is you need to know that things are made up from two core elements, structures and content. Fragments allow that same pattern. So we include fragments because you also build your emails up for fragments, but really the core items are components and structure. Structures define the layout. So whether it’s one column, two column, three column, whatever it is, you drag those structures onto the canvas to set up the overall physical structure and shape of your email. And then the content are the things that are going to fill those structures. So it’s going to be containers, text, images, buttons, dividers, everything you’re going to add your email, even raw HTML. So I said you don’t need to know HTML, of course, but you do have the ability to add HTML to your emails. So you’re perfectly able to add HTML content items into your structures and use those. So once that layout is in place, you just drop in the pieces or you can build the structure up as you go. You can build, you can put a one-one structure and build it up as your header, and then you can build the footer and then you can stick in content in the middle. So the analogy that I think of is it’s like the components are the skeleton of your email and the components provide sort of the flesh. They flesh it out. I know that’s more of a better, it’s a better Halloween analogy, but I couldn’t really come up with one for the December holidays, but that’s the analogy I look up the flesh and the bones.

So the idea of the structures, this idea of the structures and the content shows up everywhere inside the new designer. And we call it the new email designer, but really you’re designing emails, you’re designing templates, and you’re even designing fragments. So when you’re building an email, when you’re building a template, when you’re building a fragment, you’re going to build them out of components and structures. That’s where they come from. Even when you import HTML, and that’s an example I’m going to show you, you import raw HTML and then you will convert it so that it’s available as structures and content. It’s all going to come down to those.

So let’s talk about templates. When you design your templates, there’s a bunch of, just like everything in the new designer, there’s a bunch of ways to create them. You can create them from scratch. That’s always an option. So you can build things manually and it’s a lot less daunting than it sounds. It’s very quick to do. You can import HTML just by dragging an HTML file and then convert it into a friendly drag and drop format. And like I said, I’ll show you that. Or you can start with an existing template. So you can build a template from a template. So you can start with a sample template that Adobe provides. You can see the screenshot there of some of those. You can start with a save template that you created. So maybe you have a corporate template that doesn’t have a lot in it and you want to create one for like a line of business newsletter or something like that. So you can start building your template from your own other template. Or you can create a template from an approved legacy template that was created in the legacy email editor. So you can start with those and then save them as new email designer templates. So it’s important to know that when you’re looking at creating a template in the create template dialogue, you’ll have three tabs down here. And one of them is Marketo template. I don’t know if you can see that, but it says Marketo template. What you’ll see there is your list of approved old style, old school templates from the old editor. If you start with one of those and then you save it and approve it, now it’s a saved template. It’s available in the new email designer and you can then build emails off of it.

And I’ll show you why I pointed that out in about two slides.

So a little bit more about the email template importer. It’s really important we know a lot of customers have invested time and money into building all those email templates over years and sometimes as much as a decade. So with that new importer, all that effort isn’t going to go to waste.

So they can be brought in and saved as new email designer templates. And there are limitations, though. So it depends on how you built your old legacy email templates. So we have a link to the limitations and different remedies if you find issues with the importer. An example would be if you created a freestyle HTML template, it may not import every component properly and map it over. So it’s important to kind of review your imported template before you start using it. Maybe something didn’t import properly, the footer didn’t import. So you can go in and tweak it a little bit in the interface once you import it over.

And of course, you always have the ability to recreate stuff if it didn’t map over correctly.

We also introduced the image to template converter. So this is a new thing that you’ll you won’t see in the old editor. It allows you to upload a design image from an agency partner or an internal designer and directly convert it into a usable new email designer template.

Use cases for that include things like rapid prototyping, import of assets from design partners, like I said, or converting a brand campaign mock up into a template for like a seasonal mailing. That’s really common. So if your brand team provides designs as a static image, a JPEG or a PNG, instead of waiting for somebody to turn that into HTML or build it in Marchetto, the converter gives you a clean usable template right out of the gate. So it’s a much quicker way to move from that design file, the PNG or JPEG right into a fully governed template inside the new email designer.

I have one that I’ll show that I it takes about 10 minutes to generate. So I’m not we’re not gonna sit there and watch it generate. But I have an example of one that I generated. So I can show you that.

And you’ll see that the AI does a pretty good job of locating structures and content, as you might expect, within within the object once once it’s imported. So it’ll recognize table structures, images, text blocks, spacing, formatting, fonts, all that stuff. We’ve listed some best practices here. There’s a whole bunch of them on the experience league under the image to image to template HTML converter, I would definitely take a look. This is the example that I converted. So it recognizes that these are images that this is text, etc.

Does a really good job.

And just like with building templates, there are also multiple ways to create an email. You can always design it from scratch. Let’s just assume that’s true of everything. You can import the HTML.

And I’m not sure if I mentioned it before, but HTML, when you import it is imported in what we call compatibility mode. So you have to convert it to be friendly with the drag and drop interface. And we have a converter for that. And that I will show you, because a lot of customers that I’ve spoken to have HTML that they want to build either emails or templates out of and it’s the same process you imported and then you convert it. It does a really good job of figuring out structures and all that stuff. You can also of course use a template, either one of your saved templates or your sample templates that Adobe provides. And you’ll see here that this is the create new email dialogue. So one thing you’re not going to see is Marchetto templates because you don’t convert old Marchetto templates to new templates here, you do that in the template creation dialogue. So that’s why you only see two tabs here rather than three. And you also have an access point here into the convert image to template.

I’m not sure why that is, but it’s here in the create email dialogue as well. So you can, with your images here, you can create them, import those things as templates here as well.

For the editor itself, so when you’re looking at the editor, it does look a little bit daunting, but it really makes sense.

Everything comes down to those two things, structures and content. So here you see on the left-hand side, kind of lower left-hand side, what structures, what content is available to add to your structure. So we’ll see that in the demo. And you’ll notice also that as you hover over your email content area, the central content area that you have, it will tell you which structure element you’re hovering over with that blue outline, and it’ll give you context sensitive options like delete, edit HTML, and then on the right-hand bar, you’ll see your styling options. So generally speaking, on the left-hand side, you’ll see several, you’ll see a bunch of tabs. Walk through each, what each one of those things are, but largely on the left-hand side, you’ll find items that you use to build your email. And on the right-hand side, you’ll find items that are used to style your email, whether it’s the brand kit or the CSS, or just like styling options on the right-hand side, or structures and content and fragments and whatnot on the left-hand side. So items on the left, styling on the right.

So this is what all the different tabs have, basically. So we can see structures and content on the top. So we’re navigating down through the top, through the little tabs here on the left-hand side. The options there are the structures and content. The one below that is fragments. We can see all of our approved fragments there, which I’ll talk about in a second.

Assets are also available. So all of your Marketo assets are right there here in this middle guy. So you can see your images and other assets that you can drag into your email with a nice search option. We also expose the different layers in your email. So as you build up your email based on the structures, it can get kind of complex. So you can see the hierarchical nature of your email here. And the other thing you’ll notice here is this little lock icon. I’ll talk a little bit about, in a few slides, about content locking. So you have the ability to lock content at various levels. One of the quick ways to see which items in your email is locked is in this layers view. And then, of course, you have the ability to check out the links in your email. And you can also change the way they’re tracked, whether without the query string. That’s kind of a nice, easy access there. This option down here in the lower left, that looks almost like a Windows logo, is your conditional content area.

Okay, let’s talk about fragments. So fragments are very much like snippets in the legacy email editor. These are pre-created, pre-approved, pre-published bits of content that you can design and publish. And then you create them once and you can use them anywhere in your emails. So you can use them as a header or a footer or like anywhere you have reusable content. And we recommend you can have up to 30 fragments inside of an email asset. The other important thing to know about fragments is that they have an inheritance. They exist in an inheritance structure. So if you change a fragment, and it allows you to refresh that fragment in all of the emails that are using the fragment, you can also optionally break the association with the fragment. So if you have a footer and you like it, but you want to change it, and you’re allowed to based on your privileges, you can break the association with the parent fragment and edit it. This is not the best way to do it. I’ll talk about a better way to do it in a minute. You can do that. So you can create these things, save, publish, edit, republish. As with everything in the new email designer, you have a published version and a draft version.

And if you have a snippet that you want to use from the old editor, unfortunately, the best thing to do right now is to recreate that as a fragment in the new email designer. There isn’t currently a migration path for those things.

So I said earlier, you can break the inheritance with a parent fragment and then make changes. But a better way to do it is make sure that when you’re designing your fragments up front, you design them as customizable fragments. So if a fragment is…

By default, they’re locked, of course, because of inheritance from that parent fragment. But with a customizable fragment, your admin can create the fragment so that certain can be modified. So those are the editable attributes on the fragment. And those can include things like images, text, button target URL. And this is the preferred way to change a fragment in email, because you still would then receive the benefit of having the hierarchical structure, the parent. So if the parent changes, you would still get the changes, but your changes that you’ve overridden wouldn’t be changed. So it’s a much better way to manage your fragments and make sure they’re customized for your individual use.

And that’s another example of the higher degree of governance that we allow in the new email designer, for sure, as is content locking. So we’ve introduced this feature, which is another governance feature, and it’s called content locking and templates. So it lets you decide exactly what in a template can be changed. And you can apply it at the structure level or at the component level. So when in my best advice for this, I found it confusing at first, but my best advice is to go in and try this out for sure. So when you lock a structure, everything inside it is locked by default. So authors can’t add new content, they can’t remove the structure unless you allow them to by turning on allow delete.

But even inside a locked structure, you can still make certain components editable if you want them to be able to edit them. You can also leave the structure itself unlocked, but then kind of go in the opposite direction and lock individual components like text, buttons, images, while still letting authors rearrange or remove content in that section.

So there are a lot of levels that you can, there are a lot of ways you can set up your content locking. And that’s why it’s important that you can look in the levels area and see what is locked, what is editable, etc, inside of your templates and a lot of flexibility. And like I said, the best thing to do to thoroughly understand is try building a template, apply a few different lock settings, and then open an email that’s created from that template to see exactly how those controls kind of shape the authoring experience. It’s one of the new features and definitely one of the strongest governance features we have.

I can show a little example of this.

I did kind of a simple example where we just lock an image, but the first step would be enabling content locking for the entire email. So you allow this feature. So you just go to the body and then click governance and then content locking, and you select the component you want to lock, and then you choose the type of locking. So it’s really very flexible.

And I definitely recommend trying it out. And it’s great for doing things like locking a header, locking portions of content, things like that.

So we talked about styling in the right hand side there. In the new email designer, you can add custom CSS, so you can attach custom CSS, and I’ll show you what that looks like. But it’s really kind of meant as an advanced option rather than the primary approach you should be using for styling your emails. So you access it from the body panel. You can see on the right hand side there, the top button is all about the style, and there’s a button for add custom CSS. When you click that, the dialogue comes up. You can paste it in. It’s great for specific tweaks, refining spacing, adjusting a component’s behavior, matching a legacy design, things like that. But it doesn’t give you the same global controller governance as brand themes, which I’m going to talk about in a minute. So themes are more of the preferred option because they’re going to define many more things, which I’ll talk about in a second.

And you don’t have to apply them. They are applied everywhere rather than having to have them applied at each individual asset. So the guidance really is use brand themes for anything that’s brand wide or repeatable, and then you can reserve your CSS usage for small targeted adjustments. So where themes can’t quite get it exactly the way you want, and you can apply CSS here and there. And I’ll show you some examples of that.

So brand themes. So this is the new feature that gives you your centralized enforceable way to apply your brand across everything built in the new email designer, instead of relying on each author styling things that they create manually. So they’re going to define your fonts, colors, spacing, and default component styles. So everything is going to show up consistently no matter who is building the email.

They also support token based styling. So if you update a color or change a type style, everything using that brand style is going to get updated automatically. So if your brand changes, if your color slightly change, if your font slightly changes, all of those changes are going to propagate down to the assets using that theme. So it’s a lot better than CSS in that way because you would be stuck going and changing your CSS everywhere. And if you just simply used CSS to style everything.

And the things we’re allowed to control with brand themes currently are things like color palette, including like brand accent colors. So you’re not choosing colors manually. That’s always risky. You also define the typography options. So fonts, sizes, text styles, and you can also define text styles globally or by individually for like headings, paragraphs for like each individual H1, H2 inside of the HTML. So it’s really very flexible. It allows you to manage spacing, borders, layout behavior. So it’s going to keep all of your templates consistent with your design system. Even things like button attributes, size, radius, color, they’re standardized there as well. So you don’t get, you’re not going to see a dozen different button styles across your organization. And you can set up different looks for grid setting, spacing, even separators. You can decide if separators are going to be dots, dashes, things like that. So you can really control it at a nice deep level and not have to worry about the CSS if you’re not comfortable with it.

Important to know though, how you apply your brand theme. So when you’re building items in the new designer, you apply the brand theme right at the moment you create the template or the fragment. So you’ll see a use themes button right there and you’ll see it. And that tells the designer that this new asset is going to be used, brand defined color is going to be used in the brand kit, right? So once you select the theme, once you select it and create it, on the sidebar, you’ll see the little paintbrush icon. That’s going to give you access to the brand theme and you can apply it. You can browse the available themes. You can switch between different variants very easily. You can apply it, you can make changes to it. So now every structure and component you drag into the canvas is just automatically going to follow the brand rules without any styling needed.

So that’s the key, that’s the key really for scaling. Authors just build the emails and the theme keeps everything aligned to the brand without having to think about it.

You can also create theme fragments and this is important to know. When you’re working with brand themes, the fragments you use also need to be created as themed fragments. They need to be created in theme mode if you want to inherit theme levels and level styling and use those in your theme templates. So if you have a fragment that is not a theme fragment, it can’t be used in a template that is themed. So if you have, and once you create a fragment, it can’t be converted to a theme fragment. So if you had one created already, you’d have to recreate it as a theme fragment and associate the theme with it in order to use it. But the construction process is exactly the same. Just the difference is how you started. You just choose a use themes button when you’re creating it.

So if you’re using brand themes, it’s important to rebuild all those high value things as theme fragments so you have them available in that way. So it’s available across your entire ecosystem.

This next one is huge and I’m so glad we finally got it going. It’s a recent addition to the new email designer. We finally have conditional content available inside of emails. So that’s going to let you, just like it used to with the legacy email designer, it’s going to let you personalize sections, content, images based on audience attributes by approved segments without maintaining multiple email versions. So you build one email, then you define rules and swap in different text images. The example you see here, I’m going to show you. And it’s all done visually in the designer. So you have your segment, your approved segment, your records in Marketo have the attributes set and they are put into the segments and people will get the different version of the email based on their attributes. So very much like it used to be in the legacy email editor.

Honestly, tokens are largely the same as they used to be in the legacy email editor. The interface is a little bit more modern, updated. You have a nice ability to search through the available tokens. All the tokens are available that were available before person, you know, tokens that you’d find at the program level, system tokens, all that stuff. It’s all available, but the personalization tokens are there and you can add a fallback value, which will put in a value if a data value doesn’t exist for someone. So like I’ll put one in for like first name and you put in a backup value if the data doesn’t exist. But very much the same way tokens have always existed, still available.

And now finally, yay, velocity script tokens. Render in the emails that were created in the new email designer. So honestly, there’s nothing new to say about velocity script itself.

If you have a velocity token defined inside your program and you have an email that was designed in the new email designer, just put it in the email wherever you want it to render and it should render in the same way. All the same limitations and cautions exist with script tokens that always existed, but now they are finally available. So what is this good for? Of course, you can do advanced things with person token. Really any tokens are available. So if you want to put in information about opportunities, person attributes, things like that and also custom objects, you can render custom object data inside your emails. Of course, fully separate topic, but they’re all available and of course, features you’ll never see in the legacy email editor have to do with the AI assistant. The three main areas that we talk about with the AI assistant are creating an AI generated subject line for your email, creating content for a specific section of your email, and that’s what I’ll show. And then also the ability to create an entire email from a selected approved template. So if you have a template, what you do is you go into the template and without selecting any component in the template, you just click the AI assistant button, which is another button you’ll see on the right hand side is those little sparkles. And you have the ability to generate the entire email, including images and text from that template.

So here’s what it looks like to generate the subject lines. Very much like other AI generation tools you’ve obviously seen.

You can enter brand assets if you’re going to be generating images like guide assets. So for example, if you’re going to be generating images about yoga, for example, you can upload sample images for it to generate from. And then you basically highlight, you put in your prompt, tell it where you want it to go and click generate. It’ll give you four options. You can tell it whether they’re good or bad, flag them, what have you, and then put them in your email.

And here’s kind of an example of that. So you can choose a content area and have the AI generate for you. You can add prompts, tell it you want to generate FOMO urgency, things like that, all the typical things you would expect.

And here’s what it looks like to generate the entire email from a template. So like I said, without selecting any component in the template, you click the AI assistant button, you enter all of your prompt information, you choose the brand assets, image settings. And then if you want to generate images using Firefly, you can select the image settings and select the option for generate images using AI. And it will preview everything for you and create your whole email. Just a little screenshot of one I created.

Very fast way to create your emails.

And speaking of images, we also now have the ability to directly edit images with Adobe Express. So whether you have the enterprise license or not. So if you don’t have an enterprise license, you can resize an image, remove the background, I’ll show you that, crop an image, convert an image between JPEG and PNG. But if you do have an enterprise license, you can do a lot more things, as you might expect, like change color, brightness, sharpness, contrast, things like that, to all the AI magic that you would expect.

All right.

Enough talk.

Let me turn off my camera real quick, because I’m gonna be looking around while I do this. And I will share Marketo and we’ll do a little demo.

All right. I’m gonna assume everybody can see my Marketo screen. If they can give me a thumbs up.

All right, cool.

I love it. So many thumbs ups. Okay. And again, any questions you have, just please put your questions into the chat and my coworkers will definitely get to those. Okay, so the first thing I’m gonna do is I’m going to create a fragment. So my plan here is I’m gonna create a fragment, I’ll create a template, then I’ll create an email. And maybe I’ll show you the conditional content first, given the time. I’m gonna show you the conditional content first. So let me show you that. So we have my Hogwarts email with conditional content, right? So we’re gonna click edit email content here. So I have an approved segment here that has three different attributes. And this is my email. So you can see here, the orange color indicates that we’re gonna see some differences with the segmentation, with the dynamic content. So for the image, for the content and for the footer, you’ll see different versions for the, is this person a magic person segmentation. So for the image, if a person is magical, oh, that’s the, I’m in the text here, I’m sorry, image. So if a person is magical, they’ll see the picture of Hogwarts. If they’re non-magical, they’ll see the picture of the University of Arizona. If they come from a magical family, but they have no magic ability, that’s what a squib is, they will see the University of Freeburg. So I have that set for all the different levels. And you’ll see that in order to render that, I just click on the particular image, and then you can see the acceptance letter for the people from Hogwarts. Here, I’ll make that one Hogwarts too. And then this one is the Hogwarts acceptance letter. Here’s the non-magical version for people who’ve been accepted to University of Arizona. And we’ll show those separately. And then we’ll show the version for the squib. And you can see it’s really easy to toggle between these things. And the way you do it is you can add segmentations from multiple different segments. So if you want to have one section that switches based on whether someone is a dealer or distributor, for example, that’s another thing we have in this instance, you can do that for a particular content area. Or if you want to switch based on magic ability, you can do that too.

You do that all in the same email. So it’s really, really powerful.

All right. Closing that.

All right. So let’s create a fragment. So in this case, I’m going to create a fragment just from HTML. So we’ll call this webinar footer.

Webinar footer one in case I’ve done it before.

So as you see here, I’m creating a fragment. I initially and immediately have the option to either use themes or do manual styling. I want to show the CSS thing, so I am not going to use brand themes right now. So I’m just going to choose manual styling, confirm that. And then I’m left with this somewhat daunting empty screen, but it’s fine. I’m going to build this from scratch. I’m going to drag in a two, two column and a one, one column. There we go. You can see the structure is really easy to build up. And then if you put in something you don’t want, you just hover over and you get your ability to delete it, your content, context sensitive options. I like to always have containers inside of my structures. I don’t know why.

There we go. So and now I’m going to start dragging in my contents. So on the bottom one, I’ll put in a little social icon and then I’m going to put in HTML. So it’s going to look a little boring until we style it, but that’s fine. So you can see these are HTML. When I click it, you have the ability to change the HTML.

And then I’ll put in my actually paste in my HTML here.

In my right side, HTML here.

All right, there we go. So that is, and here’s where we can select editable fields. So if you have an item that is, that you want to change like the target on or like you have a button or something like that, like maybe you want to change the, allow people to change the target of the email, you would just turn on editable and like allow them to change the label in the URL. So we’ll save and close that.

Oh, we would also make the, I mean, if you want to change the social media stuff, maybe by department or something, you can do that there as well by making it editable, making it editable. So got to publish it.

All right, so now I have a published footer, very exciting. So now I’m going to create a template. So I can create a template from an image. That’s option is here as well. And now I’ll call this the newsletter template one, whatever. Just remind me, I call that newsletter template one.

And I will make this also from HTML. So again, a bunch of options.

I’m in dark mode, so you can do it in dark mode or light mode, but I’m going to just import an HTML in this case, but you’ll see, I could start from a save template. I can start from an approved Marketo template, or I can start with one of my sample templates, or I have an access point into my themes here too. So I can like play with themes and then create the template. Since you associate templates with themes, I don’t want to scratch. I already showed you that. So here we’re just going to drag and drop our HTML into, in this case, I’m going to drag my raw HTML in and here’s my newsletter. And you can see it doesn’t look very drag and droppy. This is what’s called compatibility mode. We’re being reminded this HTML is not adapted to the editor. It’ll be edited in compatibility mode, not ideal. So we don’t want that. So we’ll go to the HTML converter over here on the right. Make sure you don’t have a table as your topmost container and then give you the ability to convert and whatever it says, make sure you check it out after you’re done to make sure it’s right.

So click convert.

There we go. So now we converted that HTML and look, everything has been brought in as an HTML and you can see like this guy, you can actually edit the HTML in here, which is really cool.

I’ll save it, make sure it looks good.

Make some changes. And now I’m going to add my custom CSS. So I can make you watch me type this. I have it over here. So put in your CSS.

It’s hard to look at in dark mode, but whatever there is. So now it’s a little bit more, whatever, the more magical looking. And now we can make changes. So in our template HTML, we have this footer. I don’t know. I kind of hate this footer. So we’ll take it out. We’ll just delete it and we’ll add another one, one column in on the bottom container. And now we’ll start looking through these left-hand items. So our fragments, these are our fragments. We have our assets, images, stuff like that. We can pull in here our layers. This is the layers that it figured out from the HTML, all the links. If we have any links, we’ll see them there, but we’ll go back to fragments and we’ll pull in this footer.

There we go. Very exciting. So that’s our footer now. And yeah. Okay, cool. There we go. So let’s now edit our content.

I didn’t do anything. Maybe I’ll go back to the template in a second. I’ll put in some content locking, but what I can do here is change my newsletter content. This is just placeholder content.

Put in more HTML. And now I have a newsletter. Oh, this is my template. Okay. So let me save this, make sure it looks good.

Okay. It looks good. Looks good.

Now.

Okay. So if we want to…

Okay. I think this is good for now. So let’s build an email based on this template. Looks good. Looks good. So close that.

I’m going to publish it.

And of course, once you publish it, if you come in and make changes to it, it makes you create a draft version, very similar to the way it’s always been. Right? So you can see the draft version. You can choose to turn on governance, as I said. So we can turn on content locking and then allow the governance of different things, different levels.

So there we go.

So if we want to lock this component, for example, it’s editable right now. I can change it so it’s locked. And then you see a little lock icon appears. And that’s it. Okay. So now let’s create an email from this. We’ll create an email from that template.

And then we’ll edit our email content and we’ll create our email from our saved template.

So we can make changes in here. Like I said, very easy to put in our personalization tokens.

Right? Really, really easy to use. We can insert with our backup.

And there we go. So we created our fragment template and email all pretty easily.

Okay. Yeah. And then, of course, conditional content I showed. Yeah, I think I hit it all. So we have… I think we have scheduled until 930. So let’s go through some Q&A, specific questions. So feel free to unmute yourself and ask specific questions. Let’s do that.

I don’t know if people can unmute. Can people unmute? All right. So if there are no questions right now, what I will also do is I will show the image to template converter. So the image I converted… Let me share that real quick.

It’s the newsletter for vegetable delivery. So let me show that real quick.

All right. So there’s the image. This is just a PNG file that I pulled into the designer to be converted to a template.

So let’s share. I’ll show you what the result of that is in Marketo.

I think that’s the right screen.

Start to look at our emails here. Oh, sorry. The templates.

Image to template. This is what it created. So thinking about the image itself, we had… It’s the garden email template. The image on top was free delivery with some text inside of it. So it’s not gonna find the button inside. What it did was it took the button out and put it below. So if we click on edit the email image, it realized that this is an image. It realized that there was a button embedded in the image and it put it below the image, which is fantastic. Even the text below the image it put in and that it looked at the different sizes of the different images. It created a three by one structure, three column structure to include the three items like the three boxes of vegetables, realized that there’s text below. So it included all the text, all the buttons, looks at the size of the images and sets the images up.

So… And it’s convenient because it actually looks at the actual image and will tell you the actual size. So when you’re working with your designers, you can share this with them and they know what size images to put into this template. So it does a pretty good job and it took about 10 minutes to render this from…

Which is pretty amazing.

I can also show a little bit about…

Show some of our Gen AI stuff real quick.

I have a question too.

If you have time. Sure. Hit me. Yeah. So for the contents under the component section where you have the HTML and the text and image and stuff, is there like a rich text content thing that we could pull in? There is not, but you would probably just do that with HTML. Right. Okay. Because for people who aren’t comfortable with HTML, rich text is really nice. But okay. Thank you. Cool.

Hey, John, I had a question for you too. Sure. What would you say your recommended approach would be for a dynamic footer? Let’s say your company has a lot of corporate addresses and it usually has to reflect the nearest corporate location.

So probably the best way to do that that I can think of would be create the fragment, create the footer fragment for your whole organization. And then you can make the addresses editable and then have each different location or line of business or location.

So you can either create a footer based on that footer or you can just customize it in the context of the email. I guess creating your own footer probably would be better for each different line of business with each different location. If you have locations in New York, Chicago, LA, things like that, I would probably make them separate.

I guess we’ve been using a dynamic snippet right now, which would dynamically personalize so I wasn’t sure if having the conditional content within the fragment was on the roadmap.

I actually have not tried conditional content inside the fragment. I do not know if it works. I don’t know if that’s implemented, but I can look real quick. Hey, John, I just did a quick test. It does not work at the moment, but expecting that to be developed at some later date in the future. Not sure exactly when that will be yet, though.

That’s good to know. I feel like that changes the strategy. Do we go wild, wild west, allow people to edit it? Do we create static versions of all of our addresses? Do we try to do something in velocity? I feel like that’s kind of been our barrier to adopting this. So this is good to know.

Cool.

One more question. We have another question. John? I’m just curious. Oh, sorry. Go ahead, John. Go ahead.

I’m sorry. What’s the question, John? I was just curious if the new editor works with the API library the same way.

Ah, goodness. That’s a great question. I did not cover that. Currently, there isn’t an API the way there is for the existing email assets, like the asset API. But I talked to the product owner, and that is absolutely on the roadmap from what I am told. Of course, we can’t guarantee it. But they indicated that they’re targeting that for the first half of next year. No guarantees, but we’re hoping that happens. OK. We’re looking forward to it. Thank you.

Hey, John. Can you quickly demo the testing process? My understanding, it’s a little bit different with the new editor. Oh, gosh, yes, of course. Thank you. I showed the… So you can see different options of content. I asked it to add a little FOMO, whatever. So you can see some options it’ll give you there. It’ll do the entire content block. So if you want something, you would break out the content blocks into different areas and target maybe the acceptance portion or something and leave everything else in place. But that’s how it looks. You get four different variations. You can make it regenerate.

So testing the email…

And there are definitely more things to this that I didn’t put into the demo here. But here’s what it looked like when you simulate the email. So the thing that is most different, in my opinion, is that you have to actually add people to the list that you want to demo. I manually added these people. And the way you have to add them is with their entire email address. So this instance only has a few people in it. I’m not sure who’s in there, but you would have to add them by their email, their full email address. And then once they’re there, then you can preview for the individual people. So this is what Harry Potter would receive. This is what this person would receive. Obviously, if you have conditional content, it’s going to show the right version. That’s what I would receive.

And of course, you can send a proof. Same way. You can select the person.

And when you’re doing the simulate as… So you’re saying you have to add those people. Would those be just… Let’s say in the lead database, you would add them like, oh, I want to see how it’s going to render for this prospect.

Yeah, exactly. Yeah. In the old email editor, I know you could look at an entire list of people. So you can then scroll through the list. And that is very convenient for sure. But this is the way we have it right now. Not clear if they’re planning to enhance this at all, but I sort of agree the old version in some ways was a little bit better. Gotcha. And do you know if you have to add people for each email or once you add someone, they’re there for all the emails in your instance? Once you add them, they’re there. But the list that I have is not the same list that you would have. So if you’re logged into this instance, you would also have to have a test list as well. Gotcha.

Like every email, I’d be able to test with these people, but you wouldn’t be able to until you added them. And then the other thing I didn’t talk about is the spam report. We have integration now with SpamAssassin. So it looks for…

I didn’t actually make a slide about this because I didn’t think we’d get to it. It can do a little spam evaluation using integrated, no extra cost, using various spam fasten criteria to determine if there are…

It’ll give you a spam score and you can like go remediate based on if it finds your email to be spammy. I don’t know what the criteria are. I actually have a slide about it, but I didn’t put it in here. In retrospect, I probably should have, but there it is. We’ll add it in before we send out the deck.

Any other questions? I can’t see hands that are raised.

John.

Sorry if I missed this earlier. Is there a timeline to sunset the Legacy Editor? Oh, gosh, that’s a great question. I do not think there is an official timeline at all, but my sense, I don’t know. I could probably… I like to defer to Wyatt on things like this, but my sense is that until there is complete undeniable feature parity for things like the API and things like that, it wouldn’t make sense to sunset the Legacy Editor.

Right with you. As you alluded to earlier, lots of investments in what’s already there and even still plenty of investment coming. So timing and resourcing is everything to make the migration. So thank you for the answer. Appreciate it.

It’ll definitely happen eventually, but we know that there are like investments in API integration with email assets and the API is different with the new email designer than I don’t know how you sunset the old email editor.

Just need to rewrite your code.

Okay, thank you. All right, cool. All right, well, that’s all we have. I know a lot of you guys are here because you have solution accelerators with either me or one of the other field engineers. So I think this is a great basis to have that first or second conversation. So we’ll send out the deck, we’ll send out the recording and you can base your second conversation or first conversation even on what you now know. Definitely you can go and play with the tool now and let us know how you want to proceed with those solution accelerators.

Anything else before we hop off? All right. Well, thank you everybody for your time today. I really appreciate it. You can email us with questions. Like I said, you probably have a solution accelerator for these things. Email your field engineer, email your TAM, let us know what you think. Fill out the survey, please fill out the survey and yeah, we’ll talk soon. All right. Thanks everybody.