Skip to main content
A
Anonymous
March 21, 2016
Question

Munchkin Reliability

  • March 21, 2016
  • 1 reply
  • 2801 views

Hi Everyone,

Has anyone had any issues with the munchkin API? We're seeing about 12% of leads not making it across to the lead database when using associate lead. This has been very difficult for us to debug as it's all clientside (could be conflicts with our other scripts in particular browsers?). We use a catchup job on the server to synch any missing leads.

On another note, if we were to switch to the SOAP API, is there a way to associate the tracking cookie from the server response? We used the munchkin API initially because it gave us the tracking cookie for logging page visits and link clicks. If we could use the server side API for creating the lead, at least we would know if succeeded or failed.

Edit: I noticed there is a munchkin cookie on the docs, but how do you get that ID?

syncLead » Marketo Developers

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

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
March 21, 2016

Do not switch from the Munchkin API.  You will introduce a Denial of Service attack vector against your instance.  You'll be trading a troubleshooting task for guaranteed failure.

As for Munchkin, I wouldn't look into conflicts with other scripts per se.  But conflicts with other script-based navigation, absolutely.  Can you please point me to a page where you're doing this?  A lot of people don't understand the JS race condition that's in play when you rely on background Ajax tasks.  I also have a Munchkin adapter script that can make Munchkin astronomically more accurate in late-model browsers (although it is designed to help with page activity events like Visit Web Page and Click Link, it assists ​Associate Lead as well).

Grégoire_Miche2
Grégoire_Miche2
Level 10
March 21, 2016

Hi Sanford,

Could it be another consequence of the domainlevel bug that we discussed a couple of months ago?

-Greg

SanfordWhiteman
SanfordWhiteman
Level 10
March 21, 2016

Unlikely to be a direct cause since the bug causes the cookie to be (successfully) set a level lower than appropriate, rather than failing to be set at a higher level.  But certainly part of the troubleshooting should be whether a cookie exists.

Terms & ConditionsAccessibility statement

Loading footer...