One of Google Analytics’ under-appreciated features is Custom Alerts, which allows you to receive a notification from Google any time certain metrics fluctuate beyond the bounds you set. Custom Alerts is a great way to avoid this:

In this case, we can see that no conversions have been recorded at all for several days. This kind of thing happens frequently, in part because there are so many potential causes: changes to the website’s goal URL, the addition of a filter to a GA profile, the removal of the GA tracking code, etc. Without custom alerts, you’re only able to detect these kinds of issues as frequently as you log in, which may not be every day. By setting up custom alerts, you’ll be able to diagnose and address these issues much more quickly. Let’s take a look at a few of the most useful custom alerts.

Custom Alert #1: Goal Conversion Rate Decreases

As you can see below, Google Analytics gives you several ways to set up your alerts. In this case, I like to use the “% changes by” condition so that if my goal conversion rate decreases by more than 80%, I get an email. It’s possible that my site could just be having a bad day, but an 80% drop in conversion rate is a pretty good sign that I need to investigate what’s going on.  To set up this alert, click on “Intelligence” in your reports navigation menu. Then, find the “Create a Custom Alert” link.

Next, you’ll be taken to the alert setup wizard, which is awfully similar to the advanced segmentation wizard (which you should all become familiar with!). Choose the segment of traffic to which you want to apply the alert, and then set your conditions. Here’s how to set up our first alert.

First, we need a name for the alert. Next, we choose the profiles for which the alert will be set. Then, we choose between making this a daily, weekly, or monthly alert; for this alert, daily is the most useful. Then, importantly, we need to make sure we check the box that says “Email me when this alert is triggered.”

Next, you’ll set the various conditions for your alert. For this alert, we’ll want to make sure the alert applies to all traffic. We choose “Goal Conversion” rate as our metric, “% decreases by more than” as our condition, 80% as our value, and the previous day as the comparison value.

Press “Create Alert” and you’re all set! Now that you know how to set up custom alerts, let’s run through some more alerts that are frequently useful.

Custom Alert #2: Revenue Decreases

If you’re an e-commerce site, you should have revenue tracking set up as well as “static” goals like contact forms, etc. Setting up our first goal won’t tell you when your actual revenue is fluctuating; you’ll need to set up a similar alert, but with revenue as your key metric.

Custom Alert #3: Traffic Decreases

Hopefully, if your website is down for an extended period, you won’t need Google Analytics to tell you about it. However, setting up alerts based on traffic decreases is a great way to be alerted when something has gone wrong with your Google Analytics implementation. The following scenario happens regularly: a website update is pushed out, and your GA tags are adversely affected somewhere along the way. Although your site doesn’t go down, you see your visit metrics flat-line. To minimize the time for which you’re affected by issues with your GA implementation, set up an alert based on visits decreasing by more than, say, 60%.

Custom Alert #4: SEO Metrics

If you’re like most organizations, organic search traffic is probably something you care about quite a bit. Want an easy way to keep track of how visible your site is across the various engines? Set up a weekly or monthly alert based on organic traffic only (rather than all traffic). Try one alert for decreases of more than 20%, and one for increases of more than 20%.

Custom Alert #5: Monitoring Brand Terms

Measuring response to branding efforts can be difficult, but one good approach is simply to measure how searches on your brand terms change over time. This is super easy with Custom Alerts. Set up a weekly or monthly alert that’s based only on the specific keywords you care about, and have Google send you an email if your metrics go up or down 20% week-to-week or month-to-month.

We hope these ideas for Custom Alerts will be useful for you, and that they get you thinking about what other kinds of metrics could be helpful for your organization. To get more analytics tips and tricks, subscribe to our RSS feed, and don’t forget to follow us on Twitter.

---

Nick Iyengar
Nick is a senior analytics and web intelligence analyst with WebShare. You can find out more about Nick here.

See more posts by Nick Iyengar

It’s a bit late for a New Year’s-themed post and a bit early for a spring cleaning-themed post, but it’s never a bad time to get your Google Analytics data cleaned up. For those of you looking to do just that, here’s a “Quick Fix” checklist to put yourself on the path toward usable data.

1. Identify and resolve self-referrals
A “self-referral” is a visit for which the referring source is your own website. Self-referrals prevent you from seeing the original, valid referral information for the visits in question, so if you’re measuring ROI on advertising outlets, paid search placements, or offline campaigns, it’s important to reduce self-referrals to a minimal level.

First, make sure that every single one of your pages is tagged.  This can lead to situations where self-referrals occur.

Many self-referrals are a symptom of deploying Google Analytics without customizing your tracking code to track across subdomains (like blog.yoursite.com) or top-level domains (yourshoppingcart.com). Fortunately, this customization is fairly simple and easy to complete.

When a visitor to yoursite.com navigates, for example, to blog.yoursite.com or yourshoppingcart.com, GA’s default behavior is to set new cookies on the user’s computer, causing yoursite.com to appear as the referring website to a new visit that starts on the new subdomain or top level domain. However, by adding the following simple customization to your Google Analytics tracking code, you can ensure that GA preserves the pre-existing set of cookies, and therefore the original referral information persists throughout the entire visit.

For tracking across top-level domains:

On your first domain (yoursite.com), add the following to your tracking code before the trackPageview() call (obviously replacing “yoursite.com” with your own domain):

pageTracker._setDomainName("yoursite.com");
pageTracker._setAllowLinker(true);
pageTracker._setAllowHash(false);

