> 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/general/integrations/announcement-bar.md). # Announcement Bar How to create a dynamic Marketing Announcement Bar which changes for each market using Orbe and Translate & Adapt Welcome to this tutorial on how to create a dynamic announcement bar for your store using Translate and Adapt and Orbe. This announcement bar can be customized to display different messages and personalize the shopping experience based on the country. For example, let's say you offer free shipping up to a certain amount in different countries. With the dynamic announcement bar, you can display a message specific to each country's shipping threshold, letting your customers know exactly how much more they need to spend to qualify for free shipping. Or perhaps in some countries, the price includes duties and taxes, while in others, they will be added in the checkout. You can use the announcement bar to display this information, ensuring that your customers are fully informed about their purchases. In this tutorial, we'll show you how to set up the dynamic announcement bar step by step, so you can start using this powerful tool to improve your store's customer experience. So, let's get started! {% embed url="" %} --- # 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/general/integrations/announcement-bar.md?ask=&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.