-
Notifications
You must be signed in to change notification settings - Fork 2
Form Analytics
SEOVictory edited this page Sep 13, 2010
·
1 revision
As it stands right now, form analytics are done with a separate javascript file. It will always require its own log, because the form info is drastically different than the mouse/scroll motion.
The logfile loosk like this, with
1250705137 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html landing landing
1250705140 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html text theform::text1::1 text1::3
1250705143 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html text theform::text2::3 text2::14
1250705145 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html text theform::text3[]::2 text3[]::11
1250705147 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html text theform::text3[]::2 text3[]::4
1250705150 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html text theform::newww::3 newww::18
1250705156 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html textarea theform::area::6 area::17
1250705156 127.0.0.21 394025_4 http://site/FreeTale/ft_client/form.html submit
Note that none of the form data is logged. the format for input is like \tTYPE\tFORMID::INPUTNAME::SECONDSACTIVE\tINPUTNAME::KEYUPS
i guess i can get rid of one of the INPUTNAME fields. For about and hour i was toying with the idea of sending all the data on submit(), but this had many problems, not the least of which was really long URLs.