4 Replies Latest reply on Apr 1, 2010 2:51 PM by karina1717

    Why is Google Analytics not working?

    karina1717

      Can someone take a look at my code here and teel me why Google analytics isn't recording any data?

       

      http://www.hopropertymanagement.com/

       

      If someone can help it would be really appreciated!

        • 2. Re: Why is Google Analytics not working?
          Nancy OShea Adobe Community Professional & MVP

          Once you've correctly installed your tracking code, you should allow  up to 24 hours for data to appear in your account.

          If it has been more than 24 hours since you installed the tracking  code and you're still not seeing any data, take a look at the list of  possible reasons below.

           

          • Incorrect tracking code
            The most common reason why you're not seeing any data in your reports is  because of an error in the Analytics tracking code. Copying the  tracking code from your account to a word processor may add an extra  space or change the quotation marks in the tracking code by the time you  paste it to your website. We suggest copying the code again and pasting  it directly onto your website.

          • The Google Analytics tracking code is account- and profile- specific, so  verify that the tracking code installed on your website matches the  code shown in the account.
            Click here to view a video on how to check for the correct  tracking code
          • Incorrect filter settings
            Incorrect filter settings can affect the data you see, and may  unintentionally filter all of your data from your reports. This happens  most frequently due to multiple Include filters.

          • Viewing Incorrect Account
            If you have access to multiple Analytics accounts, you may be looking at  the wrong account. Please use the 'My Accounts' drop-down menu at the  top right of the screen to sele the account you'd like to view.

          • Using both Urchin software and Google Analytics
            If you are using Urchin software in addition to Google Analytics to  track your website, you may have both __utm.js and ga.js referenced from  your pages. You'll need to update your pages to use the correct code.

          • Using an Outdated Version of ga.js
            If you are hosting the ga.js file locally, you may be using an outdated  version of this file. You can download the most up-to-date version at http://www.google.com/analytics (click the "Check Status" link on the Analytics Settings page to find the new code), but we recommend that you let Google host  this file, as this ensures you have the most current version of the  file.
          • Interfering Scripts
            Other scripts on your pages could be using some of the same variables as  the ga.js file, and therefore interfering with the tracking code  execution. If you're using additional scripts on your pages, consider  moving the tracking code into the <head> section of the page. This  way, the tracking code will work correctly, and it won't interfere with  the rest of your scripts.

           

          Nancy O.
          Alt-Web Design & Publishing
          Web | Graphics | Print | Media  Specialists
          http://alt-web.com/
          http://twitter.com/altweb
          http://alt-web.blogspot.com

          • 3. Re: Why is Google Analytics not working?
            370H55V Level 4

            Also be 100% sure you have uploaded the robots.txt file to your root directory. GA looks for it when they make their initial check.

             

            And http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.hopropertymanagement.com%2F shows several metadata errors in your header.

             

            1. Error Line 9, Column 37:         end tag for "meta" omitted, but OMITTAG NO was  specified
              <meta name="city" content="Seattle">

              You may have neglected to close an element, or perhaps you meant  to        "self-close" an element, that is, ending it with "/>" instead  of ">".

            2. Info Line 9, Column 1:         start tag was here
              <meta name="city" content="Seattle">
            3. Error Line 10, Column 33:         end tag for "meta" omitted, but OMITTAG NO was  specified
              <meta name="State" content="WA">

              You may have neglected to close an element, or perhaps you meant  to        "self-close" an element, that is, ending it with "/>" instead  of ">".

            4. Info Line 10, Column 1:         start tag was here
              <meta name="State" content="WA">
            5. Error Line 11, Column 46:         end tag for "meta" omitted, but OMITTAG NO was  specified
              <meta name="country" content="United States">

              You may have neglected to close an element, or perhaps you meant  to        "self-close" an element, that is, ending it with "/>" instead  of ">".

            6. Info Line 11, Column 1:         start tag was here
              <meta name="country" content="United States">
            7. Error Line 153, Column 18:         there is no attribute "src"
                    <embed src="Property Mangement.swf" quality="high" pluginspage="http://ww…

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            8. Error Line 153, Column 51:         there is no attribute "quality"
              … src="Property Mangement.swf" quality="high" pluginspage="http://www.adobe.com…

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            9. Error Line 153, Column 70:         there is no attribute "pluginspage"
              …ement.swf" quality="high" pluginspage="http://www.adobe.com/shockwave/download…

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            10. Error Line 153, Column 161:         there is no attribute "type"
              …?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="4…

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            11. Error Line 153, Column 199:         there is no attribute "width"
              …veFlash" type="application/x-shockwave-flash" width="420" height="325"></embed>

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            12. Error Line 153, Column 212:         there is no attribute "height"
              …veFlash" type="application/x-shockwave-flash" width="420" height="325"></embed>

              You have used the attribute named above in your document, but the       document type you are using does not support that attribute for  this       element. This error is often caused by incorrect use of the  "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute),  or       by using vendor proprietary extensions such as "marginheight"  (this       is usually fixed by using CSS to achieve the desired effect  instead).

              This error may also result if the element itself is not supported  in       the document type you are using, as an undefined element will have  no       supported attributes; in this case, see the element-undefined  error       message for further information.

              How to fix: check the spelling and case of the element and  attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type,  and/or       use CSS instead of this attribute. If you received this error when  using the        <embed> element to incorporate flash media in a Web page,  see the        FAQ  item on valid flash.

            13. Error Line 153, Column 217:         element "embed" undefined
              …veFlash" type="application/x-shockwave-flash" width="420" height="325"></embed>

              You have used the element named above in your document, but the       document type you are using does not define an element of that  name.       This error is often caused by:

              • incorrect use of the "Strict" document type with a document  that        uses frames (e.g. you must use the "Frameset" document type to get         the "<frameset>" element),
              • by using vendor proprietary extensions such as  "<spacer>"       or "<marquee>" (this is usually fixed by using CSS to  achieve       the desired effect instead).
              • by using upper-case tags in XHTML (in XHTML attributes and  elements       must be all lower-case).
            14. Error Line 142, Column 7:         Opening and ending tag mismatch: meta line 11  and head
              </head>

            15. Error Line 204, Column 7:         Opening and ending tag mismatch: meta line 10  and html
              </html>

            16. Error Line 204, Column 7:         Premature end of data in tag meta line 9
              </html>

            17. Error Line 204, Column 7:         Premature end of data in tag head line 3
              </html>

            18. Error Line 204, Column 7:         Premature end of data in tag html line 2
              </html>
            • 4. Re: Why is Google Analytics not working?
              karina1717 Level 1

              Thanks everyone, it's working now