---
schema_version: "1"
id: c5352f8557b57ddaf6963c40a3be169a54552541e4225cdb708abbe908a10f4b
title: Telemetry in Connector Builder
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/connector-builder/telemetry.md
canonical_url: https://docs.mulesoft.com/connector-builder/telemetry
source_site: docs.mulesoft.com
content_type: documentation
content_hash: abfb36ae39434b4a0413cf4a88fa95e818dad23a7708270e4491fc73d8a6102c
description: MuleSoft Documentation Site
latest: true
---
---
product: Connector Builder
version: master
---

# Telemetry in Connector Builder

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Connector Builder can send a small amount of usage telemetry that helps Salesforce understand which
features are most useful and where to invest. It’s limited to product-usage signals and doesn’t
collect the content you work on.

Telemetry runs in the background and never affects your work. If Connector Builder can’t collect or
send telemetry for any reason, Connector Builder skips it and continues normally.

## Telemetry Data

This table shows what Connector Builder reports and what it doesn’t.

<table><colgroup><col> <col></colgroup><thead><tr><th>What Connector Builder Reports</th><th>What Connector Builder Doesn’t Collect</th></tr></thead><tbody><tr><td><div><div><ul><li><p>That a connector project was successfully created.</p></li><li><p>Where you started the action: the Connector Builder UI in VS Code or the <code>uc_generate_connector</code> MCP tool. Connector Builder records this as a category, not free-form text.</p></li><li><p>The installed version of the Connector Builder extension, so that Salesforce can understand usage for each release.</p></li></ul></div></div></td><td><div><div><ul><li><p>Source code or connector definitions, including generated project contents and draft project contents beyond how the project was started.</p></li><li><p>API specification contents, including source code, schemas, and examples.</p></li><li><p>Names and identifiers from your project, including connector names, vendor names, package names, and group IDs.</p></li><li><p>API endpoint URLs written into the generated project.</p></li><li><p>File or folder paths, including project, workspace, and output locations.</p></li><li><p>Personal, company, or account identifiers, including your identity, your Salesforce org, your user account, and your machine.</p></li><li><p>Credentials or secrets, including tokens, keys, and passwords.</p></li><li><p>Error details or free-form text, including error messages, stack traces, log output, and text that you type.</p></li></ul></div></div></td></tr></tbody></table>

Connector Builder counts only successful actions. If a project isn’t created because the operation
fails or is interrupted, Connector Builder reports nothing. It doesn’t count attempts or failures as
usage.

## Enable or Disable Telemetry

Connector Builder follows the standard VS Code telemetry setting (`telemetry.telemetryLevel`) and
checks it before sending anything. Connector Builder has no separate telemetry switch, so this
setting is the single control. To enable or disable telemetry, set the telemetry level to one of
these values:

- `off`: Connector Builder sends nothing.

- `crash`, `error`, or `all`: VS Code sends increasingly detailed telemetry. Connector Builder sends
  its usage signals at any of these levels.

Set the telemetry level in the Settings UI or in `settings.json`. The change applies immediately.
You don’t need to reload or restart VS Code. For more information, see the
[VS Code telemetry documentation](https://code.visualstudio.com/docs/configure/telemetry).

### Use the Settings UI

1.  Go to VS Code Settings.

2.  Search for `Telemetry`.

3.  Set **Telemetry: Telemetry Level** to your preferred value.

### Use settings.json

To set the telemetry level in `settings.json`, add the `telemetry.telemetryLevel` property:

```json
{
  "telemetry.telemetryLevel": "off"
}
```