> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/destinations/add-destination.md). # Destinations overview ## Destination list Find here the full list of [destinations](/getting-started/concepts.md#destination) already configured. You can search a destination by name and filter on environment (production or staging), status (active or inactive) or on specific source. ![](https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-e953ce73309b4d9f23522282d6014ea5c7121f56%2FDestination%20overview.png?alt=media) 4 sections are available: Cloud mode, Device mode, Audience and Raw Data. ### Cloud mode It refers to event based destinations that execute on the server (aka server-side tags): destinations that run in real-time and push your events (purchases, page views...). ### Device mode (soon) It refers to destinations that needs to be executed in the browser (aka client-side tags). For example : survey tag, A/B testing, heatmapping tool, live chat, web notification, ...\ Currently, client-side tags are manageable in the web containers section. They will move progressively on the device mode section. ### Audience It refers to destinations that push user's segments, each time a user enter or leave a segment you created. ### Raw Data It refers to scheduled destinations, through file exchange like FTP, S3 or Cloud Storage. ## Trend and Health The trend represents the evolution of number of events pushed to the destination on the last month (maximum data retention period). Health allow to quickly visualize the status of the destination, if everything is well sent (sunny) or not (stormy) on the last hour.\ Click on it to access to Event Delivery interface and have more details (see also [Event Delivery documentation](/features/destinations/event-delivery.md)). ![](https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-9831c6aa6e1db04e9d37e9b8e565374c1162e245%2FCapture%20d%E2%80%99e%CC%81cran%202022-03-01%20a%CC%80%2015.13.05.png?alt=media) --- # 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://doc.commandersact.com/features/destinations/add-destination.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.