How can we keep up? Alongside Google+ and the new content creator experiment (see this SERP), Google also happened to announce a slew of new features for Google Analytics and Google Webmaster Tools. Yesterday was one of those days that downloading information via a Matrix head pluggy thing would really make things easier.
That picture of Matt Cutts just made this all too easy
Well, we don’t have Matrix head pluggy things yet, so let this post be your guide. Let’s break down some of the new stuff.
+1 data in Google Webmaster Tools and Google AnalyticsFirst, the easy no-implementation cool thing. Now, all of your +1 data is passed into GA and GWT in a couple of cool ways. In Google Webmaster Tools, we can now see what impact the +1’s have had on CTR from the SERPs in the search impact report. In Google’s announcement post, they use an example site with a good amount of data (and a favorable impact). In nearly every account we have access to, this report is rather sparse despite some pretty well +1’d sites.
This isn’t exactly useful yet (ever?)
In the activity report, we’re given a look at +1 counts that have occurred on-site or on “other sites”. Google defines “other sites” as +1s from search results or ads, which is curious. Perhaps Google+ shares count as “other sites”? Hard to know at this point. Regardless, if you’ve had +1 on your site and have actually seen some engagement, this report ends up looking a lot more interesting:
Lastly, the audience report displays demographic and geographic information about those that +1 your site.
This data is for the same site, which allows us to conclude (at this point) that you’ll need a lot more than 2,000 +1s to influence CTR (see previous report).
Google showing this data to site owners certainly means that they’ll be (or have been) collecting and analyzing it themselves in the aggregate. Imagine John Doe creates a Google account and provides his A/S/L. Without any prior data on this user, John, the 25 year old male from Seattle, might be provided a completely different set of search results than Jane Doe, the 60 year old female from Oklahoma.
Tracking Social Interactions in Google AnalyticsThere were a slew of good posts recently on how to track social interactions such as tweets, +1s, Likes, etc., within Google Analytics. Yoast wrote a good post here. Essentially, we were tracking these interactions as events. It was a nice solution, but with the announcement yesterday, this is a better option.
First, your site’s +1 interactions should already be being passing into Google Analytics.
For this site, Google Analytics and Google Webmaster Tools’ data was actually extremely similar.
It is important to note that, in many ways, the +1 data in Google Webmaster Tools is more useful than that in Analytics because you’ll also be given +1 interactions from “other sites”.
Tracking Tweets, Likes, Unlikes, Shares, and More in Google AnalyticsLastly, and perhaps most substantially, Google also detailed how to track Facebook likes, unlikes, and shares, and Twitter tweets within your Google Analytics account. Fortunately, the announcement declares, “You can enable tracking for other social plugins in just a few simple steps.” (link goes to official documentation). We’ll let’s just see about that...
Many sites add social buttons by using content management plug-ins. If you are the author of such plugins, we highly recommend you integrate Google Analytics Social tracking to automatically track these interactions. Similarly, if you are a developer at a Social Network, you can also make it much easier for users to track your social network interactions in Google Analytics by integrating with our tracking feature.
For WordPress folks, it’s only a matter of time before a simple plugin integrates this functionality. Keep your eyes open. I’m sure this will be a short wait.
Also interesting is Google’s call to developers at the social networks to integrate the ability to send the _trackSocial call to GA. Will they heed the call? Once again, keep an eye out! You can imagine, perhaps, that Twitter might add a
ga-account parameter along with its
data-url, data-count, etc., properties.
Who needs a matrix pluggy thing!
Oh, and I’m just gonna leave this here: