Announcement

Collapse
No announcement yet.

Analytics SSL woes!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Analytics SSL woes!

    Oh no, not another Google analytics thread I hear you cry!

    Not at all. I have copied all the code into the right templates and all is well, except for when visitors arrive at the secure ordering form and a warning appears regarding the unsecure item. Does anybody know how to overcome this, do I just add an s into the http tracking code url and if so into which template?

    I've searched the forum in vain and would be very gratefull for any ideas.

    Regards, Robert
    Robert Johnston
    www.gentlemans-shop.com

    #2
    Robert
    Hi, I would be very interested to hear exactly what and where you have added the code. I know it is long winded but I have been unable to find a conclusive answer on any threads regarding converrsion and e-commerce analytics.
    Regards
    K

    PS - Sorry I cannot help you with an answer


    www.testrightnow.co.uk

    Comment


      #3
      Hi Robert,

      You can change the URL to https:// on Act_PrimaryCheckout.html and see how it works.

      Comment


        #4
        Hi Robert,

        Originally posted by sumiya
        Hi Robert,

        You can change the URL to https:// on Act_PrimaryCheckout.html and see how it works.
        Did this work? If so how did you do it?

        Thanks
        Percentage Golf
        Booksand.info

        Comment


          #5
          I have taken the code out from the checkout as this happens to me and it puts customers off as not only does it show a "contains secure / non secure items" message box but also prevents the padlock symbol showing.

          Changing the script to https does not work either as googles SSL cert is not for the analytics domain name

          I am going to download the script and upload it to my own site later today to see if this works.

          Comment


            #6
            Originally posted by sumiya
            Hi Robert,

            You can change the URL to https:// on Act_PrimaryCheckout.html and see how it works.
            Hi Sumiya,

            That would have been too easy! Surely I am not the only one that has this problem on the secure checkout...

            Regards, Robert
            Robert Johnston
            www.gentlemans-shop.com

            Comment


              #7
              Hi Robert,

              I'm looking into this. I will getback to you at the earliest.

              Comment


                #8
                Originally posted by sumiya
                Hi Robert,

                I'm looking into this. I will getback to you at the earliest.
                Thank you, Robert
                Robert Johnston
                www.gentlemans-shop.com

                Comment


                  #9
                  Hi Robert,

                  If your site includes secure web pages using the HTTPS protocol, you'll need to make sure that your tracking code is tailored for secure access. If your Website URL includes https, your tracking code will already be customized for secure pages. Otherwise, you'll need to update this value for your profile.

                  To obtain Google Analytics tracking code that is tailored to secure (HTTPS) web pages:

                  1. Log in to Google Analytics
                  2. Find the profile for which you are obtaining tracking code and click Edit
                  3. In the Main Website Profile Information bar, click Edit
                  4. Edit the Website URL field by specifying https:// rather than http://
                  5. Click Save Changes

                  To obtain the secure tracking code, click the Check Status link above the Main Website Profile Information bar. Your tracking code will be customized for secure pages and will look like the example below:

                  <script src=" https://ssl.google-analytics.com/urchin.js"
                  type="text/javascript">
                  </script>
                  <script type="text/javascript">
                  _uacct = "UA-XXXXX-X";
                  urchinTracker();
                  </script>

                  You can add this secure code to both secure and non-secure pages of your site.

                  Comment


                    #10
                    Originally posted by sumiya
                    Hi Robert,

                    If your site includes secure web pages using the HTTPS protocol, you'll need to make sure that your tracking code is tailored for secure access. If your Website URL includes https, your tracking code will already be customized for secure pages. Otherwise, you'll need to update this value for your profile.

                    To obtain Google Analytics tracking code that is tailored to secure (HTTPS) web pages:

                    1. Log in to Google Analytics
                    2. Find the profile for which you are obtaining tracking code and click Edit
                    3. In the Main Website Profile Information bar, click Edit
                    4. Edit the Website URL field by specifying https:// rather than http://
                    5. Click Save Changes

                    To obtain the secure tracking code, click the Check Status link above the Main Website Profile Information bar. Your tracking code will be customized for secure pages and will look like the example below:

                    <script src=" https://ssl.google-analytics.com/urchin.js"
                    type="text/javascript">
                    </script>
                    <script type="text/javascript">
                    _uacct = "UA-XXXXX-X";
                    urchinTracker();
                    </script>

                    You can add this secure code to both secure and non-secure pages of your site.
                    This worked first time, fantastic.

                    Thank you for all your help.

                    Robert
                    Robert Johnston
                    www.gentlemans-shop.com

                    Comment


                      #11
                      thanks

                      well that gets rid of the security warning i was getting - nice of you to take the time to help out numpties like me.

                      Comment

                      Working...
                      X