Skip to end of metadata
Go to start of metadata

Deep Dive

Tired of reading? Watch this cool video with step-by-step instructions.

Guided landing page templates have a special syntax. Use this syntax to specify what is customizable and where content will end up on each landing page built from your template. Only the regions or variables you specify as editable will be available for customization within the “Guided” landing page editor. 

Tip

Use good naming conventions and your marketing team will fall in love with you.

There are two ways to declare that something on your page should be editable:

  • Declare an object as an "element". The landing page creator will be able to add images, text, or Marketo assets into those specified regions. 
  • Declare a string as a "variable".  The landing page creator will be able to replace that variable with a string, color, or boolean state from a true/false lever. 

Editable Elements

Elements are declared by adding a normal DOM element to the template, then decorating the element with a Marketo-specific class name.

Text

If you define a region as Rich Text, users will be able to edit its contents using Marketo's Rich Text Editor.

Required attributes:
class: "mktoText"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
The content of an element with class mktoText (if provided) will be used as the default value for the editable region.

Example:

Image

You have two options for defining editable Image Elements. You may use either a <div>, which specifies a container that the image will be inserted into, or an <img> tag.

Option 1 – Use a <div>

Required attributes:

class: "mktoImg"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
mktoImgClass: String. The value here will be added to the class attribute of the <img> element inside the div.

Example:

Option 2 – Use a <img>

Required attributes:
class: "mktoImg"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
src: String URL. This will be used as the default value for the image.

Example:

Note

When using the <img> version, the rendered HTML will contain a generated div wrapper around the <img> tag. It will be set to class .”mktoImg.mktoGen,” and will be display:inline-block.

Form

Example:Required attributes:
class: "mktoForm"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Snippet

Required attributes:
class: "mktoSnippet"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

Share Button

Required attributes:
class: "mktoShareButton"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

Video

Note

When using the video element in a landing page, Marketo only supports videos from YouTube. If you use another service, we recommend utilizing a rich text box and pasting in the video's embed code.

Required attributes:
class: "mktoVideo"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

 

Poll

Required attributes:
class: "mktoPoll"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

Referral

Required attributes:
class: "mktoReferral"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

Sweepstakes

Required attributes:
class: "mktoSweepstakes"
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Example:

Editable Variables

All variable types are used by referencing the value of their id attribute wrapped inside of a ${ } character sequence.  They can be used anywhere in the document, except for inside of other variable declarations.

Example:

 

Declaration:

Variables are declared as meta tags inside the <head> element of the template. There are three types of variables available for use: String, Color, and Boolean.

String

Required Attributes:
class : "mktoString",
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
default: String value for the attribute. Blank if none provided.
allowHtml: "true" or "false".  Controls if the value will be printed without being HTML escaped.  Defaults to "false" if unset. 

Basic Example:

 

Example with all attributes:

Color

Required Attributes:
class : "mktoColor",
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
default: A 7 Digit HEX character color code. Eg: "#336699"

Basic Example:

Example with all attributes:

Boolean

Required Attributes:
class : "mktoBoolean",
id: ID string. Contains only letters, numbers, dash "-", and underscore "_". No spaces allowed. Must be unique.
mktoName : String. This is the display name that will be shown in the landing page editor. Best practice is to use a descriptive name.

Optional:
default: Boolean string. "true" or "false" controls if the value starts in the ON or OFF position. "false" if not provided.
false_value: String. The value to be inserted for the variable when it is in the OFF position. "false" if not provided.
true_value: String. The value to be inserted for the variable when it is in the ON position. "true" if not provided.
false_value_name: String. The display name to be shown in the landing page editor when the value is in the OFF position. "OFF" if not provided.
true_value_name: String. The display name to be shown in the landing page editor when the value is in the ON position. "ON" if not provided.


Basic Example:

Example with all attributes:

This example shows a common use case where a boolean variable controls the visibility of a css element by setting the value of css display property to either "block" or "none" to show/hide an element by id with CSS. The landing page editor will use the display name Show/Hide instead of OFF/ON.

Note

Program tokens (my.token) can also be used anywhere in Guided or Free-form landing pages.

  • No labels