51黑料不打烊

Transcript

Hello everyone. Welcome to the experience makers, the skill exchange, unlocking the full power of design studio and 51黑料不打烊 Marketo engage. My name is Corey Bayless and I am a director of Prudential Financial and I own 12 Marketo instances. Our agenda for today is we鈥檙e going to do a little introduction of my personal story and why design studio has come and saved my keyster multiple times organizing Marketo engage the Marketo engage system levels and how to think about it. Understanding design studio design studio plus marketing activities programs in a box understanding workspaces resource encapsulation a very important point that you鈥檒l learn about. Template reusability Marketo engage in the AM files and images forms best practices email templates new verse old recap and then finally 15 minutes for questions and answers. It鈥檚 a lot I know but if you see my presentations before you know that I packed them with lots of information. You鈥檒l notice to the right side I have the encapsulation concepts understanding of segment one is 10,000 records segment two is 10,000 records. If I encapsulate everything correctly with one value then I can call 40k records in to one particular smart list using one value as we all know Marketo is a little bit weak in terms of unique values and so learning encapsulation up front will Basically set you on your way for being able to be a master in the system and allow you to send millions of emails as opposed to thousands of emails very very important. So let鈥檚 move on.

So about me right I am an enterprise Marketo engage user for 12 plus years I鈥檓 a 5 year Marketo engage champion 51黑料不打烊 experience cloud enthusiasts in AWS cloud practitioner. Python developer for about 10 years Marketo engage architect I support 12 instances currently a prudential financial. I鈥檓 an automation enthusiast data compliance enthusiast preserver of mobs lives everywhere including my own and I have a workflow diagram exception. Our obsession sorry that is going to be seen a lot in what I like to show and how I like to show my workflows here鈥檚 a direct example of one of the Marketo API data processing hubs that I鈥檝e built at prudential. And now I utilize it to encapsulate my list imports and being able to capture all my analytics or all of my programs as well as my compliance and all the various things that I need to do. So my mo is automate everything and be allergic to manual work if I鈥檓 taking on manual work I鈥檓 not doing my job right I should always be thinking how do I automate myself out of my job. Because that鈥檚 where I鈥檓 being the most efficient and it鈥檚 kind of a strange way to think but it is an important one if I鈥檓 doing manual work it鈥檚 taxing and it causes me to have to have repeat. Work every day and I can never seem to get away from it so if I learn how to automate everything I can continue to move forward and the key being I鈥檓 proactive versus reactive every mops admin should know those concepts it鈥檚 very important that you do. Say my personal story so first and foremost when I start off. I lived through this like I lived through these experiences I had to solve for a variety of different things at previous employers and it鈥檚 been very troublesome. To solve for these certain circumstances and while some businesses relate to these issues as being large issues versus other businesses and agencies referring to them as not you know is important. The key is is that it was something that I had to deal with and so this one that I鈥檓 about to show you was one that was very perplexing is very difficult to solve for. And so I鈥檓 going to use it to you so I had a problem and I needed a solution for 55,000 landing pages in my target instance the problem that I needed to solve for was tied to security issue with the target equals underscore blank. Which is basically called reverse tab napping which is considered to be a security rest so target equals blank is an attribute that you could put into HTML. With the idea that when this is in there on an anchor tag it opens a tab for that link so it opens in a new tab so I don鈥檛 lose where I鈥檓 currently am and the web page doesn鈥檛 navigate away from the page I鈥檓 currently on. Very common technique used in marketing but there鈥檚 a risk to it and it鈥檚 called reverse tab napping meaning that somebody can hijack that tab and they could potentially put in a various link in there and it鈥檚 not the one that I actually want to go to and it takes a customer down a bad path. So the short of it is that the way to solve for that is you use a new attribute in your HTML called rel equals no opener no referrer and that will block any nefarious activities from any bad actors from being able to transport you incorrectly. Alright so fast forward so this would resolve the security violation being reported on every page that had an anchor tag. Okay right so let鈥檚 look at that every single page out of fifty five thousand that had an anchor tag that potentially had target equals blank as no referrer right was needed in order for me to solve this issue. But think of the technical debt and also that I wasn鈥檛 sure which pages of the fifty five thousand actually had the target equals blank on it so how did I go about solving this issue that鈥檚 a great question right. So let鈥檚 learn about it. So my solution was design studio and how did I do that so one JavaScript file at the bottom of every single one of my templates that were in use across the fifty five thousand pages and that comprised of the fifty five K. So what I did was as I added that JavaScript file reference at the bottom of every template for that landing page itself and I added the JavaScript code in order to add to every anchor tag that had the target equals blank that鈥檚 a different solution but it allowed for me to. Test that JavaScript when I knew that it worked the way that I wanted to and that I was able to push that code into that one singular file and then it seamlessly went across all of my different. Marketing activity workspaces landing pages and everything that was needed and I didn鈥檛 have to do anything to update that code on those pages it was all seamless I didn鈥檛 have any workspace blockers I was able to just get everything done quickly and efficiently. And the big part about it is that marketo has these little secrets where you can transcend workspace blockers right so all references to the file all updated all at once very quickly it deploys instantly across thousands of pages and I don鈥檛 have to individually update each page. Yes very very cool experience solution to being able to solve that problem.

