Google Analytics session breaking between secure and insecure LO domains

Options
Hello Luminate Analytics Community.


We have a client who is using the default Luminate Online/Google Analytics integration, but they're losing their GA session (and proper referral sources) when they move from their insecure LO domain to their secure LO domain.


This is happening regardless of whether the user is clicking a link to a secure page from an insecure page or if LO pushes the user from the insecure domain to the secure domain.


Is this simply the "cost" of using the default LO/GA integration or might there be a workaround to help maintain the GA session throughout their visit that is not "disable the default integration and rebuild everything yourself using proper cross-domain tracking techniques?"


Thank you in advance for your thoughts.


Adam

Tagged:

Comments

  • Hi Adam -


    The short answer is yes - the traffic from http to https (and vice versa) from the same UA-ID can use loose referrer information. You can check easily using developer tools and console "document.referrer' as you navigate around.


    Regardless of secure vs non-secure, LO is not set up for any sort of cross-domain tracking with Classic or Universal Analytics, so anyone running multpile systems not on the same primary domain shouldn't use the Google Analytics SDPs - ex: www.nptech.org as some CMS, nonsecure.nptech.org as non-secure LO and secure.nptech.org as secure LO.


    There is a larger referrer issue with CMS (convio.referrer), but I won't get into that here.

  • Thank you very much for your response, Sara.


    I hope that you're well.


    Adam

Categories