The gathering of CLI analytics data is disabled by default, and must be enabled at the project level by individual users. It cannot be enabled at the project level for all users.
Data gathered in this way can be viewed on the Google Analytics site, but is not automatically visible on your own organization's Analytics site. As an administrator for an Angular development group, you can configure your instance of Angular CLI to be able to see analytics data for your own team's usage of the Angular CLI. This configuration option is separate from and in addition to other usage analytics that your users may be sharing with Google.
To configure access to your own users' CLI usage data, use the
ng config command to add a key to your global
angular.json workspace configuration file. The key goes under
cli.analyticsSharing at the top level of the file, outside the
projects sections. The value of the key is your organization's tracking ID, as assigned by Google Analytics. This ID is a string that looks like
You can choose to use a descriptive string as the key value, or be assigned a random key when you run the CLI command. For example, the following command adds a configuration key named "tracking".
ng config --global cli.analyticsSharing.tracking UA-123456-12
To turn off this feature, run the following command:
ng config --global --remove cli.analyticsSharing
You can add a custom user ID to the global configuration, in order to identify unique usage of commands and flags. If that user enables CLI analytics for their own project, your analytics display tracks and labels their individual usage.
ng config --global cli.analyticsSharing.user SOME_USER_NAME
To generate a new random user ID, run the following command:
ng config --global cli.analyticsSharing.user ""
© 2010–2019 Google, Inc.
Licensed under the Creative Commons Attribution License 4.0.