Leverage external css and js in Marketo Landing page?

[Edward_Unthank_]

Marketo Support is wrong on this one. It might not be officially supported, but it works very reliably in every (20+) instance I've done it in.

I use a combination of placing tokens directly into the HTML template of the landing page as well as putting tokens into WYSIWYG elements through the landing page editors.

This page contains both, without your ASCII problem:

• On that page, here's a directly-embedded token into the HTML template: "<script src="http://etumos.com/mkto/js/marketo-lp.js"></script>"
• That page also has WYSIWYG tokens such as the Form title: "We'll email it to you!"

 
A thought regarding ASCII—are those text tokens or rich text tokens? If you're copying and pasting the HTML into the WYSIWYG (aka rich text token), it can convert the HTML into ACSII.
 

Best,

Edward Unthank | Founder, Etumos

[Anonymous]

Hi Edward. Interesting!!!

I am using the regular text token.

Question about how you use it - for your first example, which part is the token? The whole script? Or just the URL?
And to make sure I am trying the correct token type - are you using local tokens? For example, in mine I coded my url image with src="{{My.Event_Image}}"

[Edward_Unthank_]

Whole thing! I change where I use the tokens and to what extent. I try to have as robust and scalable setup as possible, so how that works depends on the situation. 

Here's an example:


All those "Universal" and "Folder" named tokens are in the HTML templates. The local tokens are generally in the the WYSIWYG elements.
 

Best,

Edward Unthank | Founder, Etumos

[Anonymous]

Hi Edward - I finally heard back from Marketo Support. The problem was case sensitivity of the token name in template wasn't matching what I had in my program!!!