Forum Moderators: phranque

Message Too Old, No Replies

Similar Products to Fireclick

         

dvduval

8:24 pm on Jun 18, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Fireclick is a tracking tool that actually tells you which links on a page are being clicked on at the page level, as well as tracking customers throughout the checkout process. It sounded great and I was excited as a Fireclick employee took me thru the demo. Then they told me it would be $2100/month! Bummer, dude.

Anything like it, but more economical?

Note: I meant to type Fireclick (singular), but unfortunately this forum will not allow me to edit the title.

[edited by: DaveAtIFG at 3:32 pm (utc) on June 24, 2003]
[edit reason] Edited title. Thanks for noting the need! [/edit]

chewy

9:46 pm on Jun 18, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



this is a lot like split run stuff.

Extremely useful, but way expensive to the smaller site.

No I am not familiar with such a tool, I'll take a look at FireClick and look forward to learning more.

dvduval

9:55 pm on Jun 18, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



What makes the product so expensive?
Why can't someone write a script and sell it for less?

wkitty42

9:41 pm on Jun 19, 2003 (gmt 0)

10+ Year Member



whats wrong with using a clickstream log and analyzing it yourself? in my apache configuration, i have it set to assign each visitor a unique id or cookie value for that session and it records every where they go and every resource url they access on my site... it should be easy enough to work up something that would analyze and tell you the flow they follow as they travel thru your site...

FWIW: in apache, the log setting would be something like this...

CustomLog "logs/clstream.log" "%{cookie}n %t \"%r\""

or

LogFormat "%{cookie}n %t \"%r\"" clickstream
CustomLog "logs/clstream.log" clickstream

that would give you output like this...


darktower-e.54731055617738770 [14/Jun/2003:15:09:06 -0400] "GET /cgi-bin/traceback.cmd HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:21 -0400] "GET /siteusage/ HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:21 -0400] "GET /siteusage/usage.png HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:29 -0400] "GET /siteusage/usage_200305.html HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:30 -0400] "GET /siteusage/daily_usage_200305.png HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:30 -0400] "GET /siteusage/hourly_usage_200305.png HTTP/1.1"
darktower-e.54731055617738770 [14/Jun/2003:15:15:30 -0400] "GET /siteusage/ctry_usage_200305.png HTTP/1.1"

from the above, you can see that they came in directly to /cgi-bin/traceback.cmd... hung out there for about four minutes and then went directly to /siteusage/ and from there to /siteusage/usage_200305.html after which, they left the site... this by following only those entries ending in / or .htm(l)

you can also use this to see if all the resources for a page are being pulled as you intend but i don't know if that's really a necessary thing to view as one may click on links faster than the resources are requested... the main thing is seeing the / and .htm(l) pages unless you are scripting a lot of stuff... i'm not sure how that would appear but it should be similar...

HTH