'Net Features : analytics code

40+ Data Points Added to Google's Core Reporting API (Analytics)

Pete Prestipino — Tue, 25 Sep 2012 16:30:00 GMT

Web workers can expect to see a lot more in the way of data within the applications they interface with as Google last week added over forty new data points (metrics and dimensions) to its reporting API's.

Developers wil be able to tap into the data and create reports similar to what is available within Google Analytics itself.

Some of the metrics and dimensions featured include on-site interactions (e.g. social data), visits from mobile devices, a geographic dimension to indicate the Designated Market Area (DMA), page path rollups, user timing and more.

A full list of the new data points is available on Google's Core Reporting API changelog.

Standards for Downloadable Media

Pete Prestipino — Tue, 03 Feb 2009 02:31:00 GMT

One of the many reasons that advertisers never really signed on to advertising within digital, downloadable media is the measurement complexities. It's hard to know how people are using that media when they leave a website. Fortunately, after months of formal review, several members of the Association for Downloadable Media (ADM), including NPR and PRI, have agreed to support standards for advertising formats and audience measurement.

The supported ad formats include pre-roll, mid-roll and post-roll insertions, product placements and host endorsements. The list of download measurement guidelines is actually quite interesting, addressing native and third-party measurement issues, as well as the data contained in log files - from IP addresses and time stamps to topics like byte range and bytes served.

A Flurry of Analytics Data for Mobile Apps

Pete Prestipino — Mon, 26 Jan 2009 16:39:00 GMT

Cross-platform mobile application analytics provider Flurry is making available its free service to all iPhone, Android, Blackberry and Java ME developers.

Flurry's technology allows developers to gather live consumer usage data (application behaviors, technical problems, etc.) to improve their products, increase user retention and compete more effectively in the new application markets like the App Store, which features more than 15,000 applications.

"Rapid adoption of Flurry Analytics validates we're solving a significant pain point for game and application developers. The response has exceeded our own expectations," said Flurry CEO, Simon Khalaf. "With more platforms supported than any other mobile analytics provider (1200) and new features being added all the time, Flurry offers the most complete solution on the market."

Does Analytics Code Placement Matter?

Pete Prestipino — Mon, 19 May 2008 15:40:00 GMT

Those involved directly with analytics always have the same conversation - "Where should the analytics code be placed?" Eric Enge of Stone Temple Consulting are in pursuit of a formal answer and have tested the placement of the same analytics code within the top and bottom of a web page. Check out the detailed post on testing analytics code placement here.

Enge and his team are suggesting that if page load time is fast (total page load time of under 3 or 4 seconds), then javascript code should be kept at the bottom. This will remove any risk related to analytics vendor downtime. According to the post, "The small loss of data you see in this scenario should not be a significant factor in the value of your analytics data."

If your page load time is a bit slower however (4 seconds or more), consider placing your analytics Javascript at the top of your web page. "Your data loss will be larger, and also the nature of the lost data may start to differ."

Good advice!