So design studio allowed me to do that and it allows me to do a lot more than just those things right so these are all the things that we鈥檙e going to go through but mostly we鈥檙e going to go through encapsulation and how resource reusability is super important and how to think about it in design studio. So I call it the art of organizing right marketo engage works in levels that鈥檚 how I like to think about it so design studio is resource level encapsulation the databases lead level encapsulation and marketing activities use both empowers my analytics. So if I do it right I鈥檓 able to tell the story through analytics of how my programs performed did somebody attend my webinar did somebody download the white paper did somebody do the action that led to the success that allows me to tell the story to my leaders and what we鈥檙e doing for marketing activities.

So if you take a look on this right side this is a typical workflow that we鈥檙e doing at Prudential right now and I鈥檓 always organizing my market I was my original source type that鈥檚 my top level right so I鈥檝e got my different channels in this is an omni channel orchestration so my salesforce intake my web service API intake my list imports and my web form fill out all common channels that are built out of the original source type.

So design studio encapsulation resource level the profile level the pro sorry databases lead profile level marketing activities is my lead profile level mixed with my programs top level being original source type middle being lead source mapping and my bottom being my compliance and operational governance are powered into you said it right my analytics and that allows me to tell the story that I鈥檓 trying to tell. So understanding design studio is really important and all of the factors that lead to success versus dot right so if I have all my resources on this left hand side right email templates emails forms images and files if I鈥檓 an admin I need to know is it do I can I share this with a another workspace yes or no right emails I can鈥檛 forms I can鈥檛 but image and files guess what I have no blockers right so that鈥檚 why there鈥檚 an asterix here and things update automatically. But you鈥檒l notice that my CSV download as an admin I need to be able to track all my resources and if I can鈥檛 download things out of marketo then I鈥檝e kind of got a problem once it starts to get to scale so the API is a great injunction to wait for me to be able to figure out different routes that I can take to get that information. But the one thing that to take into consideration out of the box many pages is really only thing that I can actually download right so it鈥檚 important to know these things and it鈥檚 important to know the blockers that you would run into in design studio so that鈥檚 why I鈥檓 showing them. But you鈥檒l see that I also if I make updates to templates right email templates to our require page email approvals to push code for email templates that鈥檚 the email template itself but for emails everything that鈥檚 tied to that template I would need to update the draft of that email to pull in all my new email template code same thing with landing pages right but with images and files. Images and files I鈥檓 able to do it and interactive webinars there鈥檚 no impact landing page templates you get the idea right I can send everything to a draft and when I update my forms it sends everything to a draft and so forth so it鈥檚 important to know the differences between all those things and what those capabilities are the big one is is that if it鈥檚 got this share icon right here then I鈥檓 going to be able to share it with other workspaces so workspace shareable very important take note of that. Alright so let鈥檚 build the ideal webinar program how do I do it so if I have my kennel engage in program template with design studio my connections right so here鈥檚 my designs to here鈥檚 my marketing activities and then here鈥檚 the connection between the two so let鈥檚 build it out right so in design studio have my email template about my footer snippets got my landing page template and I might have my form right so let鈥檚 see how I need to get those things into marketing activities to build out my program in an encapsulated manner right so I鈥檝e got my spark campaign template and I鈥檓 going to have my email template and I鈥檓 going to have my email template and I鈥檓 going to have my footer snippets and I鈥檓 going to have my landing page template and I鈥檓 going to have my form right so let鈥檚 see how I need to get those things into marketing activities to build out my program in an encapsulated manner right so I鈥檝e got my spark campaign template and I鈥檓 going to have my email template and I鈥檓 going to have my footer snippets and I鈥檓 going to have my form fields I got my status updates I鈥檝e got my email triggers that send to my customers right if I have my invite email invite email to thank you email no show email or recap email right I in theory want to have all those things built off of the same template right same with my registration pages I want to have a multi-use multifaceted template that allows for me to encapsulate all those things all into one landing page template all the one email template so when it breaks out it looks a lot like this my snippets will be able to cover my registration page as well as my emails for your email new email editor doesn鈥檛 use snippets so just keep that in mind the email template itself comprises as all of my different invites right so multi-use email template covers all of the different bases that I need and configurations and then I鈥檝e got my forms which only touch my registration and thank you pages right but you can see that that鈥檚 how it works out and so then as we continue to move forward we鈥檒l understand design studio plus the marketing activities and how I power my programs so same idea same model except now you鈥檙e seeing how it all comes in into play so I鈥檝e got all my all of my resources all encapsulated into one particular program and I鈥檓 able to then encapsulate everything into one event program right and that has all of these things all built into this design studio which allows me to keep everything nice and consolidated and I鈥檓 able to then move forward in the system by keeping everything nice and constant in terms of how it鈥檚 making references and which solution which resource it鈥檚 actually touching if I do all that right it allows me to scale market without having to manage a ton of downstream resources with my my parent templates right my email template in my landing page template actually have only one reference that I have to make and makes consolidation much easier and much more practical so we鈥檒l do the same thing right same idea but when you scale it out look at what happens now becomes more imperative that I have everything all consolidated nicely and then that way I can build all these event program templates I can manage all the resources that are in these things by continuing to make reference to those templates right this is called resource encapsulation in a nutshell this is how I build all my programs all my market instances across all of my different players this is the same model that I like to focus on so let鈥檚 understand workspaces right what are the tips and tricks for workspaces so the art of marketo engages understanding what doesn鈥檛 break marketo right it鈥檚 kind of a weird concept but it鈥檚 really true right I can鈥檛 architect marketo if I architect marketo in a way that breaks marketo like that kind of breaks my model and doesn鈥檛 allow me to kind of do the data flows and workflows that I need right so when you add in workspaces they鈥檙e very functional in terms of how they can work for large organizations however workspaces create complexity with design studios right so let鈥檚 learn how so our resources that if I鈥檓 using workspaces our resources must be available in that workspace for someone to clone a program with all the necessary elements I create one single location for program templates to live and that can be a folder or its own workspace so if I have a CoE or a set of excellence that has all my template I can have my marketers clone from that center of excellence and they can go into the actual marketing workspaces where they鈥檙e conducting their marketing and I also have to make sure that all those resources are shared with that workspace in order to successfully make the clone right otherwise you鈥檒l be blocked and say oh that resource isn鈥檛 available in that workspace that鈥檚 a common one that a lot of people will hit right so you want to pre build your programs with the idea that you need to share them with the workspaces where they鈥檙e actually going to be needed later right but the nice thing is is that when you start working with images and files you鈥檒l notice that workspaces are actually not blockers and that it will transcend all workspaces and it doesn鈥檛 have to be shared so that鈥檚 kind of a nice thing that you know I definitely highlighted over and over and over again right another cool thing is is that programs can actually be used as transport containers right so if all the resources that are in that particular program live in the other just at workspaces I can easily take that program and I can move it into those other workspaces pretty seamlessly but I have one caveat to that is forms are actually can鈥檛 be put into the program itself you want to try to avoid that the program will make reference once it鈥檚 cloned in that workspace to the form that鈥檚 in that workspace forms don鈥檛 travel the only way is if they鈥檙e unused and you can put them in a folder and you can actually drag them from here to the next workspace if it鈥檚 unused if it鈥檚 used by something in that workspace you鈥檒l get an error and it won鈥檛 work right but it鈥檚 important to understand some of those ins and outs of how design studio works so partitions in general are really great because they can create custom data flows between workspaces so if you have one workspace that needs to see visibility into this particular database but you don鈥檛 want them to see in another partitions is a great way to do it I like to think of it is many many databases that actually live in Marchetto that actually manage your data in a way that matters to the business so for instance you have geographical data for GDPR is a great example like I want my EU data to be consolidated if I鈥檓 using the same instance or I have HIPAA compliant data where I need only a few people in the Marchetto instance to be able to have access to that because of those different types of things partitions are a great way to do that so the nice thing is is that we can create any combination of program templates for marketers we enable the sharing cross workspaces and you know the different clones otherwise the systems won鈥檛 allow the clone which is what I said right so when you break it out it looks a lot like this so I鈥檓 now able to push all of my things to the workspaces based off of my marketers needs and then the forms also need to be pre created in that workspace and make reference to it right programs can be cloned to any workspace and here鈥檚 a tip forms don鈥檛 travel programs and I made reference to this it must be referenced in the workspace after the program is clone and try at all costs to avoid form program level forms try to build all of the forms if you can in design studio I know everyone鈥檚 got different strengths but this one is a really important one to make reference to so resource encapsulation efficiency is where it鈥檚 all where it all lives right using templates to power emails landing pages and snippets across program templates creates that one to many enablement that everybody talks about right all these resources can be edited and change at the program level and I can edit and push code very efficiently to all those resources and then I can update them using design studio it鈥檚 very very helpful everything is connected it keeps up with the scale minimizing the amount of technical debt technical debt is a major killer for MOPs teams if you鈥檙e doing work that doesn鈥檛 actually provide value for the business but it just keeps you up and running then I hate to say it but you鈥檙e you鈥檙e probably not doing it right and you want to be more efficient with how you doing things in Marchetto efficiency is king I cannot stress that enough so if you follow this model with any program template design it allows for you to encapsulate those webinars content downloads contact us operational cues and so much more and allows for my MOPs to be more proactive as opposed to reactive to those fires right very very important that you understand these things it really goes into template reusability one landing page template for many single pages multiuse templates are key responsive adaptable Marchetto engages in a website it鈥檚 an expensive it creates inexpensive stand alone pages that are highly adaptable to the use case right Marchetto is really a great example of that Marchetto is really good at having pages that have forms on them that are otherwise caught really expensive for other businesses to be able to create so think of if you have to custom build every single webinar page that is relatively follows the same kind of look feel and design well Marchetto is really good at allowing us to quickly adapt and push those pages out that allow for me to capture that webinar registration very efficiently and inexpensively it鈥檚 inexpensive low code no code and it鈥檚 incredibly fast go to market great for webinar white papers and on demand videos events all the things that you can think of that don鈥檛 need that custom development that have prebaked pages that are already readily available here鈥檚 an example of them these are women in power things I鈥檝e done for potential here鈥檚 our blueprints to black wealth one of the many things that we鈥檙e doing and but you can see I鈥檝e created intake for all of these stand alone pages plus I have multiuse templates that allow for me to handle all of my emails and configurations and all things that I need to do much more cost-efficient building everything from scratch so forms best practices right so really want to emphasize that forms can create a lot of technical debt if you don鈥檛 do it right don鈥檛 just use forms use forms have a strategy with how you manage these assets forms create debt it really does if you have too many forms it takes about 30 seconds to load up each form and if the forms are really big form it takes even longer right so from a marketing admin perspective managing this upfront is critical right use program level forms try to avoid that at all costs it鈥檚 hard to recreate you can create one form that can serve so many different use cases in your system if you do it right forms controller is very limited and it鈥檚 on a per workspace basis so if you have multiple workspaces you can only make reference to all those forms that are built in that workspace even if you do it right it鈥檚 still can create technical debt but it鈥檚 good to be able to manage that upfront so that you know what you鈥檙e getting yourself into as opposed to going into a scenario where it鈥檚 very problematic right and compliance fields should always be a constant you create one compliance field and that compliance field is referenced in that form and you never change it it should always be the same thing otherwise I don鈥檛 even you gotta you gotta keep everything the same create global triggers activating based on naming convention in your forms and also these things will bypass workspace blockers so naming convention for making references to people filling out forms will bypass your blockers another really cool thing is you can add JavaScript in your forms to be able to add additional configuration as well as all of your UTM parameters always want to capture those at all costs so let鈥檚 bring it all together so my use case is this I have program attribution from a third party content syndicated cloud integration daily MFT file transfer uploading process that鈥檚 a mouthful right so let鈥檚 look at it so I need to get my cloud integration I need operations to run through it I need my program template to capture the data and I need to route those same leads to compliance I create a fork in the road and I鈥檓 able to create nice repeatable designs using all these concepts and I鈥檓 able to capture my compliance as well as my program attribution while I鈥檓 also able to capture from a third party that may not be using native forms or native integration right not using this is a recurring daily load that I need to be able to account for so I鈥檓 getting away from manual intake manual list imports and I鈥檓 able to capture my data from a third party I鈥檓 able to move forward and not have to worry about any of that I don鈥檛 know happens behind the scenes automated it鈥檚 really really good so images and files and marketo engage a this is a big one so here鈥檚 how you do it so how to upload a JavaScript file go to the design studio from your local computer save your JavaScript file uploaded in design studio and then you capture the URL the design studio throws at you add this reference script source equals the file URL is provided add this at the bottom you can also do this for CSS it packages up code allows for you to create encapsulation on your web resources and it鈥檚 a one-to-many scenario this is how I did it for my know my the issue that I faced in my previous employer for the target equals blank tab nabbing piece right so one many serials can be solved with one URL that鈥檚 how I do it so a em assets is great for organizing your dam at enterprise scale so create image renditions very like is image renditions so I鈥檓 allowed to break up my images into all the various sizes that I would need to account for right so images could be smaller for my email it could be bigger for my landing pages and so forth am is incredibly powerful tool and I highly recommend people go to the am skill exchange and learn about all the benefits to am assets as well as am as a CMS can actually support their all really really good stuff. So let鈥檚 compare the new verse the old email designer right so the benefits of the new email designer there鈥檚 no more custom code that I need everything is baked into the email designer meta tags don鈥檛 need are not needed to enable expanded function snippets are now called fragments conditional content originally dynamic content can be built into each section of the email which is super handy velocity and handlebars is gotten getting a much needed upgrade it鈥檚 a lot easier to build your velocity handlebars dynamic random rendering for your emails it鈥檚 built in email browser code so it should transition nicely to all the different email clients and I can also incorporate AI into my design factors the big one that I see though is that structures replace what are called custom modules and custom modules need to be hand built by meta tags but these structures are now all pre built into the structures of the email allowing for much more seamless experience.

So the preview mode is more easily accessible right I鈥檓 able to incorporate AI I鈥檓 able to do a bunch of really cool things it鈥檚 a huge advancement in terms of what the email editor is capable of doing and I鈥檓 definitely more excited now to get more involved in the new email editor it鈥檚 really good incorporates gen studio and Firefly for fast go to market and it also works really well for your less technical users.

So the key takeaways right so design studio enables resource encapsulation enterprise scale is data and resource reusability and program templates allows scalability right or controllability that鈥檚 really really important in terms of understanding how you want to organize your market always use hidden hidden forms are sorry hidden fields and forms to capture utms and cookies that are super important for associating with the customer as they come through try to avoid building program mobile forms at all costs and please do it it鈥檒l be very important JavaScript file references can be placed in forms to impact functionality I can talk more about that at a later date but super cool what you can do there am assets with image renditions very cool in the new email designer and there鈥檚 just so much more that you can do this is just kind of scratching the surface to be honest with you. So the next steps for your admins what鈥檚 important here right admins in your existing instance conduct an audit see how you鈥檙e doing things for those implementing a new instance leverage this framework it will save you so much time downstream and it鈥檒l allow for you to create scalable frameworks that actually is able to generate good value for your business in the end we鈥檙e capturing data in forms and we鈥檙e sending emails to customers and if we do those things right then we can generate good revenue opportunities for the business. Practice the art of program templates right use program templates understand the keys to what make them successful.

Admins for IMS and design to try out the new email designer it鈥檚 really really handy and it鈥檚 very cool what it can do test build all the emails get familiar with it before you roll it out to your teams there鈥檚 many many many changes on that you鈥檙e going to want to know about. Also take old templates and try existing you know migrating them into the existing editor also very very handy and then practice using form intake campaigns and referring them into design studio not marketing activities. Try to avoid program level forms at all costs they鈥檙e so difficult to manage I cannot emphasize that enough I鈥檝e really struggled with that in my past and I try to stay away from it at all costs. That鈥檚 everything for now thank you guys so much for watching and I hope you guys learned a lot and I know that your heads probably hurt so make sure you rewatch it if you have any questions reach out to me directly. And with that said I will pass it over to Q&A and I鈥檓 happy to answer any and all questions anyone has thank you so much. Thanks Corey. That was some super useful stuff. Will you and PD be able to answer some questions for us? I think I have some time. PD is probably upstairs though. Okay. All right. All right. All right.

So, these landing pages that you were talking about. Do you use them on your website. Yes. So, the nice thing about domains and pages is it鈥檚 built on customer trust right so for us, I have one off Marketo pages that have their own domain but then we also have our prudential.com pages that we can embed our different form, you know, different forms on, and it creates a, you know, ton of flexibility and scale with the API is all built into those forms for Marketo it鈥檚 it makes scalability much, much easier to maintain. So, it鈥檚 really up to what the business needs to do but both are applicable and then a multitude of situations.

