The Marketo programs you attach to launchers in Jeto leverage assets that are built using email and landing page templates. Those templates, coded in HTML, follow the Marketo prescribed syntax outlined in the following Marketo documentation:

Email Template Syntax

Landing Page Template Syntax

As you can see, in both types of assets, there are 2 ways to declare an image element:

  1. Using a <div>

  2. Using an <img>

Though both methods work well, they are unfortunately incompatible with Jeto. As you may know, using the above methods results in a section in emails and landing pages that allow you to browse your design studio images directly from the email or landing page you are building. Though very useful in Marketo, Jeto cannot render the iframe and give Collaborators a view of the design studio.

As such, to optimize your templates, replace your <div> or <img> element with a rich text element ("mktoText"). From there, you will be able to use the image icon in the rich text editor to insert a token in the Image URL field as shown in the images below:

This will allow Jeto to pass the URL of any image uploaded by your Collaborator (or selected from a dropdown of pre-selected image URLs).

Please note: you cannot tokenize a Marketo image placeholder - “mktoImg” tags are incapable of having tokens, therefore it is incompatible with Jeto. Instead, you must use "mktotext" tags for any images you wish to tokenize instead.

Did this answer your question?