We’re implementing GA Event Tracking.  Presently, we’re concerned with the following events:

  • Registration/Login Window Pop Up
  • User registration
  • “More Search Fields” implementation
  • Search field utilization

Because we will track the light window pop up along with user registration, we will be able to see our bounce rate at that specific instance.  So, tweaking the registration/login light window will become a point of interest.

Because we’re tracking search field utilization, we will be able to see the most popular features on the search.  This should provide insight to improve the search app.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Technorati
  • Reddit
One Response to “Google Analytics: Event Tracking”
  1. Kevin Koitz (2 comments.) says:

    The work and the progress have been fun to watch. And I’m glad you’re taking an “academic” (for lack of better word) approach. I don’t know Austin well, but from other Austin sites I’ve explored, I think a “city/region” drop down will track well b/c you can break these areas down into a relatively small group — and each area is relatively well defined (West Austin, Southwest Austin)? Yes, kind of a question! Subdivisions…much harder in most areas. For a clean, compact interface, like yours, the solution may be a pop-out of check-boxes of subdivisions.

    I’ll stop while I’m behind :=) but just getting at how the organization of areas — and the programing solutions given the general framework of the interface itself is THE incredible challenge when designing a custom RE search program IMHO. Thanks for continuing to share, Eric…you’re close and there’s no doubt you’re going to figure out all the angles.

Leave a Reply