Troubleshooting Visited Web Page Filters/Triggers Giving Invalid URL Message and Red Squiggly Line

Included in this article



Have you ever tried to enter a web page into a Visits Web Page trigger or filter and gotten an unexplained red squiggly line? It looks like the one you get in Microsoft Word when you have a spelling error.


You hover your mouse over it and it says "Invalid URL" even though you know that the web page is a good one. This can be a frustrating one, but here are a few things to look for to troubleshoot this problem.



Troubleshooting To Try

There are a few different reasons why this could happen. You could have an error in the formatting of the URL entered, you could have a page that isn't being tracked or hasn't had any visitors. Here's what to check for.



http:// and https://

Using http:// or https:// in the beginning of the URL can cause the red line to appear. Check if you have it in the URL. If yes, remove it and the red line should disappear.





No Munchkin Tracking Code on Web Page

If the web page you're entering doesn't have the Munchkin tracking code on it yet, there's no way for Marketo to "see" the page at all. Make sure the Munchkin code is on the page and is actively tracking as it should be. For more details, check out Add Munchkin Tracking Code to Your Website - Marketo Docs - Product Docs



No Visitors to the Web Page Yet

Another cause for the red squiggly line to appear is if there have been no visitors tracked by munchkin on the targeted page. Filters look through lead record activity logs for the activity they're looking for. If the filter is searching for leads that have visited a particular web page but no leads have logged that activity yet, the filter can read this as an invalid URL, similar to if there were no Munchkin code on the page.

  • Check the page for visits.
  • Make sure you have a munchkin installed on the page you are requesting.
  • Create a test lead and visit the targeted page.



Tips for Triggers and Filters

Here are a couple of things that may help when using these filters and triggers.




"Is" Selector

  • In Triggers and Filters, if you use the selector "Is", (as in "the web page IS") then the results returned will only be those from an exact URL match. If you want to also find results for the page, they won't be returned when using the "is" selector.



NOTE: The "is" selector will return results in filters much faster since it is only looking for exact matches.



"Contains" Selector

  • If you use the selector of "contains", (as in "the web page contains"), then this would return results for all pages that have Therefore, would match. The page would match. All variations of that site would match up.



NOTE: The "contains" selector in filters will take a little longer to process because it has to evaluate the entire URL string in every web page visited to identify whether there's a match for the value anywhere within the URL. It's not extremely long of a delay, but you may notice a little slowness.