Fixed in 4.24.0: unknown targeting condition types now evaluate to false. If you run a server-side SDK below 4.24.0, upgrade. Defensive habits that survive any SDK version: (1) never mix web-only conditions (page URL patterns, device/browser web conditions) into segments evaluated by a server SDK - build server-specific segments; (2) after upgrading, re-run your targeting QA because evaluations that previously (wrongly) returned true will now return false and visitors move to default variations.

Context: Official Kameleoon changelog (kameleoon-new/client-csharp, 4.24.0): a targeting condition of an unknown type evaluated to true instead of false. The changelog documents the real impact: visitors were targeted by segments containing web-specific conditions the server SDKs do not support, so server-side flag evaluations silently matched the wrong audience.