Web Traffic Analyzer Just in case you didn't know, these things use the log files in your web server to help you see what your visitors are doing. What Makes LogJam Different? You can write your own reports. And you can start using your own reports right away. You don't have to wait hours while your log files get reprocessed. If you know a little SQL, that's even better. You can drill down into the details of a report. With LogJam, you can see exactly why one page gets so many hits from search engines or why one browser is so popular. Runs great on shared hosting accounts. There are no EXEs or DLLs to install. And you don't have to wait for your log files to download. Finally, Verio, DataReturn, and Interland customers have a choice. Requirements LogJam requires a Windows web server that supports ASP. See Requirements for more details. Who is LogJam for? LogJam is designed for a very particular kind of techie. Primarilly, LogJam is for the webmasters that are unsatisfied with the traffic analyzers they are given. Small to Mid-Sized Sites: Unlike other traffic analyzers, LogJam won't spend hours loading in log files. It's limited to about 10 minutes. That limits the amount of log files you can analyze. That's about 30megs on a 1ghz machine. For this site, that covers a month or two for this site but might be a day or even less for others. That's about 200,000 total hits (including images), 50,000 page views, or 10,000 visitors. SQL Helps: LogJam is for technical webmasters. Although it is easy to design reports without knowing SQL, it helps. That's not to say you can't learn. But you need to be prepared for that. What really makes LogJam different is that it's a good old relational database that you can run queries on. Every other traffic analyzer, in an effort to handle far more data, focuses on efficiency by generating only static reports at the cost of flexibility. But flexibility has it's advantages. With LogJam, every report is generated upon request.