1 Reply Latest reply on May 2, 2013 1:40 PM by 2039

    Tracking Cookies

      The marketo tracking cookie is crossing over to our other web properties on sub-domains in which we do not have the tracking code installed.  For example, we have the marketo tracking installed on www.ezlynx.com.  However, our application often uses auto.ezlynx.com and other sub-domains.  We do not want the marketo cookie to be tracking user data from these locations, but our IT guys have reported that it is.
      Our question is this, is there a way within the tracking code that we can say to marketo “ignore these sub-domains: [list]” and the cookie will not track those locations?
      The reason is that browsers have a cookie limit for any given website.  Only a set number of cookies can be active for any particular web page.  Our product uses cookies extensively to maintain its functionality.  It is apparently causing problems because the marketo cookie is also loaded up, even though the user, while on *.ezlynx.com, is not on any page that has the actual marketo javascript tracking code installed
        • Re: Tracking Cookies
          Hi Andrew,

          To be clear, we only track on domains where the Munchkin Javascript is on the page. However, our tracking script does place a 1st party cookie within that domain. That same cookie would be visible on all your subdomains because it is still a cookie set in that namespace.

          Unfortunately it isn't possible (in any way I can envision) to have the cookie be a first party cookie at the top level which also includes subdomains (by design) and not have it also exist in your other subdomains.