> 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/dry-mode-lab.md).

# Dry mode (lab)

{% hint style="info" %}
This feature is flagged to "**LAB**" (aka Laboratory feature), it means that interfaces are not definitive and may evolve in the future.

This feature is currently in private preview.
{% endhint %}

The Dry mode allows you to simulate sending events, **but events are not sent** to the destination.

Once this feature is activated, all outbound HTTP requests of the destination are mocked in order to test it before going live. The payload, the request, is visible in Event Inspector to let you see events and correct the format if needed.

As soon as you deactivate the dry mode, events will be sent to the destination.

When available, a switch is displayed on the destination interface:

<figure><img src="https://1259070148-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mk6XpTQ2LaRLcr2tA-d%2Fuploads%2Fgit-blob-fc8636b469428cdad714bca30b7e207fc97d495a%2Fdestination_dry_mode_settings.png?alt=media" alt=""><figcaption></figcaption></figure>

The 'Use real authentication' option allows you to test your credentials by not mocking potential authentication requests. It is only applicable to some destinations, such as Google Enhanced Conversions or Snapchat.


---

# 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/dry-mode-lab.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.