Marketo Munchkin Code Tracking Issue

Hey @edang03,

You’ll need to provide a bit more information in order for the community to be able to help you.

1. Which version of the code are you using? (synchronous, asynchronous w/ jQuery, asynchronous w/o jQuery)

2. How are you firing it (directly on the page or through a tag manager like GTM)?

3. How do you know it’s not firing at all?

The more information you can provide, the better answer you are going to get.

Best,
Hristian

Hi @edang03,

Couple of things you need to check:

[1] Make sure you are loading jQuery for your Unbounce page(s). It’s a little checkbox on the left hand side of your JS script editor inside the page builder.

1.1 If you do have jQuery on your landing pages:

1.2 Make sure it loads before the munchkin script

1.3 Make sure the jQuery version is sufficient for the munchkin script needs (You might need a newer version).

[2] Test loading the munchkin code w/ jQuery (the one Marketo provides). If that solves the problem than most likely, one of the points above is your problem.

Best,
Hristian

So here is what I discovered, as a new lead, completing a form on Unbounce with the Marketo Munchkin Code embedded, it doesn’t cookie the lead. I had to complete a form on a Marketo landing page in order to cookie my browser. After that I visited Unbounce landing pages and could see my activity in Marketo, but as far as placing a cookie on leads generated from Unbounce landing pages, the Marketo Munchkin code doesn’t seem to be working.

Marketo users need Munchkin Code and Unbounce Forms to play happy and allow for progressing profiling. That would make me an extremely happy Marketo user.

Hi @acodyjr, @edang03 and @Jennifer_Rothrock,

I’m assuming most of you are using the default munchkin snippet and depending on your particular use case, it might need to be adjusted.

In order to troubleshoot this, you need to:

1. Check whether the munchkin snippet has the correct placement.

2. Whether the snippet is firing correctly.

3. What cookies are being created or for that matter not being created. If a cookie is not being created, try to figure out why that is the case. Cross-domain issues? Top level domains with just 2 letters (.jp) or co.uk?

4. Check to see whether you might have some kind of DDoS protection in place that stops outgoing calls to external APIs.

These are just a few things that come to mind without actually seeing any of your pages.

In regards to using GTM… The main benefit is that you have a single place to insert and control your scripts. Set firing rules. Insert necessary scripts across 1, 10 or 1000 pages. If you need to change something in a script, you do it once and it’s applied across however many pages you need/want.

Last but not least… can you elaborate on your notes about Unbounce form playing nicely with Marketo? Are you referring to the native Unbounce integration that pushes form data to Marketo?

If you are referring to associating anonymous to known leads… This needs to happen with an API call to Marketo.

Feel free to reach out in a direct message if you need more help.

Best,
Hristian

Just like @edang03, the tracking works on the Unbounce pages if the lead is already known, having been captured elsewhere. Capturing the new lead in Unbounce and sending the data to Marketo is also fine.

It’s when a new lead is captured, for whatever reason, the lead still isn’t known to Marketo, losing our ability to track their movements around our web properties. With lead scoring in place as well as some other automation to pick up certain movements, this severely hinders our workflow and benefits of Marketo.

This is a really useful support thread that has larger implications beyond the original question. @edang03 asked about progressive profiling, that is one big example. @Hristian, if we have things set up as outlined above, what it limiting the usage of progressive profiling w/Marketo integration?