Multiple Munchkin Tracking Codes on a Single Page

Forum|Forum|9 years ago
August 30, 2016
2 replies
3789 views

We would like to place a form and add Munchkin code to a 3rd party page that already has Munchkin tracking from a different instance.

It appears this can be done using the altids parameter (source: Using Multiple Munchkin Tracking Codes on a Single Page ), however is there a way to turn off tracking of anonymous leads for just our instance while leaving the default instance as-is?

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

SanfordWhiteman

Level 10

Excellent question. AFAIK this would require a customized Munchkin implementation (not something to take lightly, but something we do occasionally). cookieAnon applies to all the altIds. What is the particular worry about having anonymous non-converting leads in your instance (considering that anonymous leads are now separate from the main database)?

A

Anonymous

The page we would like to implement secondary tracking on historically has a very high number of page views. I am not sure if this spike in anonymous lead tracking would affect system performance, but am hoping to prevent that.

The second need is to track multiple forms with the same form ID on a single page. I have read through your past posts on the matter, but I am not a developer so it is still not clear to me if that would be possible if we decide not to track our Marketo instance on the page. Does that make a difference?

SanfordWhiteman

Level 10

The page we would like to implement secondary tracking on historically has a very high number of page views. I am not sure if this spike in anonymous lead tracking would affect system performance, but am hoping to prevent that.

That's quite reasonable. Adding your Munchkin code to a high-traffic site directly affects your instance, and if you don't need the anonymous data it is best avoided.

The second need is to track multiple forms with the same form ID on a single page. I have read through your past posts on the matter, but I am not a developer so it is still not clear to me if that would be possible if we decide not to track our Marketo instance on the page. Does that make a difference?

If you don't supply your Munchkin ID and you don't cross-post anything to your own Instance B, you'll never know about the form post (regardless of whether you have the same form from Instance A rendered once or multiple times).

Ronen-Was-SRpro

Level 5

I’m not aware of a way to disable anonymous leads tracking, however since this is a different domain name I believe that you won’t be able to track anonymous leads at all as far as I know and I’ll try to explain why:

1. I have a customer with a few domain names
2. Sometimes they are anonymous in 1 domain and known in another, sometimes the opposite.
3. The only way to make them “known” is when they fill out a form or click a link in an email with their own token.
4. Only then – their information is being updated and they are known in the specific domain name they converted with, however for the other one – they keep anonymous.

I hope this helps, if not feel free to contact me directly

email: ronen@ronlinemarketing.com

mobile: 1-917-775-6516

Ronen Wasserman

SanfordWhiteman

Level 10

The Munchkin config option cookieAnon: false disables anonymous tracking, as I noted above.

Mollie's asking about sending hits to two Munchkin IDs (using the altIds config option for the second one) but having cookieAnon: true for one and cookieAnon: false for the other. Munchkin doesn't allow that granular config out-of-the-box.

The situation you're referring to is cross-domain tracking, which is by well-known to be hampered by the fact that cookies do not travel across different private domain suffixes. Different situation. Mollie's talking about tracking the altIds on a single domain (a single page, in fact).

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded