Hi Alexander,

I agree with your suggested changes and will get to them soon.

Best,

Joe

Hi Alexander,

Yes, I have seen that as I subscribe to the Google Analytics blog.

There are several challenges to changing to this async model, the best we could do easily is implement the split script approach mentioned here:

http://code.google.com/intl/ru-RU/apis/analytics/docs/tracking/asyncUsageGuide.html#SplitSnippet

which retains most of the benefits of the async approach.

The other issue is backward compatibility for existing sites which may have javascript snippets already entered in the content system for custom tracking. For example I have many places where I track things like referrals to consulting partners and other external links where I have added javascript to the link to track the click like this for example:

<a class="fn org url" href="http://i7media.net/mojoPortal.aspx" onclick="mojoPageTracker._trackPageview('/ReferToi7Media.aspx');window.open(this.href,'_self');return false;">i7 Media</a>

so it would be problematic for me to find all these in my content and replace with the new async syntax and others may also have existing tracking snippets.

What I am willing to do is make 2 new controls GAnalyticsAsyncTop and GAnalyticsAsyncBottom so we can implement an option for the async approach without breaking any existing tracking using the old approach. I will let you know when these controls are ready and you could test for me since I do not want to change my site. The idea would be to remove the existing one and replace it with the bottom control and also add the top control just after the opening form tag in layout.master.

I have not had any problems using the traditional approach and I think this async approach is a micro optimization. Recently I watched all the videos on the googleanalytics channel on YouTube http://www.youtube.com/googleanalytics I learned a lot that helped me get better reporting, especially about advanced segments. I highly recommend watching all these as they were very helpful. But one thing I noticed is they mentioned how they soft launched the new async script approach but are not pressing hard for people to change to it and they will never get rid of the traditional way. But in any case I will try to implement support for it with the 2 new controls and hope that you can test it when it is ready and make sure it works correctly.

Best,

Joe

Hi Alexander,

I've already made most of the changes but have not yet merged it to trunk, it should be there by tomorrow night.

I came to the same conclusion after learning more about analytics and looking at my reports, I should not be using resource files for those labels. My intention was for it to be possible to localize the labels, but on my site where I'm not forcing a specific culture I get a mix of labels based on the user browser language. I will make those come from Web.config settings so they can be customized as needed but will be constant for a site.

I have an idea for  a change for the cookie logic as the user may not always have the cookie if they come from a different machine, so it is not optimal. My intention is to flag authenticated users as members, user's who have made transactions in my store as customers, and admins as admins, but currently a customer who signs in from a different machine is flagged as member. I need to change to have the logic in mojoGoogleAnalytics instead so I can just check the siteuser object for TotalRevenue and check if he is in Admins role to determine the memberType label, then I will not need a separate customerLabel property and I will not need the cookie check at all.

I really enjoyed those videos on YouTube and next plan to study the resources at Conversion University: http://www.google.com/support/conversionuniversity/?hl=en

The things I still want to understand better is setting goals and using the funnel reports to improve conversion rates. I think there is some challenges when using external payment providers like PayPal and Google Checkout because the user leaves the site to make payment and if it takes more than 20 minutes for them to return then it is seen as a new session that completes the order and the old session looks like they abandoned the funnel. So this makes it difficult to get a good understanding of the user behavior. What happens is that orders take a while for the payment to clear and only after it clears do they get the confirmation email with a link to the order detail and that is where the transaction is logged to google analytics. So we get a session that looks like the user left the site without completing the funnel and then we get a session that looks like the user came out of nowhere and completed a transaction but they are not the same session from analytics point of view so the funnel report cannot connect the dots between the separate sessions. One solution that comes to mind is to send an initial email as soon as the order is received and make a link to the order detail so the user does come back to the site right away and we can track the transaction sooner but show the user on the order detail and in the initial email that the order is received but payment is still being processed. Then when payment clears send another confirmation so the user can download the products. These issues may not affect you or be of interest if you are not using the WebStore feature but the ecommerce reporting in google analytics is very interesting to me since I am trying to figure out how to improve ecommerce conversion rate on my store.

Best,

Joe

Hi Alexander,

The new controls for Async google analytics have landed in svn if you want to test them.

remove the <portal:mojoGoogleAnalyticsScript from your layout.master and then put this at the top just below the opening body tag

<portal:AnalyticsAsyncTopScript id="analyticsTop" runat="server" />

then add this just before the closing body tag

<portal:AnalyticsAsyncBottomScript ID="analyticsBottom" runat="server" />

If you discover any errors in these controls while testing please feel free to modify those controls and send me the changes. The controls are located under Web/Controls/Analytics.

I've also updated the regular googleAnalytics control.

Best,

Joe

Hi Alexander,

The function _setAllowHash takes a boolean not a string therefore it does not need quotes. The documentation does show quotes in one place but I believe that is an error in the documentation as most places in the documentation do not show quotes around boolean parameters passed to functions and javascript has a boolean data type represented by true and false and typically in javascript you don't put quotes around boolean variables.

http://code.google.com/apis/analytics/docs/tracking/gaTrackingSite.html

http://code.google.com/apis/analytics/docs/gaJS/gaJSApiDomainDirectory.html#_gat.GA_Tracker_._setAllowHash

I track dialog page views the same as any other because I want to record all viewed pages. I see no reason why a dialog should be treated differently.

Best,

Joe