Forums & Blog

Hello folks,
I have an issue that has been affecting our reporting for quite some time.  Our site is very busy, and we utilize a large number of pages with querystrings to bring up various content.  For example:

domain.com/viewPage.cfm?id=101
domain.com/viewPage.cfm?id=102
domain.com/viewPage.cfm?id=103

The issue is our management team would like hits based on EACH page/EACH querystring id.  The trouble we are running into is that the Data Mining query of "What query strings were passed to this file?" must parse thru ALL the various querystrings and returns stats on ALL the various querystrings for the viewPage.cfm.

So we are currently seeing the report show something like:
id=101   4,000 hits
id=102   6,400 hits
id=103   3,560 hits

Because our site is very busy, the report above takes an extremely long time to run.  For a weeks report, it will sometimes will take 2-4 minutes.  For pulling back a months timeframe for the report, it has sometimes taken 10 minutes+, othertimes it has crashed the SmarterStats service.

Ideally, what we would like to specify is:  "Give me details on viewPage.cfm for ONLY querystring id=102"? 

Is there anyway to accomplish this without pulling back ALL the data for viewPage.cfm? 
We need a solution that is ALOT faster than what we currently have for individual content pages / individual querystring ids.

Thoughts??

Hi,

I'm running into the same issue.  Did you ever get a response on how this type of data mining report could be set up?

In my case, I'm using a content management system, and *all* of the pages on the site are accessed through /am/template.cfm, where each individual page is called by a query string behind that URL, as in:

/AM/Template.cfm?Section=Journal&Template=/CM/HTMLDisplay.cfm&ContentID=3657

/AM/Template.cfm?Section=Tomorrows_Techology_Transfer_Summer_2009

/AM/Template.cfm?Section=Journal_Back_Issues&CONTENTID=1707&TEMPLATE=/CM/ContentDisplay.cfm

So data mining becoming next to impossible unless the definition of a data mining report can allowing the query strings to be included in the 'file path' field.

Thanks,

Michael

Unfortunately no solution.  No word at all from SmarterStats.  Strange as this is a VERY common situation with alot of users I would imagine.  Let me know if you find out anything.