Here's what I got back from the dev team. Is there something basic we're missing? We've seen this behavior play out during testing.
The issue is that third party cookies don’t work in mobile safari. So, if the first touch was set on a Marketo page and then they left and later came back and filled out a Marketo page form the cookie would parse into the form as normal. But first touch will not set or read on the pages where forms are embedded or are otherwise not hosted on Marketo.
Basically that takes all traffic not on a marketo page coming through mobile safari out of the equation. We could do a few things to help capture some of those values, but ultimately anytime someone goes from a Wordpress page to a marketo page or vice versa, in safari mobile, the cookie is lost. We could set things up where anytime mobile safari is detected we set the hidden form values as something like “safari-mobile-no-cookie”, but as far as I can see in mobile safari we’re always going to have a dark spot as far as recording the cookie.
Although to answer your initial question, they are on the same domain, unless that gets tricky when you bring wordpress into it. The blog is hosted on blog.DOMAIN.com and the Marketo pages are marketo.DOMAIN.com (well, not that, but you get the picture).
The issue is that third party cookies don’t work in mobile safari. So, if the first touch was set on a Marketo page and then they left and later came back and filled out a Marketo page form the cookie would parse into the form as normal. But first touch will not set or read on the pages where forms are embedded or are otherwise not hosted on Marketo. |
Marketo does not use third-party cookies, so the premise is faulty. No modern web technology relies on transmitting or saving third-party cookies.
When Munchkin runs on blog.example.com, it sets a first-party cookie for the parent domain .example.com, or uses an existing cookie if there is one.
When Munchkin runs on marketo.example.com, it similarly sets a first-party cookie for the parent domain .example.com or uses a preexisting one.
Since they share a parent domain and the cookie was set at the parent level, a cookie set on either site will always be transmitted to the other site, so an associated session on Site 1 will also be associated on Site 2 ("associated" = "web actions linked to a known lead").
[Note: the above is automatically true for a registered domain that ends in .com, .net, .org, or another TLD that has 3 or more letters. It is not automatically true, by counterexample, for a .to domain, which requires manual configuration -- simple, but manual.]
There must be something wrong with the test environment to lead to the faulty conclusion that Marketo uses anything other than first-party cookies. It's true that Safari was the first browser to block third-party cookies by default, but that's irrelevant. Marketo cookies are not set on .marketo.com (nor .mktoresp.com or .mktoweb.com). They are set on your domain.
The significant difference between [1] an embedded Marketo form on a non-Marketo page and [2] that same form on a Marketo-hosted LP is that the former does not support form value Prefill. Thus, even if Munchkin is correctly tracking activities (page views, link clicks) and linking them to a known lead in Marketo -- that's views and clicks on Marketo pages and on your third-party site -- when the lead visits a third-party page with an embedded form, the form will always appear blank (unless it has been set in the Form Editor to display the Known Lead HTML instead, which is another configuration option). Perhaps seeing a blank form misled your developer into thinking the cookie was not present.
