BLOG

How Megalytic Accesses and Uses Google Analytics Data

Published April 30, 2012

I'm in the process of listing Megalytic in the Google Analytics App Gallery. They require a page that explains in "plain language" how we access a Google Analytics account and what we do with the data. So here it is.

How Megalytic Accesses a Google Analytic Account

Metalytic uses the Google Analytics API and authorizes via OAuth 2.0. That means we don't store your user name or password for Google Analytics.

Introducing Megalytic

Published April 19, 2012

Marketing analytics professionals are overwhelmed with work these days. At one Fortune 500 company, the Director of Marketing told us that his team has only 2 analysts supporting over 180 different web sites, dozens of Facebook pages, multiple Twitter accounts, and email campaigns.

ALSO IN THIS BLOG

Remember how your mom told you not to stand too close to the television because it might hurt your eyes?
The same rules can apply to data. If you’re too close, you may miss the patterns and trends that are crucial to understanding your website’s performance. You can’t judge a site’s performance looking at data in the bubble of a single day, you must consider any day’s traffic compared to the days before and after.
Google Analytics makes it fairly easy to analyze trends over long periods of time. But it also allows you to stand right in front of that TV, to look at more granular levels of time, right down to the hour.
There’s a better way to get that close to the data, without burning your retinas. We’ll cover how to analyze traffic effectively in today’s post.

 

 

When the client first came to you, you talked up the value of Google Analytics. You emphasized the importance of seeing where your traffic was coming from. You went on and on about how Google Analytics can show traffic sources to pinpoint whether people came from search, social media or a specific site referral, and how valuable this data was. You sold them on it, so much so that your client looked forward to receiving that first report, the magical day when they would finally understand where visitors were coming from.
But then the report came, and it looked like this:

 

 

It showed that 10% of your client’s traffic came from “(direct)/(none)”. What does this label mean? How do you explain Direct traffic to your client? Better yet, how do you explain “none”?
Let’s take a closer look at understanding Direct traffic in Google Analytics and how we can address it with clients.
One of the most exciting and important aspects of digital marketing is the ability to understand exactly how your customers are finding you. It informs every single part of integrated campaigns and helps determine which efforts are working and which ones need to be revisited. Google Analytics allows you to zero in on the performances of different marketing channels to evaluate everything from brand awareness to social media messaging. To get the most insight from that data, it’s crucial to understand exactly how Google sorts your traffic.
Channels in Google Analytics are high-level categories indicating how people found your site. While the Source/Medium report shows you in more detail where people came from, Channels are broader, more “user-friendly” names lumping visits together in buckets useful for high-level reporting categories.
For instance, Facebook Sessions often show up in multiple ways in the Source/Medium report. They may appear as facebook.com, m.facebook.com, and l.facebook.com, all of which are variations of the same source. The Channels report will include all of these in the Social bucket, so you can see less granular, aggregate numbers on social media performance.