Out of hundreds of transactions tracked recently using GA Ecommerce tracking, they're all showing a traffic source of Direct, and none of them are showing google organic (or any other traffic sources) as contributing any revenue.

From some quick testing, it appears that the traffic source is dropped when the customer switches from http over to https in the checkout process.

Any good solutions for this?

UPDATE: It looks like this may have been being caused by a duplicate snippet with a difference in the placement of the setDomainName line in the snippet. No longer seeing the traffic source being dropped in GA Debugger in the checkout step, going to wait a day and see whether data begins to show up properly in reports.

  • Are you using the default magento GA module? If so what version of magento do you have installed? – Renon Stewart May 30 '13 at 18:39
  • Yes, default GA module. I'm on EE Do you not see this happen? – kalenjordan May 30 '13 at 19:01
  • Are you sure this isn't dropping querystring when redirecting from http://domain.com to http://www.domain.com? – philwinkle May 30 '13 at 20:41
  • Don't think so. I was on www.domain after arriving from google, and I saw the campaign source tracking going through just fine for several page views, it wasn't until the checkout that the traffic source was dropped. – kalenjordan Jun 3 '13 at 22:21
  • I'm glad that this has come back up - I forgot to check back on this thread. This isn't correct behavior - I suspect something else is amiss. I checked stock Magento, stock GA module, HTTPS enabled, and no loss of campaign source was detected in GA. – philwinkle Jun 3 '13 at 22:40

Turns out that I had some a duplicate GA snippet hiding out that was causing this. Traffic source should not get dropped when the customer goes from http to https in the normal course of usage.

Big shout out to my boys Fabian and Phil for the help troubleshooting.

| improve this answer | |

There is a good and easy way to solve this problem:


The customers data are worth to be protected and https is not anymore a performance problem with modern CPUs.

| improve this answer | |
  • +1 Yes I was suspecting that might be the answer. What happens though if someone is referred to the site from a non-https connection? Does the referral get lost in that case? – kalenjordan May 30 '13 at 20:36
  • good question. If you redirect him I think yes, because the JS is not executed and after the redirect it is gone. But I don'T have a solution at the moment. – Fabian Blechschmidt May 30 '13 at 20:39
  • I personally hate this idea. This has caching and 3rd-party javascript include impact. – philwinkle May 30 '13 at 20:40
  • What do you mean with caching? And Javascript should be no problem too, why should it? blog.httpwatch.com/2009/01/15/https-performance-tuning and blog.httpwatch.com/2011/01/28/top-7-myths-about-https – Fabian Blechschmidt May 30 '13 at 20:50
  • 3rd parties don't always provide HTTPS - some I've encountered include Bazaarvoice, Bronto. Varnish doesn't handle https traffic. – philwinkle May 30 '13 at 20:58

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.