uBlock blocking all Marketo Forms from Mac computers | Community
Skip to main content
October 29, 2015
Question

uBlock blocking all Marketo Forms from Mac computers

  • October 29, 2015
  • 7 replies
  • 5990 views

Is anyone else having this issue? The ad blocker UBlock has recently been blocking our Marketo forms (whether embedded or not). I reached out to Marketo support and they said they do not deal with 3rd party issues but this seems like a huge problem for all Marketo customers. Anyone else experiencing this problem? Or feel like testing it on their end?

We have found that PC users do not have the form blocked, just MAC users.

If you are having the same issue I encourage you to open a case with Marketo Support.

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

7 replies

Kenny_Elkington
Adobe Employee
Adobe Employee
October 29, 2015

On your form embed code, you can swap out the '//app-****.marketo.com' in the loadForm call with '//<your landing page domain>' which should remediate this issue.

October 29, 2015

Hi Kenny,

Our web developer tried this and the form is still blocked by UBlock. Any other suggestions?

Thanks!

Julie

SanfordWhiteman
Level 10
October 29, 2015

If Marketo's well-known domains are blocked, that's not something they can remedy.  You can switch to using all custom CNAMEs for your assets and that can help in these cases.

October 29, 2015

Hi Sanford,

Several of our landing pages have custom CNAMEs. I have visited a few other company sites that use Marketo forms and their forms are blocked as well. Any other suggestions?

Thanks!

Julie

SanfordWhiteman
Level 10
October 29, 2015

Post the URL of the form and I'll take a look. The CNAME trick can be easily foiled by an in-depth check, of course. You can route around just about anything like this (say, by going through a non-Marketo IP) but at a certain point there are diminishing returns.

November 3, 2015

uBlock sent me to Easy List who got Marketo whitelisted. All our embed forms are now working when the ad blocker is turned on.

Julie

SanfordWhiteman
Level 10
November 3, 2015

Good news! But marketo.net is still on EasyList-Privacy and mktoresp.com is still on EasyList-Tracking. I guess they realized they had misclassified, but anyone who uses those auxiliary lists is going to have problems.

November 4, 2015

Do those host forms as well? I could reach out to EasyList again to request that they whitelist those. I am very surprised that Marketo Support isn't handling this . . . maybe I should start charging them for my time.

November 5, 2015

All of ours are still blocked - finally know why some people were complaining our site is useless

SanfordWhiteman
Level 10
November 5, 2015

I'd try the CNAME method, as your domain is not going to be in those public databases.  Note you need to load everything from your CNAME, including forms2.js -- obvs. that has to load first for the form to load.

I don't know if these products do reverse DNS lookups or IP-based blocking.  If they do, you're going to have to route through another IP.

Chris_Francis
Level 3
January 31, 2018

Marketo really needs to address this issue

SanfordWhiteman
Level 10
January 31, 2018

Yeah, but how could they, really? If the intent of a plugin is to spare the end user any interaction with services known to track leads, it stands to reason that Marketo forms qualify.

Even though I've openly encouraged the use of the CNAME, that workaround is ethically unclear. You're circumventing what might be the end user's desired behavior. Just like running Munchkin on your own hostname, it absolutely works, but it may still be violating the end user's wishes.

Granted, posting forms is not itself the same as tracking (which is absolutely true) but that doesn't mean the end user cares about the difference, y'know?

Chris_Francis
Level 3
January 31, 2018

Marketo either needs to be proactive with the 3rd party ad blockers OR needs to be ahead of the curve in the technology realm.  Their entire business model is based on the ability to track customers and automate marketing actions accordingly.  If they can no longer track users, they are broken and done.  So they need to be offering solutions.  Not deflecting responsibility.

Ashley_Tate
Level 2
May 10, 2018

Is uBlock Origin blocking munchkin.marketo.net//munchkin.js simply because uBlock has it flagged as a tracking script or is it being blocked because it's a third party js file?

That being said, has anyone tried to call munchkin.js via a first party url, either on their website or a Marketo landing page? 

I can test on our website since I have control over the src in the function but with landing pages, Marketo plops the marketo.net version on them automatically so I'm not sure how to handle that short of having both the third party and first party (via Design Studio) on the landing page and hope for the best?

SanfordWhiteman
Level 10
May 10, 2018

Because it's a known tracking pixel.

Trying to route around that is defying the express privacy aims of the end user. Don't do it.

Ashley_Tate
Level 2
May 14, 2018

Wasn't trying to go around the privacy of the user--I'm a uBlock user, too.

If what pre-fills forms is the same code that tracks activity then whoever is using uBlock will just have to suffer with always seeing a full length empty form and a preference center that won't show what they're subscribed to. :/

Casey_Grimes2
Level 10
May 15, 2018

So, just a note here for future reference: it seems both uBlock and Firefox's Privacy Mode are blocking resources that come from marketo.net altogether without being too picky on subdomains.

This wouldn't be a problem if not for the fact that several out-of-the-box landing page templates reference templates.marketo.net, which is caught in the desire to block Munchkin tracking. If you're still using the Marketo-hosted versions of common assets like bootstrap.css or jQuery, you need to find CDN equivalents, whether that's at cdnjs, jsDeliver, BootstrapCDN, etc.