If you pay attention to developments in Google Analytics, you were probably glued to the live stream of the Google Analytics Summit opening presentations. GA made a number of announcements about forthcoming features. One of the most exciting is about automatically tracking events in Google Tag Manager. It’s a feature that’s been highly requested ever since Tag Manager was released, and it’s especially exciting because it’s available NOW (unlike a number of the other announcements, which are only “coming soon” — such as a forthcoming SLA for Tag Manager for Google Analytics Premium customers).
But, if you go and take a look at Tag Manager trying to figure these out, you might find yourself scratching your head over documentation that is mostly “coming soon”. Not to worry: I’ve banged on the pipes, and here’s a guide to how it all works. (more…)
Implementing Google Analytics can be pretty easy: copy and paste the code, hopefully into some sort of template file that’s used on every page on your website. Done!
But you know it’s not always that easy. First, there’s not just one template, of course, there’s that special one for the landing pages, oh, and this application on our subdomain uses a whole different server. Oh, and you wanted to put some AdWords tracking code or another tool on all those, too?
Then, of course, you’re not allowed to just copy and paste code into the website. It has to go into the update and testing queue, and three months later, if you’re lucky, it will go into production.
A tag management tool can help you with some of these issues. It’s not a cure-all, and it’s not necessarily any better for you if you don’t face these kind of issues, but if you do, it can pave the way for an easier experience. (more…)
Colliding galaxies, because the universe
Google Analytics has great site search tracking features, but they rely on the URLs of your search results pages having a query parameter (the part of the URL after a question mark, with something like “?searchterm=testing” when you search for “testing”). There are ways around this to track site search without a query parameter (that’s an oldie but still a goodie from 2010), but all those workarounds involved adding or altering the code on your site in some way. But now there’s actually a new way to go about this for some URL structures that involves no code at all. (more…)
You probably already know about the Funnel Visualization and Goal Flow reports in Google Analytics. They’re a great way to understand how users complete (or don’t) some kind of process on your website, such as filling out a series of forms, like a registration or checkout.
Sometimes, though, there isn’t a clear path. On this site, for example, we have a contact form that doesn’t just appear on one page, it appears in lots of pages, and this isn’t an uncommon feature of lead generation sites. Likewise, sometimes people say things like, “Well, page X is our goal. But you can actually get here either by going A > B > X, or by A > P > Q > X, depending on what options you choose.” How do we know which way people got to X?
The Reverse Goal Path is a report that helps fill in these details. You’ll find it under Conversions > Goals in the left-hand navigation in Google Analytics, and like all the goal reports, you can select a particular goal you want to see from the drop-down at the top. It’s very simple: it gives you the goal completion URL and the URL of each of the 3 pages that came immediately before. You don’t have to predefine a funnel or anything, it simply looks 3 pages back in the visit and tells you what they were.
So here’s an example from our contact form. The first column is the “Goal Completion Location”, which in this case is always /about-us/contact/thank-you/. Then each of the subsequent columns walks back one page, telling us whether someone was on the home page, the contact details page, the client list, etc. No funnel necessary!
To sort out this information, note that you can use the advanced filter. So if you’re only interested in one particular path or page, you can narrow down the possibilities you’ll see here.
We know you’re eager to start paid search; it can be a crucial way of bringing potential customers to your site. But there are a few things you should make sure you have in place to be successful.
1. Work the Numbers
Stop. Do not pass go. Do not deposit $200 in your AdWords account (yet).
First, figure out what your conversion is — a sale? a lead form submission? Then you have to try to figure out how much money it makes sense to pay to bring people to your site so that you get more value from that conversion than you spend on the advertising.
You can go at this two ways. If you know the value of the conversion (you sold a $100 widget), you can work the ROI calculation backwards to figure out what a reasonable cost per conversion and cost per click might be. Alternatively, if the value of the conversion is less well-defined (like in lead generation), you might simply pick a reasonable target for cost-per-lead.
As the avid users of AdWords know, Google Analytics has a great report that pulls in cost data from AdWords. If you have an ecommerce site or currency values assigned to your goal conversions, it’ll even calculate ROI.
A while back, Google Analytics announced new support for importing cost data from other sources: think Bing Ads, Facebook advertising, etc. This is great! It puts all the power of those AdWords reports to work on your data from any kind of advertising. (more…)
As a followup to my post on interpreting Language data in Google Analytics, here’s some insight into locations as well.
You can find the Locations report under Demographics in the Audience section. Google Analytics determines locations from a visitor’s IP addresses and where internet service providers assign those ranges. (If you remember the dark old days of web analytics when you could look at a report like this and you saw that 80% of US web traffic came from Virginia — because that’s where AOL was located — you can rejoice that these reports are much more accurate.) (more…)
The Languages report is among the most cryptic of the reports in Google Analytics. It looks like you need a secret decoder ring to figure out what it’s telling you. Here’s some guidance on what those codes are and what they mean.
What are they?
These language codes represent a language and optional country variant. (We’ll look at where GA gets these momentarily.)
The codes aren’t specific to Google Analytics; in fact, they’re based on two ISO standard specifications: (more…)
Don’t have a mobile site? That doesn’t mean you have no mobile visitors. In fact, Google Analytics is already measuring visitors from smartphones and tablets to your site, and you can use this data to figure out what’s important to these visitors and how well your site is working for them.
You can see mobile visitors in the Mobile reports under Audience. First, there’s the Overview report, which just says “how many visits came from a mobile device” (and that includes tablets):