Fantastic. Fantastic. Can you tell us a little bit more about fragments and how they different are differentiating from snippets.

Yeah, so a fragment is basically like an experience fragment, you鈥檙e going to, if you use a, you鈥檒l know that an experience fragment is basically a pre built piece of code that has a set layout in it, so that you can fill it in with different drag and drop capabilities as well as double clicking into things and rich text editors and all kinds of various stuff. And the new editor is sort of removing the ability to utilize snippets in email, and it鈥檚 going into what is called experience fragments and experience fragments follows the same sort of convention. It鈥檚 just more tied to just email as opposed to email and landing pages. Can you give us a little bit more time for us, why you should create forms and design studio and instead of programs. Yeah, happy to. Um, so I covered it pretty heavily in my presentation in terms of why, but what ends up happening is, is when you have forms that are in your design studio it鈥檚 a lot easier to locate them when they鈥檙e built into a program that can get nested into many, many layers of programs as well as folders. And a lot of times you really want to try to focus on how do I reuse this form on multiple instances as opposed to one form per one page. If you鈥檙e using the same fields, technical debt will come when you don鈥檛 utilize your resources for reusability. If you have them hidden, it鈥檚 hard to remember where you put stuff design studio just makes it much more globally available. And when I鈥檓 making calls in my smart lists for fills out form triggers and different things like that, it鈥檚 a lot easier to locate them because they don鈥檛 actually have to remember which program it鈥檚 located in and then which form it is. So the syntax changes instead of me making a reference to program name dot form name, it鈥檚 just form name. And that actually just makes the simplification of, you know, scalability a lot easier to maintain. Believe it or not, you build something, and then a month later you have to come back to that thing, you have to remember how and why you did that particular thing and if you didn鈥檛 put, you know, notes in the description for how to do it, it becomes, you know, kind of troublesome so it really just helps you from just a mentality standpoint of why I鈥檓 doing it is because it just makes it easier to remember downstream, as opposed to having things sporadically located in Marketo. Part of the art of understanding Marketo is how to troubleshoot Marketo and if you have things in a multitude of different directions and different workflows, it becomes that much more difficult to troubleshoot and fix things if there are breaks. Do you have any suggestions on how it could be adapted for use with email templates built in the new email editor? How, say that again, sorry, that one, I鈥檓 not sure if I鈥檒l follow that one. No worries, no worries. I don鈥檛 know how much you use new email editor, but have you had any thoughts on ways that you can adapt email templates for your use case built in the new email editor? It鈥檚 a work in progress right now, right? The key being that I can take my email templates that were previously created in my Marketo instance and I can incorporate it into the new email editor and it will bring in all of the bells and whistles and features that I need to make it look the way that my previous template looked, but I now have the ability to have a more useful UI that requires less technical elements to get incorporated into it. Even when you use modules, sometimes modules themselves, you can鈥檛 edit directly in the rich text. You actually need to go into the HTML and add in your different elements that you might need. So it鈥檚 not a perfect science in terms of like, I only get to use code free. A lot of times with the old email editor, you still have instances where you need to actually code in the different P tags as well as the HTML to make it look that way. The rich text just won鈥檛 do it. And so this new editor will incorporate and be able to incorporate all of the new drag and drop capabilities mixed in with the ability that I don鈥檛 need to actually edit inline code. So it鈥檒l be a lot easier for somebody who doesn鈥檛 necessarily understand HTML and CSS. Got it. Thank you. Thank you. Thank you. Do you know if the new email editor allows for type controls on styles for like fonts or colors? Yeah, that鈥檚 one of the really nice features about it, actually. Instead of having to use different meta tags to be able to classify different padding or margins or colors or style and font, it鈥檚 actually all built into the new email designer. So you, instead of having to have all these meta tags that were built in the template itself in order to enable all of that configurations from a code free standpoint, you now actually just have it already baked into the template itself. And so all of those things just come standard and you don鈥檛 have to have advanced knowledge of how to code these custom meta tags to get it done. So it definitely creates a pretty significant element of convenience in my mind.

