SOLVED
1 ACCEPTED SOLUTION
Accepted Solutions
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!
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!
.png)