It seems a lot of this could be done with report customization settings in Analog or
Report Magic (although some of the reports you mentioned
tie log data to database data which really is a custom process and not applicable to
Analog):
Michael Roberts wrote:
> The first part
> starts off with a summary of site-specific "interesting pages" -- this list is
> in a quasi-hierarchical form, and includes hits to static pages, total hits to
> the machine tool databases, hits by area (the main Techspex area is cobranded
> for five other companies, so we do comparative traffic analysis to see whether
> their marketing is really buying us anything.)
This could be done in either Analog or Report Magic. I've written custom scripts to
read across an Analog CRO file (or set of mutually
exclusive files [if anyone is thinking of doing this, see previous thread about large
log files for warnings on this :) ]) and build custom
pages with lists of "interesting hits". I think this could be added to Analog fairly
easily, kind of a query report, but instead of showing
top results by floor, it would just show specific items. It wouldn't add anymore
information to track (it's part of the request data), but
could be a very useful tool. (Especially with customizations and allowing multiple of
these reports, e.g. Interesting Hits for Marketing,
Interesting Hits for Systems Admins, ...)
> Then we total up
> clickthroughs. We analyze how many hits are done by signed-on users as
> opposed to anonymous ones.
This would be a simple comparison of the General Summary and the User Report.
> Of signed-on users we check how many are "watched"
> users, i.e. not machine tool buyers but rather machine tool distributors or
> builders out to scope out their competition.
This could be a special version of the Referrer Report. You could do this in Analog,
by running a special run with just the "watched"
referrers, then script it to add it back to your reports.
> We do incredibly detailed analysis of number of hits to each advertiser's
> vital information, and searches executed on them, and similar but less
> detailed analysis of the tools searched for. (Odd. That seems backward but
> that's life, I guess.)
This could be done with specific runs of Analog using REQINCLUDE statements and
ARGSINCLUDE statements. Then combining it, via a script, with
your other reports.
> Total hits: 27638
Hmm.. Is this just the successful page requests (in Analog terms)? I'm worried about
running sites that log this many per hour. I realize your
market is small, so you may never reach that level of traffic, but what about
solutions for sites that do?
> Banner displays: Techspex proper: 9748
> Mach.tools onl: 81
> AMTDA: 2424
> EDMTT: 961
> M2M: 30
> Info requests: 46
>
This kind of thing might be able to be achieved in Analog with a custom report option.
I suppose it's really just another variation of the
Interesting Hits report, except for this you want to know the number of requests for
certain urls (and specific arguments). Add some aliases
and the report would look really nice.
> This *sort* of report I can imagine building into Analog, but it'd be pretty
> complicated to define it in general, and certainly difficult to configure with
> the existing named-value approach. It might be possible to do something with
> a more structured text document external to the .cfg file, a custom report.
> Interesting exercise. Who thinks it'd be worthwhile? I might be persuaded to
> do something like that in a couple of months.
It could easily be done on a proprietary (i.e. site by site) basis with a simple
script that parsed an Analog CRO file and outputted a new
report in CRO format. Then cat the whole thing and pump into Report Magic with a new
definition for what that 'custom' report means and what
parameters to attach to the formatting of it.
I think what you're really looking for here is a way to define a summary report that
takes specific items from other reports and puts them all
on one page. I don't think that would be to hard to script if you did it _after_
Analog processed the page. However, if the data falls below
the floor of its report, then you'd never find it. Adding it to Analog may be, as you
say, an interesting exercise. You would effectively need
to customize the output routines to process the data for one more, custom report and
output that inline with the rest.
I should point out the Report Magic has the ability (if you dig deep enough :) to
customize the reports that it can generate. Bringing this
more into the user scope is pretty imminent on the wishlist. So an add-on solution for
Analog that produced this report in HTML or CRO
(integrated into the Analog output, in either case) could also be useful with Report
Magic.
Jeremy Wadsack
Wadsack-Allen Digital Group
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
