New Analytics API Features including Event Tracking!
September 18th, 2009 | Published in Google Analytics
We are excited to be releasing new features -- features that have been prioritized based on feedback from you.
Event Tracking
Get Excited! Event Tracking, our number-one feature request, is available through the API. You can use event tracking to measure the number of user interactions with a website. For example, you can track:
Ready to try out Event Tracking yourself? Check out the event tracking API docs, or fire up the Query Explorer tool.
Navigational data
The Google Analytics web interface provides a navigation report. Analysts use it to infer which links visitors click on, from one particular page to the next. Now that this data is available through the API, you can create new visualizations, such as custom site overlays, to see which links get the most clicks.
Increased filter length
The length of filter expressions has been increased to 128 characters. This enables developers to perform more complex queries with fewer requests to the API, saving bandwidth and quota.
There is a detailed list of all these changes in our public change log. We hope you find these features useful to your development and look forward to your comments and continued feedback. If you haven't done so already, please join our public Google group and let us know how you've been using the API.
Nick Mihailovski
Event Tracking
Get Excited! Event Tracking, our number-one feature request, is available through the API. You can use event tracking to measure the number of user interactions with a website. For example, you can track:
- the total number of times a white paper is downloaded
- the length of time it takes to load a video
- the number of validation errors users get when filling out a form
Ready to try out Event Tracking yourself? Check out the event tracking API docs, or fire up the Query Explorer tool.
Navigational data
The Google Analytics web interface provides a navigation report. Analysts use it to infer which links visitors click on, from one particular page to the next. Now that this data is available through the API, you can create new visualizations, such as custom site overlays, to see which links get the most clicks.
Increased filter length
The length of filter expressions has been increased to 128 characters. This enables developers to perform more complex queries with fewer requests to the API, saving bandwidth and quota.
There is a detailed list of all these changes in our public change log. We hope you find these features useful to your development and look forward to your comments and continued feedback. If you haven't done so already, please join our public Google group and let us know how you've been using the API.
Nick Mihailovski