If you are using a URL based filter to include parameters, you may fail out if you don't account for additional parameters not related to what you are looking for (unless you're already scrubbing the logs to force URI manipulations). Could you just be forgetting to account for extra parameters in the URL?

Not sure what you mean, but there is only one parameter being passed back to the page through the query string and that is the zip code.

For example the URL is

index.asp?Zip=43229

Okay so it appears now my report is not working at all.

So to summerize

Type: Standard Custom Report
Report Title: ASC Codes
Dimension 1: WT.ASCzip
Measure 1: Hits - not sortable, interval data not available
Filters: WT.ASCzip (Include)

Accumulation Type: On Event
Visitor History Dependency: No Dependencies
Express Analysis Compatibility: Compatible

Name: ASC Zip
Based On: Query Parameter: "WT.ASCzip"
When to Collect Data: All Hits
Multiple Values: No
Accumulation Type: On Event
Visitory History Dependency: Not Dependent
Express Analysis Compatibility: Compatible

Any help in figuring this out is appreciated.

This looks like a conflict. You stated that your URI is index.asp?Zip=43229 but you're basing your query parameter on WT.ASCzip

Do you have some JS code on the target page to convert the Zip variable to ASCzip?

Actually Zip is the Query (from the form), but then at the top of the page the following code is displayed.

<meta name="DCSext.WT.pozip" content="<%=Request.QueryString("zip") %>">

so this turns the zip into the WT.pozip variable for webTrends to use.

Okay, so I was successful in getting one report to work successfully. It pulls back the zip codes correctly. I setup an almost exact copy of the report for another section of the website, using a different dimension but for some reason I'm getting no hits.

One thing that needs to be checked is the 'Exclude activity without dimension data' in the report.

Will keep working on this. Got it to work in one place, not sure why its not working for the other.

quote:

Originally posted by Ironhide1975:
<meta name="DCSext.WT.pozip" content="<%=Request.QueryString("zip") %>">

This will definitely drive the switch for 'Exclude activity without dimension data'. Still, you are either getting no hits to pages with this variable (while that flag is on) or there's some other config issue.

Do you have access to the logs to confirm that this variable is actually present in the log files being passed to the analysis machine?

Another thought - could you have case sensitivity issues with your dimension definition?

Good morning,

So maybe this page wasn't getting any hits. I brought up the report this morning and I got 1 hit for zip codes. So the report appears to be working correctly now. I think applying a filter to the report at the beginning was the problem. Once I got rid of the filter, allowed exclusive data to be present and re-analyed the numbers seem to appear.

Thank you for your help.