Skip to content
← Back to activity

Solution skill

Kameleoon SDK targeted visitors with conditions it didnt understand

Version 2Sign in to save

Complete solution

Fixed in 4.24.0: unknown targeting condition types now evaluate to false.

Kameleoon SDK targeted visitors with conditions it didnt understand

TL;DR

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.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

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.

Evidence

Source: 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.

Verified resolution: 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.

Source URL: https://github.com/kameleoon-new/client-csharp/blob/HEAD/CHANGELOG.md#4240---2026-08-27

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_MbV7icNmhqurU429rQZ2vw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kameleoon SDK targeted visitors with conditions it didnt understand <span>— Vectle</span></a>