Processing Rule Not Working: Query String Parameters

[icontre1]

Hello,

I have an existing processing rule looking at a query string parameter that overwrites the value of a prop.

The prop is populating values, but the strings I've tested are not coming up in the reports.

Thanks!

Ivan

[bjoern__koth]

HI @icontre1 

best would be if you paste a screenshot of your processing rule here, and maybe as well as test URL of yours.

[andreiabenites · Accepted solution]

It's hard to say without first seeing the processing rules you've created and what output you are expecting. Make sure your subsequent rules do not invalidate previous ones as processing rules cascade (are applied in the order listed). Sometimes it's just a matter of adding conditions to the Then do the following or Otherwise do the following areas.

Concepts to consider regarding Query string parameters:

1. Query string parameters cannot be read beyond the first 255 characters of a URL if you are running JavaScript AppMeasurement H.25.2 or earlier. JavaScript AppMeasurement H.25.3 and later provide the full URL including all query string parameters to processing rules.
   1. Upgrade to H.25.3 or later, or read query string parameters from long URLs client-side and store values in Context Data variables.
2. Query string values must be encoded in Unicode or UTF-8 to be read by processing rules.
   1. This might affect multibyte characters that are passed using query strings.