Hi,
Do you guys know if the Visits Web Page trigger works the same for both Marketo Landing Pages and our own website pages? In other words, do we have to add the pages names differently on the trigger operator if its a Marketo landing page versus a webpage (Like www.google.com versus https://www.google.com)?
Thanks,
-Leticia
Solved! Go to Solution.
don't include the https:// , unlike if you use "web page: starts with."
No, the [Starts With] constraint does not use the protocol, either.
As I explained above, in Marketo filters, the "Web Page" is composed of the host + pathname + hash components. It does not contain the protocol (nor the two slashes after the protocol) nor search/query string.
In case you aren't familiar with these components, every absolute URL is composed of 5 principal text components[1] and a few static delimiter characters which glue other components together.
A couple of other notes:
[1] I've borrowed from and simplified two different standards here (the generic URI standard and the HTTP-specific URL standard) to get the different terms across for a general-ish audience.
[2] Note Internet Explorer does not correctly parse pathnames according to the standard, as it doesn't include the starting "/" (i.e. it incorrectly considers the "/" to be a separate character). This can cause some nasty problems in JavaScript.
[3] Not every webserver bothers to do a case-sensitive match on incoming URLs. That doesn't mean URLs aren't case-sensitive, as proven on millions of sites. You can't guess that a given site ignores case, it has to be specifically tested.
For non Mkto pages which are being tacked via Munchkin, you would want to use "contains" and URL string - google.com
Marketo LPs will appear just as they are named in Marketo.
For non Mkto pages which are being tacked via Munchkin, you would want to use "contains" and URL string - google.com
You can do [starts with] "www.google.com" in this example, you don't have to use [contains].
In Marketo, the Visits Web Page activity defines "Web Page" as the original hostname + pathname + hash, but not the protocol nor the query string.
So if you see
http://www.example.com/my/folder/page.html?search=223#section1
in your browser's location bar, to Marketo the "Web Page" is
www.example.com/my/folder/page.html#section1
The query string is also stored, and can be used as a constraint, but (to my repeated frustration) is not present in the "Web Page" nor in the {{Trigger.Web Page}} token.
Marketo's definition contrasts with the more intuitive (to me) meaning of "web page" which typically includes the query string but excludes the hash (since the hash is not actually sent to web servers) or would include both. Of course there are always product-specific definitions, you just have to learn 'em.
Thanks Sanford!!
So, if I want a smart list trigger that looks at a Marketo landing page that's something like "www.go.mywebsite.com/email-preferences"
Is it correct to have the smart list trigger be the following:
"Visits Web Page" contains "email-preferences" ?
Thanks!!
Leticia, if it is a Marketo landing page you can simply use web page is and select from the drop down the landing page name or type in the LP name that you've named in Marketo. If it's your company's webpage with munchkin I would use web page is "www.go.mywebsite.com/email-preferences"
Thanks Jeannie, it's actually two webpages (1 a marketo landing page and the other is our website page that does have the munchkin).
So, if I want a smart list trigger that looks at a Marketo landing page that's something like "www.go.mywebsite.com/email-preferences"
Is it correct to have the smart list trigger be the following:
"Visits Web Page" contains "email-preferences" ?
As Balkar points out, if this is a Marketo page, you can choose the friendly LP name from the dropdown.
They should work the same as long as your webpage has munchkin code. You can use the trigger "visits web page" if you use "web page: is" don't include the https:// , unlike if you use "web page: starts with." If the webpage has parameters such as utms you can say "web page: is any" and add constraint "querystring: contains: utm_source="
don't include the https:// , unlike if you use "web page: starts with."
No, the [Starts With] constraint does not use the protocol, either.
As I explained above, in Marketo filters, the "Web Page" is composed of the host + pathname + hash components. It does not contain the protocol (nor the two slashes after the protocol) nor search/query string.
In case you aren't familiar with these components, every absolute URL is composed of 5 principal text components[1] and a few static delimiter characters which glue other components together.
A couple of other notes:
[1] I've borrowed from and simplified two different standards here (the generic URI standard and the HTTP-specific URL standard) to get the different terms across for a general-ish audience.
[2] Note Internet Explorer does not correctly parse pathnames according to the standard, as it doesn't include the starting "/" (i.e. it incorrectly considers the "/" to be a separate character). This can cause some nasty problems in JavaScript.
[3] Not every webserver bothers to do a case-sensitive match on incoming URLs. That doesn't mean URLs aren't case-sensitive, as proven on millions of sites. You can't guess that a given site ignores case, it has to be specifically tested.