Home/ Questions/Q 6189727
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T02:27:51+00:00

Ok first of all, i have the new code, the one that is put

  • 0

Ok first of all, i have the “new” code, the one that is put just before the </head> tag 

<script type='text/javascript'>

var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-#*$!#*$!xx-x']);
_gaq.push(['_trackPageview']);

(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();

</script>

The application that uses this code has 5 pages.
I have put this code in 3 of them (the first 2 and the last one).
The last page send me an email about what the visitor wants from our site(a form filled by him actually).
In the last 5 days i received 5 such emails/requests.
But google analytics only show 1 visit in that page.

Any reason as to why? I dont know how accurate google is for the first two pages, but i know for sure how much trafic/vistis my exit/thank you/email page has.
So, what’s wrong and what should i check?
Or it’s just a google glitch?

EDIT:
finally it works. Ignore google’s new code. Stick to old code at end of page, before the </body>.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Google Analytics (GA) can fail to get an accurate count for any number of reasons:

    • Javascript is turned off
    • User has blocked GA
    • A Javascript error in codes before the GA codes prevents it from running
    • The GA code is at the bottom of the page and that part is not loaded because
      • The user left the page before it could finish loading
      • A blocking event (e.g., another Javascript) timed out before the GA could run
      • An error on the page prevented the browser from loading GA
    • GA itself failed to record the data for whatever reason
    • A caching proxy server mangled the page so the GA code was not included or was broken1
    • Network error
    • Browser error

    If you want truly accurate visitor information, you need to look at your web server(s) logs, and even then you won’t always get it due to caching (local, proxy, etc).

    Try this

    <body>
 <div>
  <img src="/images/top.gif" height="1" width="1" alt="" />
 </div>

 ...[page content]...

 <div>
  <img src="/images/bottom.gif" height="1" width="1" alt="" />
 </div>
</body>
</html>
    1. Put web bugs (1×1 transparent images) on your page, one at right after <body> and one just before </body>.
    2. Examine your server logs to determine the percentage of people who successfully load the entire page (each top-bug’s entry matches a botom-bug entry in the logs)
    3. Calculate the page load time between top and bottom bugs.

    This will give you a good idea of what is going on with your pages and whether people are even loading each one in its entirety.

    1 I’ve actually witnessed this on more than one occasion.

    • 0