Implementation Best Practices
Join the Beyond Web Analytics team as we get a little more technical and talk implementation with Kevin Rogers of @VaBeachKevin fame. The conversation explores tips for planning an implementation, tools to test your implementation, and strategies for multi-site projects. Be sure to use the comment section below to ask specific questions or suggestions for future shows.
Hosts: James Dutton, Adam Greco, Rudi Shumpert
Guest Host: Kevin Rogers
Kevin Rogers is the Web Analyst for Dominion Enterprises, where he uses Omniture SiteCatalyst as the main analytics engine. Kevin manages the relationship between Omniture and all of Dominion’s businesses, serves as the in house expert for all Web Analytics and is responsible for the implementation of SiteCatalyst for every one of Dominion’s web sites. Kevin blogs at http://webanalyticsland.com/ and can be found on twitter @VaBeachKevin
The Beyond Web Analytics podcast team has explored Implementation best practices, but we would like to hear from you to find out not only any questions you may have or to share some thoughts on the podcast.
Note: The sound clips used in this podcast were used under license.
Burnkit2600 / CC BY-NC-SA 3.0
4 Comments
i wish i could join you guy’s conversation, i have so much to share.
Great podcast guys, I particularly loved Kevin’s tip on setting up a Google Alert on s_code updates.
To be a thorough discussion of implementation validation tools, your listeners may also want to evaluate our solution SiteAudit. SiteAudit is a server based analytics auditing solution with support for all the major analytics and Ad vendors. We have a free account for anyone to try us out. Request one here: http://www.observepoint.com/contact/sales
Best,
Nathan
@Michael – Thanks for listening. Use the Ask The Podcast Or Contact form to drop us a note for a podcast idea and maybe we can have you join us sometime.
@Nathan – Thanks for the comments. I’ll have to check out the tool.
-Rudi
I can understand working with smaller teams and on many sites utilizing the URLs, html layout and other elements to infer values to report to web analytics is the quickest way to get an implementation up, but don’t you find that your implementation will just degrade from then on as the web team makes changes?
utilizing page titles is vary problematic as soon as any SEO efforts are put in place. utilizing URL structures can also cause problems as the website changes over time. many sites use different products for different parts of their sites.
for larger more enterprise sites, the best way to implement is to have the pages output web analytics values in javascript that are not related to URLs, pagenames or design elements which often change without the web analytics team being made aware until AFTER a reporting problem has started.