Adding Munchkin to a Wix website

SanfordWhiteman
Level 10 - Community Moderator
Level 10 - Community Moderator

Adding Munchkin to a Wix website

Either I was a bit overconfident in this Marketo Community Post from over a year ago about Munchkin & Wix, or Wix has changed something since. (Can't track changes on their side, not being a real Wix user myself.) Either way, as of Spring '16, Wix makes you jump through a few hoops. But Munchkin tracking can be done! I don't think this recipe is available anywhere else on the web, so let's dig in.

The problem: Custom HTML is wrapped in IFRAMEs

Unlike other "prosumer" site builders such as SquareSpace, Wix seems deathly afraid of letting you add custom HTML (including JS) directly to your managed pages. Instead, any HTML you add using the Add More » HTML Code is always wrapped in an IFRAME before insertion.

Read the full post on TEKNKL :: Blog →

1806
3
3 Comments
Jo_Pitts1
Level 10 - Community Advisor

@SanfordWhiteman ,

I've followed the guide on your blog.  As always, very helpful.

When I look at the page source of the Wix site in question, I can't see anything related to the injector code, or munchkin code.  How (within the Wix context) can I prove the code is loaded.

Also, on this page https://support.wix.com/en/article/wix-editor-adding-code-to-your-site I see reference to Tracking Tools & Analytics.  Should we now be using that function to add in Munchkin code?

 

Cheers

Jo

SanfordWhiteman
Level 10 - Community Moderator

IIRC, Wix improved capabilities so you can use the Tracking Tools section instead of something more elaborate.

Jo_Pitts1
Level 10 - Community Advisor

@SanfordWhiteman , that is exactly what they did.  This gives a couple of options.  Embed Munchkin through there, or GTM (if you are also embedding that).  I've gone the direct route.

 

In a remarkable lack of SEO if you google 'munchkin wix' or 'marketo wix' their own help pages don't appear meaning the post here referring to your blog is still the first reference that comes up.

 

It might pay to update your blog to reference the slightly historical nature of the solution and point to the 'easy way' (although the whole communicating from inside the iFrame to outside the iFrame was super interesting).

 

Cheers