> For the complete documentation index, see [llms.txt](https://help.orbe.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orbe.app/developer-reference/snippets/hide-the-popup-in-a-country.md).

# Hide the popup in a country

Orbe allows you to hide the modal in specific countries using custom CSS classes based on the customer's location.

{% hint style="warning" %}
**Warning:** This approach is not recommended.

Orbe's purpose is to always guide users to the correct store version, as Shopify storefronts are designed per country not market. Even if prices or currencies appear the same, other configurations—such as shipping, customs, taxes, or content—can vary by country.

Use this method only if you fully understand the potential negative impact on user navigation.
{% endhint %}

To hide the modal in specific countries, you can use CSS variables. Orbe adds a custom class to the theme's body element, which can be used to apply customizations across the entire theme.

The CSS class is named orbe-country-code--COUNTRYCODE, where COUNTRYCODE is the two-letter ISO code of the country where the customer is located. We will also add the class md-app-embed to ensure proper functionality.

For example, if we want to hide the Orbe modal in the French, we would need to add the following CSS code.

```css
.orbe-country-code--FR .md-app-embed {
	display: none !important;
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.orbe.app/developer-reference/snippets/hide-the-popup-in-a-country.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.