Telemetry
Altus Telemetry
Diagnostic telemetry data is used to keep Altus secure and up-to-date, detect, diagnose and remediate problems, and also make product improvements.
Our telemetry collects:
- Metadata: Data about customer data, e.g. counts of the types records in use.
- Performance Data: e.g. How long do operations take? How long to pages take to load?
- Behavioural Data: e.g. What features are most popular? How do users prefer to work with their data?
This data does not include:
- Personal Data: e.g. a user’s name or email address
- Customer Data: e.g. the content of the user’s files, or the contents of projects, programs or portfolios managed by the product
Our system uses a unique ID associated with user’s diagnostic data. For example, if we receive diagnostic data showing that one of our apps crashed 100 times, this unique ID lets us determine if it was a single user who crashed 100 times or if it was 100 different users who each crashed once. We don’t use this unique ID to identify a specific user.
Altus uses Microsoft Application Insights for Telemetry collection management and storage. Altus collects the following telemetry data items in addition to the default items collected by Microsoft Application Insights:
- Tenant ID
- Tenant Name
- Application ID
- Application Name
- Organisation Unique Name
- Organisational Currency ID
- User ID (guid)
- User TimeZone offset
- User Security Roles
- Browser Language
- Table Type Displayed
- Event Type Action
- Dataverse Storage Metrics
Note
Altus will never share user identifiable or organisational specific telemetry with a 3rd party unless required to do so by law, or via express written permission.
Platform Vendor Telemetry
In addition to telemetry collected by Altus, platform vendors integrated into the Altus experience may also collect telemetry. The sections below provide detailed information on what each vendor collects, how data is stored, and their security and compliance posture.
Userback (User Feedback Tool)
Userback is used within Altus to collect user feedback, bug reports, and satisfaction ratings.
What Userback Collects
User-Provided Data:
- Feedback content (star rating)
Technical / Browser Data:
- Device type and browser version
- Screen resolution, screen size, colour depth
Usage Context:
- URL of the page where feedback is submitted
- Time of visit
Userback Security & Compliance
| Aspect | Detail |
|---|---|
| Certification | SOC 2 Type II |
| GDPR | Compliant |
| Encryption (at rest) | AES-256 |
| Encryption (in transit) | 256-bit TLS |
| Data Storage | Amazon Web Services (AWS) |
Reference Links:
- Userback — Security Information
- Userback — Trust Center
- Userback — Privacy Policy
- Userback — GDPR Commitment
- Userback — Privacy and Cookies (Help Center)
How to Disable Userback
Userback can be disabled via the FeedbackOptOut configuration setting. This setting is managed in the Settings Area → Configuration Settings within Altus (see How to add Telemetry settings below).
| Setting | Value | Effect |
|---|---|---|
FeedbackOptOut |
Any value (e.g. true) |
Disables all user feedback collection, including Userback and feedback rating prompts. |
Product Fruits (Product Help Tool)
Product Fruits is used within Altus to provide in-app user onboarding, guided tours, hints, announcements, and checklists.
What Product Fruits Collects
Required Data:
- A unique user identifier hashed anonymised identifier based on the User's Power Platform UserID.
Optional User Attributes (explicitly passed by the customer):
- User roles, sign-up dates, or other custom properties — only collected if the customer chooses to send them to Product Fruits.
Product Interaction Data:
- Tours the user has finished or skipped
- Hints that have been displayed to the user
- Announcements the user has read
- Checklists the user has completed or dismissed
Feedback Data:
- Submitted feedback is stored on Product Fruits servers.
Technical / Log Data:
- Technical logs of user activity within the Product Fruits platform
- IP address of the account
What Product Fruits Does NOT Collect
- Product Fruits states: "We only track data necessary to operate Product Fruits and data that you explicitly consent to us tracking."
- They present aggregate behaviour patterns (e.g. which features are working, where users struggle) — not individual-level tracking of who clicked what.
- Customer data is never used for advertising, resale, or AI model training.
- Cookie-less tracking is supported.
Product Fruits Security & Compliance
| Aspect | Detail |
|---|---|
| Certifications | ISO 27001, ISO 27701, SOC 2 Type 2 |
| GDPR | Compliant |
| HIPAA | Report available |
| Encryption (at rest) | AES-256 |
| Encryption (in transit) | TLS 1.2+ |
| Data Storage | Amazon Web Services (AWS), default region: Ireland (EU) |
| Data Processing Addendum | Agreed upon account creation |
Reference Links:
- Product Fruits — Privacy Policy
- Product Fruits — User Data, Security & GDPR
- Product Fruits — Security & Privacy
How to Disable Product Fruits
Product Fruits can be disabled via the cloudServices configuration setting. This is a JSON-based setting managed in the Settings Area → Configuration Settings within Altus (see How to add Telemetry settings below).
Set the Enable Product Help property to false within the cloudServices setting value:
{
"productHelpEnabled": false
}
| Property | Value | Effect |
|---|---|---|
productHelpEnabled |
false |
Disables Product Fruits entirely — no tours, hints, announcements, or checklists will be loaded. |
Telemetry Settings
An Altus customer can opt out of telemetry via settings in the Altus configuration settings area. There are two settings related to telemetry, InstrumentationKey and TelemetryConnectionString.
Either a key or a connection string may be provided. If both are provided, the connection string takes priority. If the setting is set to 'false', then telemetry will be disabled.
| Setting | Description |
|---|---|
| InstrumentationKey | Used to provide the instrumentation key. If set to 'false', telemetry collection is disabled. |
| TelemetryConnectionString | Used to provide the connection string. If set to 'false', telemetry collection is disabled. |
| FeedbackOptOut | If set to 'true', disables the collection of user feedback. |
User Feedback Prompts
As of version 2022.05.31.3, users will periodically be prompted for feedback ratings in Altus. Customers can modify the cadence of feedback rating prompts to users. Note that if FeedbackOptOut is set to true, no prompts will occur regardless of the cadence setting.
| Setting | Description |
|---|---|
| userFeedbackCadence | Sets the number of days between feedback rating prompts. First-time users will be prompted after 30 days. The default cadence after the first prompt is 90 days. Setting this value to 0 will disable feedback prompts. |
How to add Telemetry settings
The above settings are not provided by default, so if needed they should be created manually.
- Open the Settings Area -> Configuration Settings
- Press the "New" button
- Enter the desired setting name from above in the "Name" field.
- Enter the desired value in the "Value" field.
Example to disable periodic feedback collection:
Telemetry for Documentation Usage
Content served by this website utilises the following telemetry services:
- Google Analytics
- LinkedIn Analytics
Dataverse Analytics
Microsoft provides built-in analytics for Dataverse, giving administrators visibility into usage, performance, storage, and overall system health across their environment. This helps support monitoring, optimisation, and informed decision-making.
For more information, refer to the official Microsoft documentation