"Exclude a Request URI" log processing rule does not exclude URIs with query strings

Problem reported by Massimo Bandinelli - Today at 3:58 AM

Submitted

SmarterStats build: enterprise 8761 (dic 27, 2023)

Log format: NCSA (IIS)

We need to exclude hits whose query string contains specific values (affiliate traffic, e.g. utm_term=DiscountHero) from a sub-site.

The primary site processes all logs with no rules, as recommended.

What we tried on the sub-site

Log Processing Rule "Exclude a Request URI" with the URI exactly as it appears in the raw log: /?utm_medium=affiliate&utm_campaign=cloud-prova&utm_source=tradetracker&utm_term=DiscountHero Full reprocess: no hits excluded.
Same rule with parameters in alphabetical order, as shown in the Query Strings report: /?utm_campaign=cloud-prova&utm_medium=affiliate&utm_source=tradetracker&utm_term=DiscountHero Full reprocess: no hits excluded.
Filter Set with the URI in the Excluded Items field, in both orders, without the leading "/?", and with wildcards (*utm_term=DiscountHero*): no effect on the Pages report.

IP exclusion rules added in the same reprocess work correctly (the excluded IPs no longer appear in reports). Log Import Status shows all rows as good rows.

Questions:

Does "Exclude a Request URI" match the query string, or only the URI stem?
If it matches the query string, what exact format and matching type (exact, prefix, wildcard) does it expect?
Is there any supported way to exclude hits based on a query string value at log processing time?
Would defining a Query Variable (page "/", variable "utm_term") make an exclusion rule such as "/?utm_term=DiscountHero" work?

Thanks in advance to whoeven can help.

Back to Community Threads

Reply to Thread

Enter the verification text