Munchkin tracking not working on second domain

Question

I'm having an issue where the munchkin tracking that was installed on two domains isn't working on the second domain. I've confirmed that web page activity with munchkin works on the primary domain via the web page activity report. I'm able to see where people navigate from the primary domain to the secondary domain, but I'm not seeing any web page activity for the second domain (or utm values we've been using in the emails to click on the second domain).

I read another post on this topic and I think we need to update the scripts on both domains to use an iframe and point from the first domain to the second in javascript, is this correct?

Also found this article here which seems to have provided a solution: https://purplemeup.substack.com/p/maximizing-munchkin-tracking-across

SanfordWhiteman · Accepted Answer

From the looks of that screenshot, you’re using a Brave private window. Munchkin will never load in that setup, as it is by definition a tracker and Brave is aggressive w/trackers. ERR_BLOCKED_BY_CLIENT means it’s the local browser config blocking the script.

When you switch to a browser + config that isn’t set to block trackers, your site does load Munchkin, set the cookie, and send a hit to Marketo. But that’s not necessarily all good, because when connecting from US (New York City) I get this cookie consent popup...

... yet the cookie is set regardless of whether the person clicks Accept Cookies. That seems rather misleading, no? You’re unlikely to get in trouble for it in regions without regulations, of course. But seems like it should say Reject Cookies because they’ve been implicitly accepted at that point.

Luckily, when connecting from France I get the full OneTrust popup and when I only accept required cookies the Munchkin cookie isn’t set. So it’s working correctly there.

Luckily, when connecting from France I get the full OneTrust popup and when I only accept required cookies the Munchkin cookie isn’t set. So it’s working correctly there.

Actually, one addendum: it’s not fully working in France/GDPR.

When you do accept cookies there, Munchkin doesn’t run until the next pageview or refresh. That is, you always lose the pageview where they first opted-in.

This has implications if you ever wanted to read the anonymous Munchkin cookie on that first page. Though as noted earlier, there’s no sign you have a setup that’s capable of doing anything with that cookie, even on subsequent pages, so it’s a minor problem overall.

SanfordWhiteman · Answer

Let’s track down exactly what you mean by “not working”.

Do you mean you aren’t even getting anonymous visits on the “not working” domain, or you aren’t getting known visits?

You shouldn’t expect to have known Munchkin sessions on the 2nd domain if the person only became known on the 1st domain. The cookie cannot be shared across different private domain suffixes (e.g. example.com and example2.com).

So as long as you’re getting anonymous web activities when the Munchkin session is anonymous, Munchkin is working as expected out of the box. Can we confirm that first before continuing?

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded