Set Up User Counting
Overview
The eyeo telemetry system enables user counting while maintaining privacy standards. No requests sent to data collection services contain any personally identifiable information.
Required Configuration
To implement user counting, developers must provide two essential gn arguments during the build process:
-
eyeo_telemetry_client_id -
eyeo_telemetry_activeping_auth_token
These values are supplied by eyeo following initial contact.
Implementation Example
gn gen --args='eyeo_telemetry_client_id="mycompany" eyeo_telemetry_activeping_auth_token="peyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9" ...' ...
Important Security Note
Warning: Keep your auth token secure. Never embed it in open-source repositories or documents. If your auth token is revealed, reach out to eyeo as soon as possible to receive a new token.
If these arguments remain unset, the application will still function normally, though eyeo cannot properly attribute user metrics to your product.
Optional Parameters
Additional configuration is available through:
-
eyeo_application_name -
eyeo_application_version
Optional Configuration Example
gn gen --args='eyeo_telemetry_client_id="mycompany" eyeo_telemetry_activeping_auth_token="peyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9" eyeo_application_name="My great browser" eyeo_application_version="111.24.0.1" ...' ...
When omitted, the system defaults to values retrieved from version_info::GetProductName() and version_info::GetVersionNumber() from the Chromium version_info.h header file.
Privacy Assurance
User counting doesn't transfer any PII or other identifiable data to eyeo, nor does it allow tracking or profiling of users by eyeo.
Source: Set Up User Counting