--- title: "Blocker does not appear for my end users" slug: "ive-created-a-blocker-but-it-isnt-showing-up-for-my-users" updated: 2025-11-03T03:08:01Z published: 2025-11-03T03:08:01Z --- > ## Documentation Index > Fetch the complete documentation index at: https://support.whatfix.com/llms.txt > Use this file to discover all available pages before exploring further. # Blocker does not appear for my end users ### Issue You [created a Blocker](/studio/docs/how-to-create-a-blocker), but it’s not visible on your application. ### Probable Causes - The Blocker segment is not pushed to Production or the correct segment is not in Production. - If you've pushed only the content and not the widget to Production. - Incorrect Visibility Rule conditions are configured for the Blocker widget. - If you have selected an incorrect UI element or a wrong CSS selector of the element for the Blocker. > [!NOTE] > Info: > > Incorrect Visibility Rules that are commonly used: > > - **Adding URL Equals instead of Contains**: When you use equals as a condition instead of contains, the Blocker is displayed only when the page's URL exactly matches the provided URL. Even if the page's URL is slightly different, the Blocker is not displayed on the page. > > ![Use contains when adding visibility rules Where](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Blockers_Visibility%20Rules_Where_Contains.png) > - **Selecting the rule as URL Path and adding the Domain name**: When a **Domain**name is added instead of the **URL Path**, the rule is not evaluated and the Blocker is not displayed. For more information, see [New Visibility Rules](/studio/docs/advanced-visibility-rules-for-widgets). > > ![Add URL path when adding Where conditions in visibility rules](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Blockers_Visibility%20Rules_Where_URLpath.png) > - When you are adding more than one Visibility Rule, ensure that the right operator is used. > > a. Use the **AND** operator when the Blocker needs to be shown only if all the conditions are evaluated as true. > > b. Use the **OR** operator when the Blocker needs to be shown if any one of the conditions is evaluated as true. > > ![Select AND or OR when adding visibility rules](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Blockers_Visibility%20Rules_AND_OR.png) #### If you're using the Whatfix Browser Extension for content delivery - The version number of the updated extension on the Whatfix dashboard does not match the version of the Whatfix extension in the browser extension page. #### If you're using the Whatfix Browser Extension for content delivery and the Preview extension to test content - There might be a conflict between the browser extension and the Preview extension after the Blocker is pushed to Production. The browser extension is enabled and the Preview extension is disabled. ### Suggested Solutions - Push your Blocker segment from the **Ready** stage to the **P****roduction**stage to make it live on the application. - Ensure that you push the widget first from the **Widgets** section, as this guarantees that the segment and its associated content are simultaneously published. For more information on pushing a widget to Production, see [Push Whatfix content and widgets to Production](/studio/docs/pushing-whatfix-content-to-production). - Use the correct Visibility Rule conditions to show your Blockers. Also, add the right conditions **AND/OR** if you are adding more than one Visibility Rule. - Re-select the correct UI element or use CSS selectors for the Blocker to appear correctly on the selected element. To understand how to identify an element’s CSS selector and what are good CSS selectors to add, see [Identify an element's CSS selector](/studio/docs/identify-an-elements-css-selector). #### If you're using Whatfix Browser Extension for content delivery - Check the updated extension's version number on the Whatfix dashboard and the Whatfix extension in the extension page. They need to be same so that end users can see the latest Whatfix content updates. If they are different, try updating the extension again and wait for some time for the extension versions to be in sync. For more information, see [How is the browser extension updated?](/studio/docs/how-is-the-browser-extension-updated) #### If you're using Whatfix Browser Extension for content delivery and Preview extension to test content - If there's a conflict between the browser extension and the Preview extension, enable and disable the [Preview extension](/studio/docs/use-preview-extension-to-test-whatfix-content). Refresh the application page and check if you're able to view the Blocker. > [!WARNING] > Note: > > If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Blocker%20does%20not%20appear&body=Hi%0A%0AThe%20Blocker%20that%20I%20created%20does%20not%20appear%20for%20my%20users.%20Kindly%20check.%20). ## Related - [Is Blocker WCAG compliant?](/is-the-blockers-feature-on-studio-wcag-compliant.md)