Munchkin Code via Google Tag Manager not firing

[Nikki_Aurelio]

Hello - looking for advise from anyone who has their munchkin code implemented on their external website via Google Tag Manager.

We previously had our munchkin code embedded in the individual pages of our website, but recently made a switch to host it in Tag Manager; however, the tags don't seem to be firing and the web activity is not tracking.

Followed these instructions (that are likely out of date): http://developers.marketo.com/blog/integrating-munchkin-with-google-tag-manager/

Appreciate any advise on why this might not be working / what I need to change in our setup.

Here is our tag configuration in Google Tag Manager (used our asynchronous tracking code type):

And here is what it is saying about firing on our site:

[SanfordWhiteman]

You'll need to provide a sample URL.

Also note that -- although running via GTM is not advised -- if you do use GTM there's no reason to use the full-async Munchkin bootstrap (Munch is at least 1/2 async in all cases, since the library is loaded async by the bootstrap).  Everything you load via GTM is async, and you're just adding another layer of indirection.

[Nikki_Aurelio]

Sorry about that - here is our homepage: http://www.fieldglass.com/

I didn't realize running via GTM was not advised...

[SanfordWhiteman]

The page is firing Munchkin activities:

What are you actually doing to test this within Marketo?

[Hobie_Thompson1]

One thought - have you gone into the template and clicked 'Disable Munchkin Tracking'? It's possible that, based on how GTM is firing, that Munchkin is initializing through Marketo's script before GTM.

[SanfordWhiteman]

One thought - have you gone into the template and clicked 'Disable Munchkin Tracking'? It's possible that, based on how GTM is firing, that Munchkin is initializing through Marketo's script before GTM.

That wouldn't cause Munchkin to not fire, though.  Like the Forms2 library, Munchkin is smart enough to not load twice (it looks for an existing global object). You're right though, it should be enabled in one place -- to not duplicate network requests if nothing else.

Anyway the report is rather strange b/c the page is sending Munch activities, it's plain to see...

[Dan_Stevens_]

Sanford has provided some really good insight in many posts within the community that talks about why it's not advised and the risks associated with it.  That being said, for large, global organizations with web pages in the tens of thousands, companies like ourselves feel the benefits of GTM for managing all of our tags/scripts outweigh the risks.  As for Munchkin, I believe it's a very small percentage where Munchkin may not fire (< 1%).  Just be sure to disable this on your Marketo LPs since Marketo adds Munchkin automatically to these LPs.  So for example, on Marketo LPs, our GTM is setup to only serve Google Analytics and DemandBase scripts.

[Mehul_Bhadani]

I went through the thread. Our case is a bit different where the tag fires but the web page activity did not show any data. If we go with GTM, you mentioned not to use GTM and if we use, since the GTM is async there's no reason to use the full-async Munchkin bootstrap. Which of the below do you recommend to use in case of GTM?

Thanks,

Mehul