ga_tokenizer not working for google analytics 2.0?

Thank you for reporting the issue.

Believe it or not, GA Tokenizer is completely independent of the Google Analytics module (even though I made the GA module a dependency). GA_Tokenizer reads the cookie set by the Google Analytics javascript provided by Google. If you are seeing blank values, it would suggest that:
1. Google Analytics cookies are not being set at all -- perhaps the GA script is not being inserted into the rendered html?
2. Google might have changed the format of their cookie and those values are no longer present.

If it is #2, then I would expect to see a lot of tickets to be opened in the near future from everyone using GA.

Can you do a View Source on your web page to confirm that you see ga.js in the code and that no javascript errors are occurring? Chrome has a nice tool. Right click on a page an choose "Inspect Element" to see the developer console.

Peace,
Brian

I'm experiencing the same thing. Tokenizer is no longer working for me after upgrading to GA 2.0...

Actually, my apologies as I went through a bunch of settings on my set and it appears to have been a block caching issue on my end.

My understanding is that it's #2, per Brian's original follow-up questions. The new universal analytics script does not store Campaign, Source, etc etc in the user's cookie. Instead, they are using a remote database.

I've ran into this issue a lot this year with new GA scripts and especially Tag Manager. My current work-around is to use the old, deprecated version of GA (manually added, not via the module) along side the new version, using two different GA account numbers.

I have already upgraded my GA property to UA, so I don't know what my "old code" is. Can you provide an example? Thanks!

Hmm.. Old GA analytics code:

You can visit the google_analytics module page (https://www.drupal.org/project/google_analytics) and look at the old releases. You could probably pick it out from there. Sorry I can't be a little more helpful.. pressed for time at the moment, but wanted to try to give you a point in the right direction.

Thanks I was able to bring up my old site and get the code.

For anyone interested here is what it looks like:
<script>var _gaq = _gaq || [];_gaq.push(["_setAccount", "UA-XXXXXXX-Y"]);_gaq.push(["_setDomainName", "www.example.com"]);_gaq.push(["_trackPageview"]);(function() {var ga = document.createElement("script");ga.type = "text/javascript";ga.async = true;ga.src = ("https:" == document.location.protocol ? "https://" : "http://") + "stats.g.doubleclick.net/dc.js";var s = document.getElementsByTagName("script")[0];s.parentNode.insertBefore(ga, s);})();</script>

I put this code in the HEAD section of my theme html.tpl.php file. Is this right? It looks like it is working.

I thought I'd give some insight to future people trying to figure this issue out. I've worked out an alternative that checks utm_parameters and/or attempts to infer source&medium from HTTP_REFERER. It saves it all in a cookie to be used in tokens. It's undeniably not as good.

There's a couple other alternatives around, such as this one:
https://github.com/dm-guy/utm-alternative/

Very similar solution, although js-based. In both cases, inferring source and medium can be tricky (What you would previously see as organic/direct/referral/cpc). Referrals from HTTPS sites like facebook and twitter are very problematic because HTTPS sites do not transfer HTTP_REFERER information.

Installing Universal and regular analytics still works, at least for now (who knows when support for ga.js will be dropped)
http://stackoverflow.com/questions/18604715/google-analytics-missing-utm...

I put in the utm-alternative approach, but found there would be a lot of extra work to get that setup working properly with all the other token modules that coincide with this module.

I ended up putting the following code on my site, I do have to check to see if its going to double my traffic, but hopefully not.
Once this was on the site things started to work properly. I now run the google_analytics module (universal) and have this snippet running for tracking purposes.
Please note that I grabbed the __utm.gif file from google as well and stored in my theme. I believe this is just a blank.gif file.

  <script>
    var _gaq = _gaq || [];
    _gaq.push(['_setAccount', "UA-XXXXXXXX-X"]);
    _gaq.push(['_setDomainName', "SITENAME.com"]);
    _gaq.push(['_setAllowAnchor', true]);
    _gaq.push(['_setLocalGifPath', "http://PATHTOTHEME/images/__utm.gif"]);
    _gaq.push(['_setLocalServerMode']);
    _gaq.push(['_trackPageview']);
    (function() {
        var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
        ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
        var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
    })();
  </script>

I created a quick sandbox module to replace this one because of this problem:

https://www.drupal.org/sandbox/dsnopek/2844722

It basically just puts the utm_* stuff in a custom cookie, and then grabs the info from it for some tokens