PLEASE HELP!! Ad-blocking Software is Preventing our Customers from Accessing Forms, Completing Registration and the Munchkin Code | Community
Skip to main content
Anonymous
March 12, 2015
Solved

PLEASE HELP!! Ad-blocking Software is Preventing our Customers from Accessing Forms, Completing Registration and the Munchkin Code

Has anyone else encountered this before?  If so, how did you handle this (other than going directly to one of our largest customers and asking them to remove or adjust their filtering rules)?

We would certainly appreciate any assistance or guidance.
Thanks!
 
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Accepted solution
March 12, 2015

I've run into this with some restrictive proxies blocking the Marketo domain, but not our web domain, which might be what you're running into. I got around it by replacing the Marketo pod URL with the landing page domain, for example with a landing page domain of pages.mydomain.com:

Embed code from Marketo:

<script src="//app-abcd.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1951"></form>
<script>MktoForms2.loadForm("//app-abcd.marketo.com", "000-ZZZ-000", 1951);</script>

Change before putting it on your page to:

<script src="//pages.mydomain.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1951"></form>
<script>MktoForms2.loadForm("//pages.mydomain.com", "000-ZZZ-000", 1951);</script>

If you are using a Marketo landing page directly you might have to put it in as an HTML block of embed code, instead of putting in the form directly.

HTH

View reply

6 replies

Anonymous
April 1, 2015
Andy - we tried your solution and it fixed our problem =D

Thank you soooo very much!
Translate
SanfordWhiteman
SanfordWhiteman
Level 10
March 12, 2015
Problem with this approach is you are probably skipping the Marketo CDN. This will kill performance the further you get geographically from your instance. It would be much better to have a separate CNAME at your domain that points to the Marketo CDN.
Translate
Anonymous
March 12, 2015
Thanks Andy - we are going to try this first thing tomorrow - very interesting :)
Translate
Anonymous
Accepted solution
March 12, 2015

I've run into this with some restrictive proxies blocking the Marketo domain, but not our web domain, which might be what you're running into. I got around it by replacing the Marketo pod URL with the landing page domain, for example with a landing page domain of pages.mydomain.com:

Embed code from Marketo:

<script src="//app-abcd.marketo.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1951"></form>
<script>MktoForms2.loadForm("//app-abcd.marketo.com", "000-ZZZ-000", 1951);</script>

Change before putting it on your page to:

<script src="//pages.mydomain.com/js/forms2/js/forms2.min.js"></script>
<form id="mktoForm_1951"></form>
<script>MktoForms2.loadForm("//pages.mydomain.com", "000-ZZZ-000", 1951);</script>

If you are using a Marketo landing page directly you might have to put it in as an HTML block of embed code, instead of putting in the form directly.

HTH

Translate
Anonymous
March 12, 2015
Thanks Sanford!  That's what we thought as well.
Translate
SanfordWhiteman
SanfordWhiteman
Level 10
March 12, 2015
What exactly is the policy being enforced?

Both Munchkin and Forms 2.0 scripts load from a third-party domain, as you know (they do not use third-party cookies). You might try to re-host the JavaScript itself on your domain (though that's painful to maintain). But even if that worked to load the forms and/or Munchkin, eventually the user data needs to be posted to Marketo.  They could choose to stop the data post from happening.  Essentially there's nothing you can do if they have a strict (even if it's illogical) idea of how to enforce privacy.  
Translate
Terms & ConditionsAccessibility statement

Loading footer...