> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment identification for product analytics

Domino tags every product analytics event with two values that identify the deployment it came from:

* `customer_name` — your organization's name.
* `deployment_name` — a label for this specific Domino environment, for example `prod-us-east`, `staging`, or `dev-eu-west`.

We recommend setting both values, and keeping them consistent afterward. You can do this at install time or any time afterward by running the deployer; you don't need to wait for an upgrade. Doing so helps Domino Support quickly identify your deployment when you reach out, so we can resolve issues faster. Until they're set, telemetry events are still sent, but with an empty identifier. Domino cannot attribute those events to your deployment on its own.

<Note>
  Setting `customer_name` and `deployment_name` helps Domino Support identify your deployment. It does not give your team its own analytics, reporting, or filtering on this data.
</Note>

## How the values are resolved

Domino resolves `customer_name` and `deployment_name` from the first of the following sources that has a value, in order of priority:

1. A [configuration record](/6.3/admin/configuration/central-configuration) (highest priority).
2. The environment variable set from your installation configuration.
3. A built-in default of an empty string (lowest priority).

Configuration records are read at service startup, so after adding, changing, or deleting one of these records you must [restart the Domino services](/6.3/admin/configuration/central-configuration#restart-services) for the change to take effect.

## Set the value

Add the following to the `release_overrides` block of your installation configuration, then run the deployer:

```yaml theme={null}
release_overrides:
  nucleus:
    chart_values:
      config:
        dominoCloud:
          enabled: true
        keepEnvironmentsUpdated: true
        mixpanel:
          token: "REDACTED"
          customerName: "acme-corp"
          deploymentName: "prod-us-east"
```

<Warning>
  This `mixpanel` block, under `release_overrides.nucleus.chart_values.config`, is a different setting from the `mixpanel` block documented under [Telemetry](/6.3/admin/configuration/installer-configuration#telemetry) (`enabled` / `redacted_mode`). Adding `customerName` or `deploymentName` to the `telemetry.mixpanel` block described there has no effect and will be rejected. Set them here instead.
</Warning>

This renders as the `DOMINO_TELEMETRY_CUSTOMER_NAME` and `DOMINO_TELEMETRY_DEPLOYMENT_NAME` environment variables on the nucleus deployment.

## Change the value afterward

There are two ways to change either value after your initial install:

1. **Update your installation configuration and re-run the deployer** (preferred).\
   Change the values in the `release_overrides` block (as explained under [Set the value](#set-the-value)) and re-run the deployer. The deployer only reconciles the configuration that changed, it does not redeploy your entire cluster.
2. **Set a [configuration record](/6.3/admin/configuration/central-configuration)**.\
   You can use this override if you can't re-run the deployer right away, for example if a change-control process limits how often you're able to run it. You don't need to wait for your next deployer run to update the values:

   | Configuration record key                      | Sets              |
   | --------------------------------------------- | ----------------- |
   | `com.cerebro.domino.telemetry.customerName`   | `customer_name`   |
   | `com.cerebro.domino.telemetry.deploymentName` | `deployment_name` |

   As with any configuration record change, you must [restart the Domino services](/6.3/admin/configuration/central-configuration#restart-services) for the update to take effect. Deleting a record reverts that field to the value set in your installation configuration.

## What to enter

* `customerName` — a stable name for your organization, such as the account name on your Domino license or contract.
* `deploymentName` — a free-text label you choose to tell one environment apart from another, for example `prod-us-east`, `staging`, or `dev-eu-west`. Keep it consistent across upgrades.

## What data is being captured

<Note>
  Product analytics telemetry does not include file contents, code, datasets, or other project data, only the categories below.
</Note>

Product analytics telemetry can include:

* Identity information used to attribute events to your organization and users.
* Version and build information for the reporting service.
* In-product actions taken by users, along with metadata describing each action.

Enabling redacted mode (`mixpanel.redacted_mode` in the [install configuration reference](/6.3/admin/configuration/installer-configuration#telemetry)) removes email addresses and reduces names to initials.

<Note>
  This is separate from Fleetcommand telemetry, which reports installation and cluster health data to Domino for support purposes. See [Deployments telemetry](/6.3/admin/configuration/deployment-telemetry).
</Note>