Skip to main content

Customer Managed Telemetry

This capability allows you to output a workflow telemetry log file after you upgrade to Alteryx Designer 2021.4 (or higher). It enhances an organization’s ability to collect and record Designer usage data down to the individual workflow run per user. You can use the data to perform internal product usage analysis.


The telemetry XML files don't include information from the Results window. Information such as workflow run time, records read from and written to files, and any errors, warnings, or other messages are only included in the engine logs. To set up your logging directory to produce logs that include this information, go to Options > User Settings > Edit User Settings > General.

Governance Enterprise Utility Starter Kit

A new Enterprise Utility that features Customer Managed Telemetry is now available. This utility lets you process the telemetry data you've collected using this new feature in Designer into usable data. The utility also includes 2 sample dashboards that automatically populate with your data to streamline your journey to insight.

To download the utility, go to the Alteryx Markeplace.

Alteryx Protects Data Privacy

The resulting log files exported by Customer Managed Telemetry are not sent to Alteryx or consumed by Alteryx in any way. You can deploy Customer Managed Telemetry by editing administrator files as part of an Alteryx install. The use of this feature might subject administrators to obligations under local privacy laws. For example, the responsibility to disclose the collection of personal data. Alteryx does not require this feature to be turned on or control the use of this feature.

Telemetry Setup

  1. Open the RuntimeSettings file, typically located in the following directories. Please note that the below file paths are the default paths for Alteryx installations. Your version of Alteryx might be installed in a different location.

    • Admin Version: %ProgramFiles%\Alteryx\bin\RuntimeData\RuntimeSettings.xml

    • Non-Admin Version*: %LocalAppData%\Alteryx\bin\RuntimeData\RuntimeSettings.xml

      *Re-installing a non-admin version of Designer may override these settings.

  2. Ensure you have edit permission to the RuntimeSettings file.

  3. Add the below code to the RuntimeSettings XML file. Ensure that the Telemetry tag is nested under SystemSettings, but not under any other tag within SystemSettings.

    Note how the <Telemetry> tag in this image is its own entry nested in <SystemSettings> but not nested in the <Engine> tag. This is an example of correct placement.

    Image showing an example Telemetry entry inside of the SystemSettings tag.
    • You can set the file path to any existing path you want the XML to be stored. The example file below saves the files to a log folder within C:\ProgramData\Alteryx\Engine.

    • Also, note that the EnableCustomerManagedTelemetry tag and associated file path should be on one line. Don't place the tag in another section.

  4. Save your edits to the RuntimeSettings file and restart your computer.

Once users run a workflow, a full XML record is captured and stored in the file path that you set.

Information Captured

Customer Managed Telemetry is intended to be flexible and supports a variety of use cases. To deliver usage information, you can set up Alteryx to log the underlying XML file of a workflow to a local or network file path.

Note that the telemetry XML files do not include information from the Results window. Information such as workflow run time, records read from and written to files, and any errors, warnings, or other messages are only included in the engine logs. You need to set up your logging directory in Options > User Settings > Edit User Settings > General to produce logs that include this information.

These XML header tags are represented at the top of the log file:




Timestamp that identifies when the workflow was executed. Timestamp is in UTC with this format: yyyy-MM-dd'T'HH:mm:ss'Z'.


The user email submitted at the time of product activation.


The machine hostname.


Unique Run ID.


Fully qualified path for the file that was run.


The license key used to activate the product.

Additional Notes

  • WorkflowFilePath does not record a value until a workflow has been saved.

  • Ensure you have write access to the file path specified in runtime settings to successfully turn on this feature.