I was just looking at this yesterday on the Google Analytics site. It's a way to define custom variables at either the page, session, or visitor level:
Tech Support Analyst
Hunter Library @ Western Carolina University
[log in to unmask]
Please consider the environment before printing this email!
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Yitzchak Schaffer
Sent: Monday, November 23, 2009 7:01 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Web analytics for POST data
Alejandro Garza Gonzalez wrote:
> on your coding wizardry level) could track anything from hovers over
> elements, form submission, "next page" events, etc.
Thanks for a great suggestion. I tried poking around at it; it seems to
me like Events aren't built for what I'm really interested in doing,
namely systematic exploration and analysis of the search sessions. IOW,
let's say a form looks like
It looks like I could log this as three separate events, or one; but
either way, how would one analyze this? I'm not interested (solely) in
how many times this particular query was entered.
I started looking at ways to funnel the params into my own tracking
script, the prototype of which just writes a line to a text file with a
JSON serialization of the form data; but I'm not a JS ninja, so I'm
still trying to figure out how to get around the XSS problems.
Ruddy III turnkey...
Touro College Libraries
33 West 23rd Street
New York, NY 10010
Tel (212) 463-0400 x5230
Fax (212) 627-3197
Email [log in to unmask]