Munchkin code for the different 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.

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...

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.