How to set up Munchkin code on a completely new domain | Community
Skip to main content
J
jiwonhe
Level 2
November 27, 2024
Solved

How to set up Munchkin code on a completely new domain

  • November 27, 2024
  • 2 replies
  • 2481 views

Hello there, I'm Jiwon.

I would like to additionally track web activities on a completely new domain that is different from the domain name currently set on my instance. If this is possible, how should I modify the existing Munchkin code?

 

Also, I have one more question:
Can I distinguish activities by domain in the activity log of person?

 

I hope someone can help me. Thank you.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

What I meant was, as you can see, “won’t send.”

 

Let me share specifically what I'm trying to achieve.

 

I have an inquiry regarding tracking across multiple domains.

Scenario (domain information is for example purposes):

1. aaa.com domain

- The aaa.com domain will be used for Marketo landing pages and emails, with CNAME, SPF/DKIM already configured.

- We plan to track activities on three subdomains: bbb.aaa.com, ccc.aaa.com, and ddd.aaa.com. Munchkin code has been inserted.

2. abcd.com domain

- This domain will not be used for Marketo landing pages or emails.

- We do need to track customer activities, and the Munchkin code will be inserted. Based on the above scenario, what settings are necessary to enable cross-domain tracking (recognizing the same person across both domains)?

 

I have already seen the questions you left answers for resolution. I thought my question was related to these questions too.

https://nation.marketo.com/t5/product-discussions/marketo-tracking-token-across-multiple-domains/td-p/294902

https://nation.marketo.com/t5/product-discussions/munchkin-tracking-multiple-sites/td-p/132194

 

I always look forward to your help.
Thank you.


Each site will need to “peek” at the other site(s) until it finds a existing cookie. Once found, it copies that cookie value — more accurately, the token part of the cookie value — onto its domain.

 

This is done using an IFRAME element and cross-window messaging (postMessage).

 

Note you will not be able to set cookies within the IFRAME, you only get existing cookies and pull them out. Cookies are only set at the parent document’s domain.

 

All of this is quite straightforward for an experienced JS developer. Don’t assign the task to a junior.

2 replies

ilona_buteneers
Adobe Champion
ilona_buteneersAdobe Champion
Adobe Champion
November 27, 2024

Hi @jiwonhe 

 

You're talking about modifying the existing Munchkin code. 

This is definitely a no go/ not possible. 

 

Please also read this article on the community about this topic for further info: https://nation.marketo.com/t5/knowledgebase/using-muchkin-id-on-multiple-domains/ta-p/252313. 

 

In addition to the article, please also have a look at this article for a possible workaround. https://trackfunnels.com/cross-domain-tracking-for-marketo-with-munchkin-code 

 

I see also @darshil_shah1 wrote an article about this topic, so maybe he can help out: https://purplemeup.substack.com/p/understanding-munchkin-cookies-tracking

 

Good luck, 

Ilona 

SanfordWhiteman
SanfordWhiteman
Level 10
November 27, 2024

In addition to the article, please also have a look at this article for a possible workaround. https://trackfunnels.com/cross-domain-tracking-for-marketo-with-munchkin-code 

Wow! is there a remarkable amount of misinformation in that article.

 

Referring to trivially reversed encoding as “encrypting” the cookie value “to ensure security”, for one... or another, using setTimeout() guesswork to check if Munchkin has loaded when you can listen for that event with 100% accuracy... and so on. 

 

IMO it‘d be pretty reckless to follow the recommendations there given the technical misunderstandings.

SanfordWhiteman
SanfordWhiteman
Level 10
November 27, 2024

You don’t need to tell Munchkin about your domains in advance. For example: www.site.example can load your Munchkin code, even if you send emails from user@mail.example and your Landing Pages are under pages.marketing.example. 

  

The Visit Web Page and Clicked Link on Web Page activities contain the URL so you can distinguish the activities. Try it!

 

P.S. @ilona_buteneers’s response assumed you mean sharing the tracking cookie across a totally different HTTP origin which is a whole other question. 

J
jiwonheAuthor
Level 2
November 28, 2024

Hello, Sanford Whiteman


Well, there seems to be a misunderstanding.
Actually @ilona_buteneers' response is more like an answer to what I was wondering.

I won't send emails using a completely new domain that is different from the existing domain. So, the web tracking and cookie setting in the new domain is more interesting than the answer you mentioned.

And you said "https://trackfunnels.com/cross-domain-tracking-for-marketo-with-munchkin-code " contains a lot of wrong information, so could you please share with me a site with the right information you know?

 

I always look forward to your help.
Thank you.

SanfordWhiteman
SanfordWhiteman
Level 10
November 28, 2024

I won't send emails using a completely new domain that is different from the existing domain. So, the web tracking and cookie setting in the new domain is more interesting than the answer you mentioned.

You mean “want [to] send” or “won’t send”? Not clear what you’re attempting to do.

 

Tracking Visit Web Page and Clicked Link on Web Page on Domain B is as simple as deploying Munchkin on Domain B. Clicking a tracked link in a Marketo email will automatically associate the person’s Munchkin web session, just as it does on Domain A.

 

What, other than that, are you trying to accomplish? Please provide complete details of the expected behavior.

Terms & ConditionsAccessibility statement

Loading footer...