You can update statistics about as often as you'd like, provided new log data is available for Urchin to see.
Take a look at the Run/Schedule tab under Profile Settings in the Configuration menu. You can choose monthly, weekly, daily or hourly, and you can also schedule a time to begin processing logs, whichever schedule period you choose.
Or you can click "Run Now" to schedule log processing immediately. In any case, Urchin will skip portions of log files already processed, provided Log Tracking is enabled in the profile settings.
-Jeff
--
You received this message because you are subscribed to the Google Groups "Urchin 6" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
urchin-help-...@googlegroups.com.
To post to this group, send email to
urchin...@googlegroups.com.
Visit this group at
http://groups.google.com/group/urchin-help-6?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Short answer is, I don’t use that report. I get my page views by page from the "Top Content" report, and my page names never have query arguments.
If your pages look like:
/one.html
/two.html
/index.html
They should all show up in Top Content with distinct page view counts. Are you saying you need to count pages with different query terms as distinct pages? Such as if your page names look like:
/display?page=one
/display?page=two
/display?page=index
There's an article in the online help that gives clues on how to do this—I'll paste the contents here:
How can I display the full URI including query terms in one report?
In Urchin 6, query patterns are displayed in a special drill-down 'Content Optimization -> Content Performance -> Page Query Terms.' If you prefer to display the full page and query pattern in the 'Top Content' report, you can use the filter below to change the way this data is displayed.
Note: This will increase the processing time for any profile it is applied to. Also, because of the increase in unique page names, your database limit may be exceeded.
Create a new 'Profile Filter' with the following settings:
· Filter Type: Advanced
· Filter A: request_stem (AUTO) - Extract A (.*)
· Filter B: request_query (AUTO) - Extract B (.*)
· Output to: request_stem (AUTO) - Constructor $A1/$B1
· Override Output Field: 'Yes'
· Required Fields: 'Both Fields'
· Case Sensitive: 'No'
It helps if you can explain in more detail what you're trying to do, with examples if possible. Otherwise I have to guess…