Landing page tracking twice | Community
Skip to main content
A
Anonymous
August 16, 2017
Solved

Landing page tracking twice

  • August 16, 2017
  • 1 reply
  • 4091 views

I have built a custom HTML landing page with a Marketo Form. I left the templates default setting of allowing Munchkin tracking. When viewing an instance of this template, it is tracking two views for a single view of the page. I went back into the editing the template and disabled the Munchkin tracking, approved it, went back to the instance of the template, approved its new draft (created from updating the template), approved it, and viewed the page again. Even after disabling the tracking, it still showed two additional views after I viewed the page once. I have viewed the page in Incognito mode of my primary browser (Chrome), I also viewed it in Firefox and IE11. One time it actually showed three additional views for a single view.

Any ideas?

Edit: When I have set Munchkin tracking to be disabled at the template level (the only place that you appear to be able to control this), it tracks 1 view per single page view (correct on the count). When I have tracking enabled, it tracks 2 views per single page view.

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

Just as a reference, I have been looking at "Statistics: 69 Views, 3 Filled out Form (4%)" in the instance of the landing page settings under the Design Studio (where you have Status, Type, Editing Mode, Statistics, Template, Form, Redirect Rule, URL). Are those stats not correct or not the right place to be reviewing the stats of the landing page?

Thank you for your assistance.


Just as a reference, I have been looking at "Statistics: 69 Views, 3 Filled out Form (4%)" in the instance of the landing page settings under the Design Studio (where you have Status, Type, Editing Mode, Statistics, Template, Form, Redirect Rule, URL). Are those stats not correct or not the right place to be reviewing the stats of the landing page?

You don't want to be using those Views because they count all HTTP-level GETs of the Landing Page, which is to say, a superset (sometimes a vast superset) of the true user-interactive pageviews that are logged by Munchkin, the JS-based web analytics library. Those Views include bots and any other user agent context requesting the page.

In other words, those Views aren't Munchkin views, they're more like pure web log lines, which are, if not necessarily useless, merely directional about the amount of traffic seen by a page.

You should use a Web Page Activity report to get accurate stats.

But what's interesting about you peeking in this other area is that it highlights an error in your code.

Look at this CSS rule in one of your inline <styles>:

Using an empty string as the background-image causes an extra GET of the current document. That's where your extra pageview is coming from. Remember, an empty string and background-image: none aren't the same!

1 reply

SanfordWhiteman
SanfordWhiteman
New Participant
August 16, 2017

Doesn't make much sense.

Are you deploying this page in an IFRAME?

Please provide the URL so we can troubleshoot.

A
Anonymous
August 16, 2017

argus metals

No iframe. This is using the Marketo system to create a landing page from custom HTML.

SanfordWhiteman
SanfordWhiteman
New Participant
August 16, 2017
  1. Def'ly should not troubleshoot LPs using a *.marketo.com hostname as this absolutely leads to unexpected Munchkin behavior. You should always test using your custom LP domain. Not to say that explains that particular issue, but we need to uncomplicate testing.
  2. Please show me a page where you don't have tracking turned off on the template, and have not made any other changes on the derived LP.
  3. Are you positive you have not pasted Munchkin.init() into your HTML, at the base of the <body>?
  4. Even repeated calls to init() with the same parameters don't result in multiple Visit Web Page events (Munchkin controls for this error) so something else is going on besides simply ​init()ing twice.
Terms & ConditionsAccessibility statement

Loading footer...