More and more sites are moving towards HTTPS in the past months. Google claimed it can be used as an SEO ranking signal and privacy organizations advice it so you give your visitors more privacy.
Google Analytics works fine on both HTTP and HTTPS sites. In the basic tracking script you see this line:
It's a protocol independent URL that will fetch the analytics.js file from HTTP or HTTPS based on the site's protocol where the script is loaded. But Google Analytics offers an extra option to do the tracking in HTTPS also. Take your basic tracking code and add the forceSSL line:
ga('set', 'anonymizeIp', true);
ga('set', 'forceSSL', true);
(I also add the anonymizeIp line by default to give my visitors just a little bit more privacy).
Google recently launched a new function called "Exclude all hits from known bots and spiders". You can find, and turn it on, in your "view settings":
Last week I did a tweet with this image in it:
It shows a Google Sheet with some data per AdWords campaign and a little sparkline next to the numbers. It got much attention, and I got many requests to explain what I did there. So here it goes, I will explain some things about the Google Analytics API, how you use it in a Google Sheet and how to extract and query data from it. And last but not least: how to create the little sparklines.
Today Google officially launched the real-time widgets for use on the Google Analytics dashboards. Awesome feature that can make real-time analytics a bit more useful than it was before. These are the new widgets (the second row) you can use to visualize real-time stuff:
The great news is: you are able to put filters on these widgets... really awesome. Google has a more extensive description about all new possibilities, but here's an example I would use these features for.
Great news, my buddy Tim Bakker told me Google introduced a new Change History feature. And when you login to your analytics account you will see this message:
With this new feature you will be able to see which account changed what to your account. This includes:
- Accounts: created, deleted
- Users: added, deleted, changed
- Goals: created, deleted, changed
- Filters: created, deleted, changed
In one word: awesome. From now on you can see if the requested goal changes are processed by your Web Analytics consultant. Or who applied a filter that blocked all data from a specific profile.
Just a quick post about the retargeting (remarketing) option in Google Analytics. July '12 Google launched a new feature in Google Analytics that made it possible to retarget a specific group of visitors. You only need to change this line in the Google Analytics Tracking Script from:
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
ga.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'stats.g.doubleclick.net/dc.js';
The script will be loaded from the doubleclick domain and a third party cookie is set. That cookie can be used to target visitors on other sites that have been on your site.
Google launched a new feature in their ecommerce module that helps international sites in tracking their worldwide revenues. Until now every single site that worked with multiple currencies had to implement some sort of curreny-converter script to get all revenues in the same currency. This is a very time consuming and expensive action that needs constant attention. As of today this is all history.
Google implemented a new feature that can convert the local currency to the currency you specified in your profile settings:
It looks like Google is rolling out some new features in Google Analytics. There isn't an official statement/blog about it, but after some digging I found these new features:
New graph formats on the dashboards
There are 2 new types of graphs you can choose on your dashboard:
The Geomap and Bar are new. The Geomap is a known report that was available for quit a while in the normal reports. But on the dashboard it's a welcome addition. The Bar is new and looks like this:
Just a small update from here (haven't been blogging for a while). If you're looking at the Windows 8 stats in your Google Analytics account you will see this graph:
Last October I tweeted that Google Analytics was reporting "Windows 8" as "Windows NT". I like to think they read my tweet and changed this on December 11th Since the launch of Windows 8 on October 25th you see traffic for "Windows NT" suddenly rising until they changed it to "Windows 8".
For a while I wanted to write this post about the Google Analytics sampling. You know, the dreaded message that appears on top of your reports:
This message shows up when you work with a dataset that contains more than 500.000 visits or more than 1.000.000 items (keywords/url's/etc). Above that Google takes a sample of all those visits to calculate the numbers for your reports. But what is acceptable? In this example Google uses 30.62% of all visits to guess what the other 70% did on my site...