Hello, Hopefully I have selected the right post location for this. I've seen a few community posts on this, but I have not yet been able to wrap my head around it with those resources. I am creating an email template and I am having trouble understanding "mktoActive" and "mktoAddByDefault" and how they work together. My goal is to have all of my modules in the sidebar/Modules tab, and then also have a few of those on the "canvas" when an email is created from our templates. For example, I have a module that I want to be listed in Modules tab and also NOT display on a newly created email using this template.Here is the markup I currently have: <tr class="mktoModule" id="module-name" mktoName="Module Name" mktoActive="true" mktoAddByDefault="false"> With this, the module is not added on creation, but also not in the Modules sidebar tab. What I found in the documentation: mktoActive: Determines whether this module appears in the list of modules within the email editor. Defaults to true. If false, the module cannot be added by an end user to an email. mktoAddByDefault: Determines whether this module will be in the canvas of a new email that uses this template upon creation. Defaults to true (if mktoActive is false, this value is ignored). From my understanding, the mktoActive attribute determines if the module appears in the modules tab in the sidebar and the mktoAddByDefault attribute determines if the module should display in an email using this template at creation. (true=visible, false=hidden, for both) I had originally just omitted mktoActive, set mktoAddByDefault to true or false (depending on the module) and when I was adding my code to my design studio email it did reflect what I needed. Once I created a template and then created a new email out of that template... the modules that weren't on the "canvas" were not in the sidebar Modules tab either. (the ones that exited on the canvas were in the Modules tab) <tr class="mktoModule" id="module-name" mktoName="Module Name" mktoAddByDefault="false"> What am I understanding/doing wrong? &#x1f605 Thanks!

RootreeCory

New Participant

Solved

How do "mktoActive" and "mktoAddByDefault" actually work?

Forum|Forum|2 years ago
June 1, 2023
3 replies
3385 views

Hello,

Hopefully I have selected the right post location for this.

I've seen a few community posts on this, but I have not yet been able to wrap my head around it with those resources.

I am creating an email template and I am having trouble understanding "mktoActive" and "mktoAddByDefault" and how they work together.

My goal is to have all of my modules in the sidebar/Modules tab, and then also have a few of those on the "canvas" when an email is created from our templates.

For example, I have a module that I want to be listed in Modules tab and also NOT display on a newly created email using this template.
Here is the markup I currently have:

<tr class="mktoModule" id="module-name" mktoName="Module Name" mktoActive="true" mktoAddByDefault="false">

With this, the module is not added on creation, but also not in the Modules sidebar tab.

What I found in the documentation:

mktoActive: Determines whether this module appears in the list of modules within the email editor. Defaults to true. If false, the module cannot be added by an end user to an email.
mktoAddByDefault: Determines whether this module will be in the canvas of a new email that uses this template upon creation. Defaults to true (if mktoActive is false, this value is ignored).

From my understanding, the mktoActive attribute determines if the module appears in the modules tab in the sidebar and the mktoAddByDefault attribute determines if the module should display in an email using this template at creation. (true=visible, false=hidden, for both)

I had originally just omitted mktoActive, set mktoAddByDefault to true or false (depending on the module) and when I was adding my code to my design studio email it did reflect what I needed.

Once I created a template and then created a new email out of that template... the modules that weren't on the "canvas" were not in the sidebar Modules tab either. (the ones that exited on the canvas were in the Modules tab)

<tr class="mktoModule" id="module-name" mktoName="Module Name" mktoAddByDefault="false">

What am I understanding/doing wrong? 😅

Thanks!

Marketo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by Dave_Roberts

From my understanding, the mktoActive attribute determines if the module appears in the modules tab in the sidebar and the mktoAddByDefault attribute determines if the module should display in an email using this template at creation. (true=visible, false=hidden, for both)

From my experience, your understanding of this is correct. I'll generally omit the mktoActive attribute b/c I rarely run into a situation where you'd want to include a module but omit it from the sidebar -- maybe a use case for this would be to force a header or footer onto the page but not be able to add another?

Here's the matrix of how I've seen these work in combination:
mktoActive = TRUE, mktoAddByDefault = TRUE: This should include the module on the canvas AND in the sidebar

mktoActive = FALSE, mktoAddByDefault = TRUE: This should include the module on the canvas BUT NOT in the sidebar

mktoActive = TRUE, mktoAddByDefault = FALSE: This should NOT include the module on the canvas but include it in the sidebar

mktoActive = FALSE, mktoAddByDefault = FALSE: This should NOT include the module on the canvas NOR in the sidebar

It sounds like you've got this setup correctly but are still seeing an issue with the modules being displayed as you'd expect them to. Is there a chance you could share your email code using the syntax highlighter here (Click HTML button in the toolbar then the </> button to add code).

Sight unseen, the only thing I could think of that might cause something like this to happen is if the modules were all NOT nested in the same class="mktoContainer" (which I would assume is a table based on your markup). Here's a link to the docs for the containers: https://experienceleague.adobe.com/docs/marketo/using/product-docs/email-marketing/general/email-editor-2/email-template-syntax.html?lang=en#containers -- this has a warning that you can only use one main container so maybe if they were in different containers something like this might occur?

Alternately, something might have gotten funny while you were working on the email template code -- a lot of times I'll hit the "Preview" button before the code is actually saved and the changes that I made (which are unsaved) don't end up sticking even though they show in the code editor. You might try copying your code from the existing template and spinning up new template and pasting the code in there. Wait for the "Auto-Saving" thing in the top right corner to do it's thing and then approve the template and try making an Email asset and see if you get any different results?

Dave_RobertsAccepted solution