Case Study: Demographic Insights with YWAUsing YWA’s demographic reporting, YWA Consultant Network partner Location3 Media has been working with one of their clients to research their website visitor demographics. This client has several business locations across the United States, which service the entire region for their location. In order to get a better understanding of the differences between demographics in these regions, Location3 Media created a unique segment for visits from each of the regions.
Adding Customization to Actions in YWAThe following post is by Yahoo!’s Tim Hampshire, he is a YWA Account Manager and Support Specialist. Actions are a powerful feature of YWA that allow you to track conversion events that take place on your site. Currently YWA allows you create up to 50 of these custom actions which you can quickly run out of if you do not define them with care. In this post we will demonstrate how to use Custom Fields to store additional information about your actions in order to avoid overusing the limited number of actions available in YWA. How Not To Use Actions in YWA Let’s suppose we are working on setting up YWA on a cooking site where the users can view flash video presentations for each of the recipes on the site. For the reporting, we are interested in seeing how often each one of these videos are viewed. One way of accomplishing this would be to define an action for each individual video:
The number of actions used could also get compounded by cycling through the various forms of each recipe:
Using this method of defining actions we would very quickly find ourselves running into YWA’s limit of 50 custom actions. We also might find that adding extra categories to these actions would be laborious and potentially error prone. The Correct Usage of Actions in YWA When creating actions in YWA, you will want to define them as broadly as possible so that they can be used on multiple locations of your site. We can then use Custom Fields to capture detailed information about the specifics of the action performed. Using Custom Fields with our actions in this way will add the detailed classification and grouping information we are looking for when running granular reports in YWA. Dynamic Tracking Code Loading in HTTPS or HTTPThe following is a guest blog from Gustavo Cornejo of Multiplica, one of the members of our Consultant Network (YWACN). They are located in Barcelona and specialize in web measurement, testing, and intelligent analysis. You can find the original post in Spanish here. Monitoring websites with secure pages requires the use of two different sets of Yahoo Web Analytics tracking code, one for secure pages and the other for non-secure pages. The drawback to this is that you are left with inconsistent tracking code across the site and care must be exercised to ensure that the correct tracking code is being used in the right place. An alternative to this would be to use the secure tracking code on all pages but this would lead to unnecessary load time on the pages that do not need it. Another solution is to integrate a discriminator according to the protocol used on the page to load only the code necessary for that page. Additionally, we must know when the JavaScript is loaded and execute the tracking code without causing execution errors. The solution is taken in 4 steps:
Carga Dinámica En HTTPS o HTTP Para YWAThe following is a guest blog in Spanish from Gustavo Cornejo of Multiplica, one of the members of our Consultant Network (YWACN). They are located in Barcelona and specialize in web measurement, testing, and intelligent analysis. Update 11/2/1: We’ve added an English version of this blog post Para el seguimiento de webs con entornos seguros es necesario implementar dos códigos diferentes utilizando Yahoo Web Analytics, o simplemente utilizar siempre el código para entornos seguros. Alguno de los inconvenientes; el seguimiento y la inconsistencia en el código, errores en la implementación. Utilizando sólo el código para entornos seguros estamos penalizando un poco más la carga del código en todas las páginas que no requieren elementos seguros. Una solución es integrar un discriminador según el protocolo utilizado en la página para cargar para cargar el código necesario. Adicionalmente, tendremos que saber cuándo se carga para poder utilizar las funciones necesarias para el seguimiento y no provocar errores en la ejecución. La solución se separa en 4 partes:
(Continue reading…)Yahoo! Web Analytics: Segmentation Made EasyNote: This is a cross-post originally from Matt Lillig’s personal blog, Matt is the Senior Analytics Lead at Yahoo! Let me give you a tip. If you want to run a successful web site, then get to know your visitors better. The companies that really understand who their visitors are tend to be the most successful because they’re able to get the greatest return out their visitors. They get more engagement from their visitors, their visitors click on more links and pages, and their visitors tend to convert more. Part of understanding your visiting audience comes down to figuring out which segments of your audience perform the best. Once you figure that out, life gets much easier because now you know who you should be developing and targeting your web site content for. In Yahoo! Web Analytics, it’s easy to figure out who your audience is with its demographic, geographic, and interest group data. For example, by visiting the ‘Age and Gender’ report you’ll quickly see what age range and gender group visits your web site the most. By visiting the ‘Interest Group’ report you’ll understand which category your visitors are interested in the most (entertainment, sports, finance, news, etc). In less than two minutes, you can begin to build a picture of your audience. But Yahoo! Web Analytics also does so much more to help you understand your audience. |
|
