# Cockpit

Umbraco Engage includes a cockpit feature to help verify the tracking of analytics and understand personalization behavior. The cockpit adds a button to the front end, giving real-time insights.

As of Umbraco Engage 16, the cockpit is automatically added and visible for logged-in Umbraco users.

{% hint style="info" %}
Automatic injection of the Cockpit can be disabled by setting ‘**Engage:Cockpit:EnableInjection**’ configuration to **false** in your appsettings.json file.
{% endhint %}

When visiting the front-end website, the Umbraco Engage Cockpit will appear on the left or right side of the screen. The cockpit will only be rendered if the user is logged into Umbraco.

![Umbraco Engage Cockpit](/files/GinFGPCWifCbm37vvG42)

Clicking the **Open** button provides detailed information:

![Umbraco Engage Cockpit - Detailed information](/files/2zFfsdK2L0ypKB66MjvM)

If the Cockpit is missing and the Umbraco backoffice runs on a different domain, see the [Load Balancing and CM/CD Environments](/umbraco-engage/getting-started/for-developers/loadbalancing-and-cm-cd-environments.md) article.

## Opening the Cockpit in CM/CD Environments

In load-balanced setups where the backoffice runs separately, you can use the **Open Cockpit** button in the Engage dashboard to open the Cockpit. This provides secure authentication without requiring cookie domain configuration.

See [Load Balancing and CM/CD Environments](/umbraco-engage/getting-started/for-developers/loadbalancing-and-cm-cd-environments.md#cockpit) for detailed setup instructions.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.umbraco.com/umbraco-engage/getting-started/for-developers/cockpit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.