Why is my Experience showing on the wrong page?
If a Chameleon Experience appears on a page where it was not intended to show, the cause is almost always a URL rule that matches more pages than expected. This article covers how to diagnose an over-broad URL rule and fix it.
ℹ️ This article is about an Experience showing where it should not. If your Experience is not showing where it should, go here.
How to check which URL rule is causing the match
Open the affected Experience on your Chameleon Dashboard, and open it in the Builder.
Look for the URL Rules field. If it shows with a green check on a page where you do not want the Experience to show, the URL rule is matching that page unintentionally.
If you don't have any URL rules set up, consider adding one to control in which pages the Experience should show!
Common URL rule mistakes that cause wrong-page display
"Contains" rule matches too many pages
A Contains rule for a short string like /a, /app, or /dashboard will match any URL that includes that string — including routes you did not intend.
Example: A rule containing /settings will match /settings, /account/settings, and /admin/settings/billing.
Fix: Make the Contains string more specific, or switch to Is Exactly match if the path is stable. You can also use a Regex rule to define exact boundaries.
URL rule set at the wrong Step
URL rules can be set independently per Step. If you have a multi-Step Tour and only Step 1 has a specific URL rule, later Steps may default to a broader or empty rule and appear on unexpected pages.
Fix: Open the Experience in the Builder and check the URL rule on every Step individually. Set an appropriate URL rule on each Step that should only appear on specific pages.
Experience is set to show on all domains
If your account has multiple domains or Environments and the Experience is set to All Domains, it will appear across every domain where the snippet is installed and the URL rule matches.
Fix: In the Experience settings, use the Choose Environments setting to restrict the Experience to the specific domain or Environment where it belongs.
Still stuck?
💡 Tip: If you've checked your URL rules and things still aren't clicking into place, try describing the issue to Copilot and it can help you pinpoint the problem fast. Just share what you're seeing and Copilot will walk you through it.
If the URL rule looks correct but the Experience is still appearing for unintended users, check the audience Segment. Read Why is my Experience showing to the wrong users?.
Contact Chameleon support with the output of
chmln.debug("YOUR_EXPERIENCE_ID")and the URL where the Experience is appearing unexpectedly.