Advanced Content Tracking with Google Analytics: Part 2 This is part two of a two part series on advanced content tracking. This post is about the reporting and analysis of how people interact with content. As I mentioned in part one, this technique and concept was born from collaboration. Nick Mihailovski – Developer advocate at Google (and the guys that sits across from me)Thomas Baekdal – Smart guy and publisher of www.baekdal.com (you should subscribe)Avinash Kaushik – If you don’t know Avinash…Joost de Valk – Creator of the Google Analytics for WordPress plugin (you should use it)Eivind Savio – Blogger and GA consultant (read his stuff) Let’s look at some data. The Reports This tracking technique uses event tracking to track how people scroll through pages on a site. Here’s the Content > Events > Top Events Report. Reading actions in Google Analytics All the events are bundled in the Reading category. Drill into the Reading event to view the specific reading actions. Let’s take a look at this data and translate it. UGH! This is pretty cool.
Tracking Clicks with Google Analytics Pt. 0 Have you ever wondered what people click on when they get to your website? I don’t mean which links, I mean which elements. Do they get confused and think that an image is a link and try to click on it? Which outbound links do they click on? I know this may seem like a strange topic, but I am headed somewhere :) Using Google Analytics we can actually track every single click that a visitor makes. non-html pages (mp3, pdf, exe, etc.)links to other sitesform elements There is some instruction in the GA help docs, but I’m going to dive deep into this topic during during three blog posts. Part 1: About urchinTracker() In the first part of this series I’ll discuss the technology that Google Analytics uses to tracks clicks. Part 2: Basic Implementation Once we know how GA tracks clicks, I’ll walk through a basic implementation. Part 3: Advanced Implementation Finally, in Part 3 I’ll give you guys the framework to avoid everything I discuss in Part 2. :)
Event Tracking Pt. 1: Overview & Data Model One of the major new features announced by Google at the EMetrics summit is event tracking. There has been a lot of discussion in our industry about tracking events and only a few vendors offer this feature. I believe that Google is the third. Anyway, this post gives an overview of the new feature. Part 2 covers the actual implementation and part 3 covers the reporting. What Are Events Events are actions that visitors take on a web page that don’t generate new pageviews. In the old GA we could track this data as a pageview. Event tracking adds another layer of data to the visitor data hierarchy: Visitors Visits Pageviews Events Now we can really get a good idea of how visitors are engaging our interactive content. Every time an event occurs GA will increase the event counter. Start With Business Questions Before I get into the structure of event data, I want to talk about analysis. But with events, you need to create ALL of the data that will end up in GA. Understanding the Data Model Labels
Understanding Google Analytics Time Calculations Measuring time on a website can be hard. Really hard. Every web analytics tool has issues, and that includes Google Analytics. I’d like to clarify how Google Analytics track time on page and visit length. Understanding Engagement Hits The key to understanding Google Analytics time calculations is understanding the data that is sent to Google. Data hits are the image requests sent to Google Analytics. Pageview hitsEvent hitsEcommerce transaction hitsEcommerce transaction item hitsUser defined hits (this is the predecessor of custom variables)Social plugin hits While these are all data hits they are not all engagement hits. An engagement hit is any hit that is not marked as “non interaction” and is not filled only with custom variable information. Filtering the above list of data hits using the engagement hit definition results in five types of engagement hits: Pageview hitsInteractive event hitsEcommerce transaction hitsEcommerce transaction item hitsSocial plugin hits Pretty easy, right?
Nurturing Your Customers & Business with Universal Analytics Disclaimer: This is a personal post on a personal blog . I’ve been working in the analytics industry as a consultant for a few years and have gotten a feel for some of the challenges that business face. These are my personal ideas and do not reflect those of my employer. Now that all the excitement has started to subside around Google’s Universal Analytics announcement last week I wanted to take some time and talk about how the system can actually be used. I think it’s important to remeber that Google Anlaytics is a platform. The goal of Universal Analytics is to give a business insights into their entire world. To understand the platform let’s walk through how a real business might use Universal Anlaytics. Note: Whenever I give a talk I like to infuse it with a personal touch, which often includes a reference to Vermont, a place I love dearly. The Business There’s a great company in Vermont called Gardner’s Supply. Gardener’s Supply sells via physical store, catalog, online and phone.
What Is The Core Reporting API - Overview | Analytics Core Reporting API | Google Developers This document provides a high level overview of the Google Analytics Core Reporting API Version 3.0. For a detailed reference of the API, see Reference Guide. Introduction The Google Analytics Core Reporting API gives you access to most of the report data in Google Analytics. With the Core Reporting API you can: Build custom dashboards to display Google Analytics data. Choosing a Version We recently launched a new version of the Core Reporting API. Building a new application? Getting Started Want to get started right away? Each application that uses the API will have to go through a couple of steps to register, authorize the user, and work with the API. Conceptual Overview The Core Reporting API returns report data consisting of statistics derived from the data collected by the Google Analytics tracking code. There are 3 fundamental concepts underlying the Core Reporting API: How reports relate to users and views (profiles). Reports, Users, and Views (Profiles) Working With Reports Back to Top
Analytics Blog Gestion de la durée des sessions et des campagnes - Aide Google Analytics Définissez la durée des sessions et des campagnes. Cette fonctionnalité n'est disponible que pour les propriétés qui utilisent Universal Analytics. Les sessions et les campagnes se terminent une fois un certain laps de temps écoulé. Par défaut, une session se termine au bout de 30 minutes et une campagne dure six mois. Vous pouvez modifier ces paramètres de sorte que les sessions et les campagnes se terminent au bout d'un certain laps de temps. La durée d'une session et d'une campagne dépend de votre site et de votre entreprise. Si votre site permet aux utilisateurs de se déconnecter automatiquement après avoir été inactifs pendant un certain laps de temps, définissez le délai d'expiration de façon qu'il s'ajuste à ce laps de temps. La durée d'une campagne ne peut pas être supérieure à deux ans. Modifier la durée des sessions et campagnes Pour effectuer ces modifications accédez aux paramètres d'administration de chaque propriété de votre compte. Accédez à une propriété.
How a web session is defined in Analytics - Analytics Help Les informations incluses dans cet article ne concernent que le suivi des pages Web. Les calculs ne s'appliquent pas aux données collectées via le SDK Analytics pour un système d'exploitation pour mobile.En savoir plus sur les sessions dans les applications Il est important de comprendre le concept de "session" dans Analytics. Vue d'ensemble Une session correspond à un groupe d'interactions effectuées par les utilisateurs sur votre site Web au cours d'une période donnée. Une session peut s'apparenter à un conteneur incluant les actions effectuées par un utilisateur sur votre site. Un même utilisateur peut entamer plusieurs sessions. Expiration en fonction de la durée : Après 30 minutes d'inactivité À minuit Suite à une modification apportée à la campagne : Si un utilisateur arrive via une campagne, quitte la page, puis y revient via une autre campagne Expiration en fonction de la durée Combien de temps une session dure-t-elle ? Exemple Expiration en fin de journée Sites référents
Hits, Sessions & Users: Understanding Digital Analytics Data We talk about data every day – sessions, visits, conversions, pages, hits, etc. etc. etc. But sometimes we fail to understand how all of these metrics fit together and where they come from. Let’s take a look at how digital analytics tools organize data. All digital analytics data is organized into a general hierarchy of users, sessions and hits. It doesn’t matter where the data comes from, it could be a website or a mobile app or a kiosk. Digital analytics data is organized into a hierarchy of hits, sessions and users. Sometimes we use the terms visitors instead of users and visits instead of sessions – they’re analogous. It’s important to understand each piece of the hierarchy and how it builds on the other to create a view of our customers and potential customers. Let’s start at the bottom, with hits, and work our way up to users. Hits A hit is the most granular piece of data in an analytics tool. All data is sent using a hit. Events: An event is like a counter. A quick note on mobile…