Munchkin Tracking Multiple Sites

[Anonymous]

Hi,

For those with multiple brands and multiple sites but only one instance of Marketo how are you tracking page visits independently of each other?

i.e. Site A is tagged with Munchkin and Site B is tagged with Munchkin but you want to determine which site is which to create the appropriate SmartLists and Flows.

N
 

[Jep_Castelein2]

If the site is on a different domain, it will have a different Marketo cookie (cookies are domain specific). So for anonymous Leads, you'll see two Leads being created, and you don't know it's the same person. 

Once people fill out a form or click a link in an email that goes to site A or B, then the Marketo cookie will be linked to the known Lead record and becomes more actionable. If people do this for both sites, both cookies will be associated to this known Lead record. 

In your Smart Campaigns, you can say 'Visits Web Page, page starts with "http://www.siteA.com"', and that's how you keep them apart. 

[Anonymous]

I have the same question.

Putting it into specifics. It seems that when I run the anonymous website visitors report, all the traffic is attributed to one domain. So the question is how to split this out?

Thanks

James

[Anonymous]

This seems to be an old question, but I'm currently figuring out a solution for our domain change so I may have an answer. It may or may not work for what you're experiencing.

There is a workaround to send a cookie from domain A to domain B when the user visits domain A using this method: How To Set Same Cookie On Different Domains - Subin's Blog

I have not tested it out yet. But if Marketo is tracking on both domains it should be able to give you the URL they are on attributed to the right person.

[SanfordWhiteman]

This won't work for Munchkin for multiple reasons:

1. It assumes the cookie is set via HTTP Cookie: header. Munchkin cookies are set via JS.
2. It assumes browsers allow 3rd-party cookies (cookies from subsidiary assets on other domains) to be set at all. Modern browsers apply varying security to 3rd-party domains.
3. It assumes a cookie with exactly the same value on another domain will be usable once it's set. Munchkin will not see this cookie unless specifically configured (which is actually a solvable issue, it's #1 and #2 above that kill the idea).

[Anonymous]

I see, I don't quite understand the the difference between an HTTP cookie and the JS Munchkin cookie.

Well, if you do the Redirect Method: Sharing Cookies Across Domains it should be treated as a first party cookie based on what I've seen right? Would that be a plausible solution?

[SanfordWhiteman]

I see, I don't quite understand the the difference between an HTTP cookie and the JS Munchkin cookie.

An HTTP-set cookie is set via HTTP header only, so it

• is set regardless of whether an asset is rendered in the browser (you can send a Cookie: header on an HTTP 3xx redirect, or even an HTTP 404)
• can be set by assets that don't, or can't, run JavaScript, like images or CSS stylesheets or videos, or even by a broken external JS file (even if the JS is broken, the HTTP header is processed)
• optionally can be made invisible to JavaScript (this security measure isn't widely used because JS is so often used to read cookies)

A JS-set cookie

• can only be set by JavaScript running in an JS-enabled HTML document (including an IFRAMEd document)
• is used by all web analytics packages

Redirect Method: Sharing Cookies Across Domains it should be treated as a first party cookie based on what I've seen right? Would that be a plausible solution?

That method also uses HTTP-set cookies (ASP Response.Cookies == Cookie: header).

A related approach is possible using JavaScript and IFRAMEd HTML documents, but is much more complex.

[Anonymous]

Thanks for the explanation. I was wondering if there was a difference between a Munchkin cookie but I couldn't find any documentation from Marketo on it.

The Iframe method that you speak of is this: javascript - Share cookies with other domains - Stack Overflow right? The concern here is that it doesn't work with older browsers...
Anyways, my particular case is that we are switching domains, and we don't want to lose all of our cookie tracking so we're trying to figure out a way to share the cookies from the old domain over to the new one.

[SanfordWhiteman]

The Iframe method that you speak of is this: javascript - Share cookies with other domains - Stack Overflow right? The concern here is that it doesn't work with older browsers...

In line with that method, yep.

But you don't have to worry about older browsers unless you mean IE 7!  The note "HTML5 only, obviously." is misleading as IE 8 supports PostMessage (in fact Microsoft invented it before it was added to HTML5).

[Anonymous]

So based on that, do you think this method could work for preserving our cookie tracking for Marketo from the old domain to the new domain?