Go to Nosto

Marketo enables clients to create re-usable Modules or add Content on an Ad-Hoc / Per Template basis.

The following guide focuses on creating a re-usable Modules which can then be added to all future templates.

1. Create your Marketo Module

One of the features of Marketo’s Email Editor 2.0 is the ability to create reusable ‘Modules’ which can be added to your Email marketing templates.

The Modules are coded in HTML and can be added using Drag and Drop within the editor.

As the Modules are completely customisable for this guide we are going to create a simple 1x Tile Module.

Modules within Marketo are built using simple HTML and follow a structure similar to the below:

<table cellpadding="0" cellspacing="0" border="0" width="100%" class="mktoModule" id="<--Module Slug-->" mktoname="<--Module Name-->">

As you can see with the above code, there are three variables which we can specify, these are:

  • id : Module Slug

  • mktoname : Module Name

  • code : Custom Code

Taking the snippet of code we collected in the first step and giving the module a name like 'Stackla - One Tile', the code we would use to make our module would be like the below:

<table cellpadding="0" cellspacing="0" border="0" width="100%" class="mktoModule" id="stackla-onetile" mktoname="Stackla - One Tile">
<a href="https://snaps.stackla.com/10/stacklarunclub/run-club-01.html"><img

2. Adding a Module to a Marketo Template

Once we have created this module code, we can now look to add it into our Templates.

There are two ways in which a Module can be added to a Marketo Template. The first is via the Module component available on the Right Hand side within the Email editor.


Through this option, users can simply search for their recently saved Module, in this case 'Stackla - One Tile' and drag it into their template.

The second option, and is more useful if you want to make these modules a permanent part of your Email template is via the Template code.

For this option, users can simply insert the Module code they have generated previously into the HTML structure of their respective custom templates.

Did this answer your question?