pageTracker._setDomainName("yourshoppingcart.com");
pageTracker._setAllowLinker(true);
pageTracker._setAllowHash(false);

Now, for every link that you have on either domain that sends a visitor from one domain to the other, add the following bolded code:

<a href="http://www.a-different-domain.com" onclick="pageTracker._link(this.href); return false;">


If you have forms that submit across top level domains, you’ll need to add the following bolded code to each of those as well:

<form action="http://www.a-different-domain.com/form-processor.php" onsubmit="pageTracker._linkByPost(this);">


For tracking across subdomains:

This is MUCH easier than the above.  All you need to do is add the following line of code to your tracking code that appears on all your pages, regardless of the subdomain they’re on, again making sure that it goes above the _trackPageview() call:

pageTracker._setDomainName("yoursite.com");

For both subdomain AND top level domain implementations:

Lastly, you’re going to need to set up a filter to apply to each of your profiles so that you can see which (sub)domains your visitors are viewing in your content reports.  To do this, you’re going to create an Advanced Filter like this:

Filter Type : Custom filter > Advanced
Field A : Hostname Extract A : (.*)
Field B : Request URI
Extract B : (.*)
Output To : Request URI
Constructor : $A1$B1

To illustrate what this filter does, let’s say that you have an “index.php” on both www.yoursite.com and blog.yoursite.com. By default, Google Analytics will take all the pageviews for “index.php” and aggregate them on one line of data in your content reports. The problem here is that you want to be able to distinguish between those two URI’s, because they are NOT the same! The filter above will take “index.php” and prepend the hostname to it, so you’ll end up with TWO rows of data in your content reports: “www.yoursite.com/index.php” and “blog.yoursite.com/index.php” – and now you can see who’s viewing what pages.

Note that this will change the URI’s that Google Analytics stores, and if you have goals configured to match your old URI’s, you must update those goals once you’ve applied this filter.

With this customization in place, you’ll eliminate one of the biggest sources of self-referrals. Here’s an example of how you’ll benefit. Let’s say you’re running a Google AdWords campaign. You’ll now be able to track your AdWords visitors (and spend) end-to-end on your site, without the risk of losing track of them due to self-referrals. This is critically important for evaluating and improving the performance of any source of traffic.

2. Track all your goals
This sounds basic, but a very large proportion of Google Analytics users don’t track any goals at all, and most GA users that do track goals will only configure one or two. Now that you can have up to 20 goals per profile, you should be tracking every single goal you can think of. To do this, have a brainstorming session and write down every reason you have a website. For example, if you run an e-commerce website, your shopping cart will most likely be your most important goal, but what about tracking goals like these?

• Newsletter sign-ups
• Email to a friend
• Buttons to bookmark/subscribe
• “Contact us” submissions
• Internal search

You could also track goals such as video views, specific content views, social media interaction, RSS feed clicks, blog comments left, and literally hundreds more. Using new “threshold goals,” you can even track time on site and pages per visit as goals.

It’s important to measure all of the value that your site provides. These “microconversions” will give you a fuller view of the performance of your marketing efforts, which will in turn help you make better decisions.

3. Tag your campaigns properly
Tagging campaigns properly is critically important if you plan to use Google Analytics to evaluate the performance of your various marketing efforts. Without proper tagging, it’s nearly impossible to use Google Analytics to evaluate the performance of marketing channels like:

• Yahoo! Search Marketing, Microsoft adCenter and other SEM platforms
• Banner ads, text ads, and other paid placements
• Offline media like print, television, radio, direct mail, billboards, etc…

You can very easily link your AdWords and Analytics accounts and have Google auto-tag your AdWords campaigns for you, but for any other marketing channel, you’ll need to get your links tagged yourself. We recommend that you develop standardized naming conventions before you start to tag or re-tag your campaigns; this will promote consistency and minimize confusion and headaches down the road.

For example, for paid search campaigns, will you use “cpc” or “ppc” as your medium? For campaign names, will you use flight dates (“feb2010”), target audiences (“nascardads”) or something else? Once you have a naming convention in place, you can use Google’s free URL Builder to input your tagging parameters and get your campaigns set to go. Of course, you can always tag your links manually too. In either case, here’s what a properly tagged URL might look like for a Yahoo! Search Marketing ad:

http://yoursite.com/?utm_source=yahoo&utm_medium=cpc&utm_campaign=widgets&utm_content=smallwidgets&utm_term=little%20widget

Notice that we’ve defined the source of the traffic (“yahoo”), the medium (“cpc”, denoting cost per click), and the name of the campaign (“widgets”).  We’ve also used the optional parameters content (“smallwidgets”, which in this case is the name of the adgroup) and term (“little widget”, in this case the keyword we were bidding on).

IMPORTANT: Third party tracking mechanisms or URL shorteners often strip out these parameters, so make sure that any redirects that occur before a user reaches your landing page accept query string parameters.  If you click on your own ad and you end up at a URL like the above, you’re all set.

Cleaning up self-referrals, tracking all of your goals, and tagging your campaigns correctly will help you quickly get more accurate and actionable data in your Google Analytics reports.

For more tips, tricks, and strategies, bookmark our blog, follow us on Twitter or attend one of our Google Analytics & Website Optimizer Seminars!

---

Nick Iyengar
Nick is a senior analytics and web intelligence analyst with WebShare. You can find out more about Nick here.

See more posts by Nick Iyengar