Invalid value for Web Page. URL not found | Community
Skip to main content
March 16, 2013
Question

Invalid value for Web Page. URL not found

  • March 16, 2013
  • 13 replies
  • 3458 views
Hello,

I'm attempting to add an anonymous smart list for a specific blog post. I have a munchkin code on our companies wordpress blog

This page does not appear in the drop-down auto-suggest and when I past the URL into the filter I recieve an error "Invalid value for Web Page. URL found."

I have accesed this page from my home IP and a device to try and trigger marketo to recognize this page but it has not worked so far. 

The other blog posts are being recognized.

Thoughts?

Thank you for your time

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

13 replies

November 13, 2013
i
Giles_Rossi1
Level 2
February 11, 2014
I have experienced the same issue. Changing from "is" to "contains" resolves the error but does not show any results.
August 5, 2014
Not to totally resurrect an old, dead thread, but I was having this same issue.

Tech support said the "Filled out form on:" constraint ONLY is supported for landing pages built within Marketo UI, and since none of our pages are official marketo landing pages, we would be unable to use this feature.

With Ryan's help, I was able to figure out a solution (that worked for us).

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).

This seems to be working for landing pages that are not created through/hosted with Marketo; and all our forms we simply extract the code from the Marketo created form (non-scripted type, just plain old form code that submits through marketo).

Hope this helps someone else!

Edit: This same kind of thing could be accomplished with an invisible auto-filled field that looks at the page the form is embedded on's URL. Since I didn't really feel like updating our form templates site-wide though... we went with the above.