Hi,

Thank you for the details, it helps a lot!

I checked the filter configuration, and I found two issues with the state and age group filters. The operator was set to “EQUALS”, while these fields are non-numerical. I changed them here: https://i.imgur.com/yMaQFWx.png

Another issue was, that the age group filter contains values which may cross-match. For example “7u” also matches string “17u”. These values are stored in the database as a serialized array, but the SQL query can only compare them as strings.
To bypass that, I made an adjustment to the field, and entered the values manually, and added a double quote to the beginning of each: https://i.imgur.com/FOjthX1.png
In the actualy field storage the fields are stored with double quotes at start, this ensures that the fields match at the actual beginning of the serialized string.

It should be okay now.

You are welcome!

1. You can add normally before/after as if it was used wihtout the get_values syntax:

||Choose one/any
{get_values}
my_custom_value1||Custom value 1
my_custom_value2||Custom value 2

2. By default the connection is “AND” between the groups. You can change that here to “OR”, in that case either of the values matching is enough independently.