HTML Box Support for Guided Landing Pages

[Casey_Grimes]

I love the new Guided Landing Pages, but there is one fatal flaw that keeps me somewhat reliant on free-form landing pages: the ability to use HTML elements. Right now, doing something as simple as adding a Wistia/JWplayer video isn't something a frontend user can do. I can set up a defined space and give a variable for a video ID, but that is certainly not the same as allowing someone to optionally add and remove a video to an area. TinyMCE won't support scripts, so I'm out of luck.

Moreover, as pushing the limits of what a Marketo LP can do is something I wind up doing more often than not, and a lot of that requires giving frontend users basic, basic script access to something being done in AngularJS and Backbone to edit a few things that need more than what variables can provide--as much as I'd like to move these styles to guided templates, it would break key functionality.

Allowing for a little more finessing under the hood would be amazing.

[Grégoire_Miche2]

Hi Courtney,

You may want to add your input to this idea :

Best regards,

Greg

[Anonymous]

God I wish Marketo would realize the major problems they have introduced by removing the html box.. Can list out so many customizations that just went right out the window and landed over at Salesforce and Eloqua. These types of mistakes can be quantified.

"Don't fix what isn't broken"

Said everyone

[Diego_Lineros2]

You can upload a js file to Design studio and then go to Landing page actions>Edit Page Meta Tags and Custom Head HTML and call it using something like

<script src="http://go.genesys.com/rs/XXX-TDW-XX/images/yourscript.js" type="text/javascript" defer="defer"></script>

You can also add here styling that you don't want from the template or it was not included on it.

[Brianna_Bridges]

Diego - have you gotten this to actually work?  Just wondering as I tried the method you mentioned above and was unable to get the javascript working correctly....the only way I seem to get it working is by having the code in the actual template?

[Diego_Lineros2]

Hi, yes I always do that, and no problem, depends on when you want to load your script, try removing the defer attribute, because that forces the script to be ran when the page has finished to load.

[Grégoire_Miche2]

Have you tried this :

• Create a variable in the template and put it in the template code where you see fit. Default value will be <script style="display: none;"></script>
• Upload the js in the design studio.
• Replace the variable value with <script src="http://go.genesys.com/rs/XXX-TDW-XX/images/yourscript.js" type="text/javascript"></script>

I have not tried it, but worth a try.

-Greg

[Grégoire_Miche2]

I have appended the idea ​to add the idea of a "Script" variable.

[Anonymous]

I agree  here - Vidyard also requires HTML space. We can put the space there and hide it, but it is still cumbersome.

[Dan_Stevens_]

This idea is now marked as "coming soon".  But we don't know when this was marked as such.  Can someone for the product team reply back to reassure us that this is indeed on Marketo's short-term product roadmap?

Justin Cooperman​

[Justin_Cooperm2]

It will come when we update the editor. No solid ETA right now.

Greg's suggestion does work here:

https://docs.marketo.com/display/DOCS/Create+a+Guided+Landing+Page+Template

Use a string variable and set allowHtml parameter to true.