Munchkin Tracking Multiple Sites | Community
Skip to main content
A
Anonymous
March 17, 2015
Question

Munchkin Tracking Multiple Sites

  • March 17, 2015
  • 2 replies
  • 5057 views
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
 
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Jep_Castelein2
Jep_Castelein2
Level 10
March 17, 2015
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. 
A
Anonymous
June 29, 2017

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

A
Anonymous
March 19, 2018

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
SanfordWhiteman
Level 10
March 19, 2018

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).
A
Anonymous
March 19, 2018

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?

Terms & ConditionsAccessibility statement

Loading footer...