Munchkin code for the different websites

[Tatiana_Breygin]

Good day everyone,

Could you, please, help me to sort out the situation. We have a few websites (one - for the company in general, others - one for each product). It's important to track the websites of the products separately (as they differ in audience, structure, cost of the contract, etc - so we should see the data for analytics separately). Is it possible to do this without workspaces and partitions? As this module is not included in our contract. If yes, what should I do with munchkin code for it to track this info and divide it for the reports&analytics?

Thanks in advance

[SanfordWhiteman]

Are you actually (from the top of your company) committed to deliberate duplicates just so you have different web activity logs? This is a bad idea.

[Josh_Hill13 · Accepted solution]

A solution is to go to developers.marketo.com and customize Munchkin to better handle multiple websites.

You can put munchkin on all these sites, however, Marketo won't merge the Anon info until they fill out a form with the same email address on ALL the sites.

I believe there are ways within Munchkin and Adobe or GA to better tie people to a single record.

[SanfordWhiteman]

You can put munchkin on all these sites, however, Marketo won't merge the Anon info until they fill out a form with the same email address on ALL the sites.

But that's the point: if the leads are supposed to be merged, you can no longer "see the data for analytics separately." The only way to forcibly segregate web activity logs is by having different leads. Otherwise, Munchkin merges automatically across subdomains of the same private parent domain, and will merge across even completely different public domains once someone fills out a form or clicks an email linked to each domain.

The ask is overly vague, so who knows...

[SanfordWhiteman]

So what did you mean by "track the websites separately"? It was never clear what you wanted to happen.

[Tatiana_Breygin]

Hi Sanford,

As I don't quite understand how the system works yet, I wasn't able to put my question clearly. I'm still wondering will I be able to have the reports on traffic showing me which webpage it is coming from if I install one Munchkin code on all of them. But I guess I won't understand it untill I see the first report

[SanfordWhiteman]

I'm still wondering will I be able to have the reports on traffic showing me which webpage it is coming from if I install one Munchkin code on all of them.

You can use the same Munchkin embed code on as many websites as you want.

You must make sure to share the same Munchkin cookie as broadly as browsers will allow: if you're using any 2-letter TLDs you must use a custom Munchkin config).

But due to age-old browser restrictions -- which cannot be circumvented -- browsers will not share the cookie across different private domains. A new, unique cookie will be generated if a shared one is not found. That is:

• example.net, pages.example.net, and www.example.net share a private domain, so they can also share the same Munchkin session cookie. If someone is initially known on only one of those domains, their activities will also be tracked on the others automatically.
• example.net, example.org, and example2.info will not share a cookie. Thus if someone is initially known via pages.example.net and later visits otherpages.example2.info (without filling out a form on example2.info nor clicking a link in a Marketo email that leads directly to example2.info) their activities on *.example.net will be tracked to their lead in Marketo, but their activities on *.example2.info will remain anonymous and will not be shown alongside their lead in the database until such time as they associate themselves (or are associated via API, but that's another matter).

I don't know what else you're wondering about exactly. If by the "webpage it is coming from" you mean "Does Munchkin log the hostname, pathname, query string, and hash for all hits?" -- of course it does. It would be nonsensical for it to not be able to tell between example.net/page1.html and example.org/page1.html.

[Tatiana_Breygin]

Thanks for such a detailed answer and your time! I think that's enough info for me for now.

[Dan_McGinn3]

Hi Sanford! We are dealing with a similar issue. You mention a new unique cookie will be generated if a shared one isn't found. Can you elaborate on how to create a shared cookie? Any resources you can provide would be great - not a developer here.

Thanks!

[SanfordWhiteman]

As mentioned above, you make sure the cookie is as shareable as possible by setting it at the shortest private suffix (SPS).

For www.example.com and pages.example.com Marketo will automatically use the correct SPS.

For www.example.ly and pages.example.ly you need the tweak in my blog post in order to make sure example.ly is used.

You'll never be able to share across example.com and example.ly, no matter how broadly those individual cookies are configured.