Forms 2.0 Blocked By Adblockers

[Anonymous]

I'm noticing a number of adblockers(Ublock / Adblock Plus with addtional filters) are blocking Marketo's clientside Forms 2. Sadly these forms are completely unusable when they are being blocked like this.

Any possible solutions to this problem? Perhaps I need to take a look at the REST API instead and do on the backend instead.

Thoughts?

Thanks.

Stan Keathly

[Josh_Hill13 · Accepted solution]

Curious. First I've heard of it. Maybe support can help here?

Do you think it's some javascript? What exactly seems to be blocked?

[Anonymous]

Yeah the javascript gets blocked by the adblocker so the Marketo Forms never shows up. Hopefully the REST API is almost as simple to setup?

Stan Keathy

[Grégoire_Miche2]

Hi Stan,

What do you mean by using the REST API?

You should never add a REST API call on a client-side code. As it contains connection info to you Marketo REST API end point, it will enable any one to use it and saturate your REST API, with both the risk to populate you DB with *** data (Marketo won't control it) and also create a DOS when the 10000 calls a day will be reached.

What you can do instead is use another type of form (such as the form system from your CMS) which will post the data to your web back-end, from which you can call the REST API to insert/update the lead in Marketo. You will also need to capture the Marketo cookie value and run a REST API associate Lead. This method will have a drawback : you will not be able to capture the "fills out form" event and it will not be possible to prefill the form with Marketo values.

-Greg

[Anonymous]

Hi Greg.

Correct. I was thinking of replacing the clientside Marketo Forms 2 with a typical webform and process the form on the back-end. Just curious if these adblockers / privacy extensions will likely also block the Marketo cookie from being written also??

Thanks for the informative post.

[Grégoire_Miche2]

Hi again Stan,

You need to run the pages with a console and track the JS code execution, with the add blocker on, to see where it gets blocked and if the cookie is being placed on the disk or not. It will also tell you more on what exactly gets blocked in the form. May be it's not the JS code per se, but a specific text or element on you form.

-Greg

[SanfordWhiteman]

Correct. I was thinking of replacing the clientside Marketo Forms 2 with a typical webform and process the form on the back-end. Just curious if these adblockers / privacy extensions will likely also block the Marketo cookie from being written also??

Yes, any anti-privacy tracking list worth its salt includes Munchkin.

If you are concerned about evading these lists, you should use subdomains CNAMEd to Marketo for all Marketo communication -- including forms and Munchkin.

But bear in mind that by avoiding a tracking list that specifically includes Munchkin -- for example, EasyList Privacy -- but still using Munchkin, you are on uncertain ethical ground.

[Grégoire_Miche2]

Hi Stan Keathly​,

Have you tried the workaround I suggested here : Guided Landing Page and Ad Blockers

-Greg

[Grant_Booth]

We had this issue as well when we deployed Forms 2.0. Changing the URLs in the form code to use our Marketo CNAME instead seems to have fixed it.

[SanfordWhiteman]

Only if you also did this: Really, finally winning the Marketo Forms vs. Tracking Protection battle