Guided Landing Page and Ad Blockers | Community
Skip to main content
November 24, 2015
Solved

Guided Landing Page and Ad Blockers

  • November 24, 2015
  • 2 replies
  • 6029 views

Hi- I'm pretty new to Marketo, but just updated some landing pages using the new guided templates.  One of our IT people informed me that common ad blockers are now blocking templates.marketo.net and using this domain is causing the page to be broken.  The new landing pages are displaying with things all jumbled up, like the form in the wrong place etc.  He is viewing it on Chrome 46 on Windows 7.

Everything looks fine on my end both in Marketo and when accessing the live pages.  Has anyone else encountered this?  If so, is there a solution?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by

You should set up a Cname to mask the templates.marketo.com domain

2 replies

Grégoire_Miche2
New Participant
November 25, 2015

Hi Kristen Yanchak,

The only solution I see is that you copy all the resources from templates.marketo.net to your own domain (in Marketo or on your web server) and replace in the templates all the URLs with URLs to your domain.

We are talking here about a couple of js and css files, nothing enormous.

-Greg

Justin_Cooperm2
New Participant
November 30, 2015

This is a totally reasonable workaround. The resources referenced in our example landing pages will not be updated very frequently, so shouldn't be a problem to copy them down and host locally.

Grégoire_Miche2
New Participant
November 30, 2015

Thx Justin

Accepted solution
November 24, 2015

You should set up a Cname to mask the templates.marketo.com domain

February 22, 2016

Hello Jamie,

We followed your advice: we used a CNAME to mask templates.marketo.com domain. Anyway we are stuck now. What are the next steps? Could you detail them please?
Thank you

Best regards,

Benjamin

Grégoire_Miche2
New Participant
February 22, 2016

Bonjour Benjamin,

You would rather use the workaround I posted in November (see below)

-Grégoire