Skip to main content

Why is my Experience showing to the wrong users?

Learn how to identify and fix issues where a Chameleon Experience is displaying to users who shouldn't see it.

Written by Amanda Oliveira
Updated yesterday

If a Chameleon Experience is appearing for users who should not see it, the most likely cause is the audience Segment being too broad, a stale or incorrect property, or the Segment logic not matching your intent. This article covers how to identify which users are seeing an Experience and how to tighten targeting.


Common reasons an Experience shows to unintended users

Audience is set to "All Users"

If you set the Audience to the "All Users" Segment, that means the Experience matches every identified user. It will display to everyone.

Fix: Open the Experience in the Dashboard and assign a more specific audience Segment.

The Audience or Segment is too broad

A Segment that checks whether a property contains a value, or uses OR logic across multiple conditions, can match more users than expected.

Fix: Open the Segment in the Dashboard and review each condition. Confirm that every condition would exclude users who should not see the Experience. Consider switching OR conditions to AND to narrow the match.

Property type mismatch producing unexpected matches

Segment rules treat data types strictly. If your rule compares a property to a number but the property is being sent as a string, the match may behave unexpectedly.

Fix: Run chmln.data.profile.attributes in the console and check the data types of the relevant properties. Ensure the value type in the Segment rule matches exactly what is being sent in chmln.identify().

Stale data from a CSV import or integration

If user properties were imported via CSV or synced from an integration, those values may not match current live data if they were not updated. The stored property is what Chameleon evaluates β€” not your live system of record.

Fix: Check the user's profile in People in the Dashboard to see the property values Chameleon is using. If a property value is outdated, update it.

The wrong Segment is assigned

If the Experience has recently been cloned or has undergone audience changes, it may be using a Segment that was intended for a different Experience.

Fix: Open the Experience and review the assigned Segment name and its conditions carefully. Confirm it is the intended Segment.


Still stuck?

πŸ’‘ Tip: Not sure why your Experience is still targeting the wrong users? Try describing the issue to Copilot β€” it can walk you through your specific Segment setup and help you spot what's off. Sometimes a quick conversation gets you to the answer faster than digging through settings alone.

  • If targeting looks correct but the Experience is still showing to users who should be excluded, contact our Chameleon Support Team!

Did this answer your question?