Web Page Is vs. Contains

I would use contains with the entire main URL you want to capture. I have found IS does not work as intended with web page urls.

so place either

http://www.company.com/page/page.html
or
www.company.com/page/page.html

CONTAINS is not "safer" for this sort of thing, if anything, it is more dangerous and makes marketo work harder.

IS works differently depending on whether you're referencing a Marketo page or non-Marketo page.
If it's a Marketo page, you use the asset's name in Marketo. If it's a non-Marketo page, you use the page's URL *without* the protocol (the http://). Keep in mind that if it's a non-Marketo page, it needs to have Munchkin working on the page, and someone needs to have visited it, in order for the URL to appear as an option in the dropdown menu.

For contains, you need to use the URL (I would actually leave out the http:// here too) whether it's a Marketo page or not. This gets a little confusing but it's difficult to avoid due to the structure of the database on the backend that the filter is pulling from.

And if your URL contains a query string, do not include in the Web page value field. Instead add a constraint to the trigger/filter to separate this piece out. For example, using the query string constraint, your value would be "source = 1"

Thanks guys.

It sounds like contains is a better logic to use in my situation. My only issue is that I can't seem to get a count. I realize Marketo is working harder, but I never see the circle stop spinning.

Is this normal??