![wix add html code without iframe wix add html code without iframe](https://support.glofox.com/hc/article_attachments/360009193978/wix-add-code.png)
Which isn't so bad - you could use a Contains in a Smart List and do pretty well with this. I won't detail it here since there's a complete solution below, but in all browsers but IE 8-9, you could coerce Munchkin into showing just the IFRAME's hostname but logging the pathname, querystring, and hash from the main doc. There's a crafty workaround for the problem of logging the IFRAME's URL as the visited URL. But the Referrer will change for each visit, and the Referrer can, to a degree, be used in Smart Lists. Since the IFRAME URL is the same on every page with Wix, Marketo sees repeated visits to the same URL. It'll pass the main document (the one your lead is actually looking at and which appears in the browser's location bar) as the Referrer of the Visit Web Page activity, but the URL of the Visit Web Page is the IFRAME's URL. When you simply load and init() Munchkin from inside an IFRAME, it sees the IFRAME's location - its URL and query string - as the current document.
![wix add html code without iframe wix add html code without iframe](https://www.wikitechy.com/step-by-step-html-tutorials/img/html-images/code-explanation-iframe-tag-in-html.png)
But it certainly can lower it to 99% from 99.9%.įar more negotiable are #1 and #2. Now, I'm not saying this is going to lower your accuracy below 99%. If you then load other scripts async and/or fetch tracking pixels via Ajax (like Munchkin does) that's just more stuff that may or may not finish loading before someone moves away from the main doc. When you put HTML in an IFRAME, the IFRAME's inner document is always loaded asynchronously, so that means the tags inside the IFRAME are, non-negotiably, fetched asynchronously relative to the main document. Those are essentially conflicting priorities: calling something important/mission-critical and treating that same thing as unimportant/disposable. This is the definition of background/async processing, and as I've written about a lot before, pushing analytics scripts deep into the background doesn't make sense if you simultaneously expect all your hits to be logged. The more levels of indirection + asychronous loading you add to a page, the more likely the user is to navigate away from the page before everything's finished. There's not much that can be done about #3.
![wix add html code without iframe wix add html code without iframe](https://www.cloudweblabs.com/wp-content/uploads/2019/12/1.png)
Click Link activities on the main page will not be logged.You'll log a Visit Web Page to the URL of the IFRAME, not the URL of the main page the person is looking at.If all you do is put the Munchkin embed code (whether you use Simple, as I usually advise, or one of the Async versions available in Marketo » Admin » Munchkin) in an IFRAME, here's what's going to happen: So what's the problem with loading Munchkin in an IFRAME, in general? Well, that depends on how much you can tweak your install, and how well you understand JS and the DOM (so non-developers aren't prepared to make it work perfectly). Like - huge hint - a subdomain of our Wix domain. There is one very helpful difference for our purposes, though: while the automatic IFRAME you get with HTML Code is loaded from one of Wix's internal domains (like, which is a subdomain of ), the IFRAME we can specify with Embed a Site can load from anywhere we want. (Note: Embed a Site is the same as choosing HTML Code, then switching to the Website Address option in the popup - aliases for the same action.) They both end up adding an IFRAME, it's just that in the first case, the IFRAME is created automatically to wrap your code (without warning you!). Therefore HTML Code isn't so different from the more explicit Add More » Embed a Site.
![wix add html code without iframe wix add html code without iframe](https://docs.edoobox.com/wp-content/uploads/sites/2/2017/04/Wix-Code-1.png)
Instead, any HTML you add using the Add More » HTML Code is always wrapped in an IFRAME before insertion. 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. The problem: Custom HTML is wrapped in IFRAMEs But Munchkin tracking can be done! I don't think this recipe is available anywhere else on the web, so let's dig in. (Can't track changes on their side, not being a real Wix user myself.)Įither way, as of Spring '16, Wix makes you jump through a few hoops. ← TEKNKL :: Blog Adding Munchkin to a Wix websiteĮither I was a bit overconfident in this Marketo Community post from over a year ago about Munchkin & Wix, or Wix has changed something since.