Comments on: Episode 6 – Implementation Best Practices

By: tom pitts

tom pitts — Sat, 06 Mar 2010 20:57:41 +0000

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.

By: Rudi Shumpert

Rudi Shumpert — Thu, 14 Jan 2010 00:15:38 +0000

@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

By: Nathan McLain

Nathan McLain — Tue, 12 Jan 2010 04:12:28 +0000

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

By: Michael Lee

Michael Lee — Tue, 12 Jan 2010 00:43:33 +0000

i wish i could join you guy’s conversation, i have so much to share.