Got it. What is the best way to attribute the program to a reusable form in Design Studio? You can鈥檛 send email alerts, you know, from a program based on form fills in this scenario. So how do you like filter it appropriately? What fields do you use? Like get into that a little bit for us. Yeah, great question. So the big one is understanding how to utilize your constraints for the fills out form. Referrer is my common one that I use to differentiate between a landing page if I鈥檓 using the same form. So if you don鈥檛 have a native Marketo landing page, you can鈥檛 choose landing page like, you know, fills out form is form and then landing page is landing page. The only way to use that is to actually have the landing page built in Marketo. And in certain circumstances, let鈥檚 say my domain is actually not a Marketo landing page, it鈥檚 something else that I need to use the referrer. And referrer is actually a constraint where you add the URL of that page where the form is located to be able to differentiate. So if you鈥檙e embedding on another, you know, another domain, a Marketo form on another domain, then that鈥檚 kind of how you want to think. And you can actually test that with your form submissions on your embed, you can go into the customer profile and you can actually look for referrer. And that鈥檚 how you determine where the location of the person was and where they came from. And you take that URL string, and you just plop it right in that constraint for referrer and you鈥檒l be able to get it dialed up in terms of how you want the lead flow to work. That鈥檚 a wonderful trick that I have used many times in my career. So I hope you guys can use it too.

