> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/order-types/trailing-stop-orders.md). # Trailing stop orders Use a trailing stop to protect a position after a selected activation price A trailing stop follows a position after price reaches the activation level you select. It is useful when you want to protect a move without choosing a fixed stop price for the entire trade. ## Enable a trailing stop 1. Open the [Trade form](/terminal-sections/trade-form.md) or a position's TP / SL controls. 2. Enter the stop activation price. 3. Turn on **Trail**. 4. Review the projected stop and submit the order. When Trail is enabled, the stop fields are shown as **Trail Start** and **Start PnL**. The price is the activation price. It is not a trailing distance or percentage. You can preview the activation level on the [Chart](/terminal-sections/chart.md) before submitting. ## Venue support Trailing stops are currently available for connected Bybit and OKX accounts. Support depends on the active exchange, market, account, and order action. If the active venue does not support trailing stops, the Trail control is not shown. Review the exchange's own trailing-stop rules for movement, triggering, and execution behavior. Related pages: [Trade form](/terminal-sections/trade-form.md), [Positions](/terminal-sections/positions.md), [Chart](/terminal-sections/chart.md), [Supported exchanges](/features/supported-exchanges.md). --- # 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://docs.proliquid.xyz/order-types/trailing-stop-orders.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.