Conditions switching is not working in experience editor. enter image description here But if I remove the content part from default rule conditions switching works properly. Any suggestions please?


2 Answers 2


The default state should not have a selected content item. It should be empty. The component will use the data source that was selected when you set-up the component. The UI is a little misleading.

Select your default content when you drop the component on the page. Then set-up your personalization conditions. It should work then.

enter image description here

  • I tried the same. But if I am selecting default content while dropping component on the page in experience editor. After saving it and reloading the page, same issue is appearing. Is there any way to switch conditions with content in this default rule in content editor?
    – Mittal
    May 16, 2020 at 18:17

You can use the default rule to set a default data source for your rendering or hide it if you want. also, try to clear the data source field on rendering control properties:

enter image description here

You can use experience editor rendering web button to test the two conditions you have as you can see in the following screenshot:

enter image description here

Also, you can use explore mode to try testing, I noticed you are using a country personalization, so make sure Sitecore GeoIp service is working fine, double check if you should use country name or country code in your rule condition.

Another suggestion is to use a different OOTB personalization rule to identify if this issue is with the country rule.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.