Love the tips, love the tips. All right. A lot of questions are coming in. How did you learn about the new email designer, the new email editor? Where did you gain your knowledge? I know I have a few spots that I鈥檇 recommend folks to you, but how did where did you go? Yeah, so another great question. Documentation is definitely where you want to start, right? It gets you in the weeds of like, here鈥檚 all the different features and things that you鈥檙e going to do. But then honestly, if you have a Marketo instance that鈥檚 migrated to IMS, just go into design studio, create your own and just start messing with it. They have lots of pre-baked templates that you can use and just start dragging and dropping different things, looking at all the different features, how you change colors, just all the things that you had to do in code previously or had to be coded in meta tags and within modules. Now you can just really you can just see it right out of the box. So it just makes things a lot easier. Just play with it and just experiment.

Great. I also mentioned too as well, we have a bi-weekly, so twice a month office hours specifically on the new email designer that you can sign up for. And there鈥檚 also a Marketo educational course that was just released in the last few months. So those are also two great places. Excellent. Final thoughts, any golden nuggets you want to share before we wrap, Corey? So just a couple of highlights in terms of things and takeaways from that, from my presentation. Less is more in Marketo. So always build with the idea that I only need to build the things I need to build in order to have success. The more that you build downstream, the more technical debt you could end up with having. Technical debt is very painful for a mops team to be able to work around. And as long as you maintain the concepts of a proactive approach versus a reactive approach, you will be able to hit your roadmap items when you鈥檙e planning at a director level position. So if my team is constantly reactive to things, I can鈥檛 actually ever move forward because I鈥檓 constantly reacting to all the fires that are coming in versus proactive. I don鈥檛 have that problem.

All right. Thank you, Corey. Appreciate all the knowledge. We鈥檒l see you soon. OK, sounds good. Thank you. Thank you all.