Invalid value for webpage

[Anonymous]

I am trying to do something I thought was pretty straightforward. For my smartlist, I want a trigger to occur when someone fills out a form on my landing page. I have the 'fills out form' trigger selected, have the correct form there, but the webpage URL keeps coming up as invalid. 

http://offers.indeed.com/ExploreLondonII_201402Q2SJALLUKEVENT00029.html

That is the URL that was generated after I created my landing page. In the smartlist it doesn't give you the option to select 'contains.' It's just 'is' or 'is not' for the webpage options.

Any ideas on why this is happening or what I could do to resolve?

Thanks!

[Dory_Viscoglio]

Michael, have you tried removing the http:// prefix? That has worked for me in the past so that it is a valid URL.

[Anonymous]

Hi Dory - thnaks for the tip. I tried removing the http:// but still no go... 

[Anonymous]

Are you certain that your munchkin tracking code is working on that page? Have you done anything to customize its deployment?

I've run into similar problems, and the only fix that I found for my assets was to use the Asynchronous jQuery variety.

[Anonymous]

I had the same problem, and I noticed an almost identical conversation going on over here: https://community.marketo.com/MarketoDiscussionDetail?id=90650000000PZmOAAW

Basically, I contact support and they said unless the page the form is on is an official Marketo landing page, the "Filled out form" with constraint "On page" will not work.

WIth the help of another community member, I managed to come up with this work-around that worked for our environment:

Instead of using the "On Page" constraint, I switched to using the "Referrer" and using the "Contains" logic, and then simply plugging in the URL of the page with the form of it (minuse the http:// nonsense).

Be aware, your mileage may vary. The main reason (that I can tell) that Marketo is counting the page the form is filled out on as the "referral" page is because we basically rip out the html from marketo generated forms and we don't actually use any of the normal JS that goes along with Marketo forms. This solution may/may not work if you use more complex forms, or if you use them in the officially supported way.

[Adam_Vavrek1]

Michael, have you considered using a new form (cloned) for each campaign?