[no subject]

[Jason Linhart <jason@xxxxxxxxxxx>]

The simplest thing to do is to turn on "Include query string in
requests", on the Options configuration page. That will include the
content=xxxx part of the request in the content reports.

If you are using query arguments for other things, besides specifying
which page to display, including all of the query arguments might not be
the best approach. If you have Summary Plus you can use aliases to
remove the query arguments that you are not interested in tracking.

If you are using Summary SP Lite or SP you can turn off "Include query
string in requests" and use "Query tag to include in request", on the
sub-report Details configuration page instead. That allows you to get
the content=xxxx included in the request, while still allowing other
query arguments to show up in the CGI Arguments and Local Search reports.

Good Luck
Jason


Justin Carroll wrote:
> Basically everything is filtered through "content.html?content=whatever".
> 
> How can we setup Summary to track these queries individually so that we
> can see how many people are going to each page?

-- 
Jason@Summary.Net
--
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
    -- Peter van der Linden, Expert C Programming, Deep C Secrets
-------------
Go to <http://summary.net/list.html> to update subscription info.