User privacy, tracking, and user consent management in Usage Insights

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture

    • Usage Insights relies on tracking user activity to measure the adoption, retention, and usage of KPIs to help you make better product and implementation decisions.

    Tracking users in Usage Insights

    Usage Insights can be used to track user behavior across  ServiceNow Core UI, Next Experience, Portal, and Mobile applications.  Usage Insights used on web and mobile applications collects limited information about the users themselves.

    Usage Insights doesn’t store the user ID. Instead, it uses a one-way SHA256 hash of the sys_id, stored on the sys_user_table as “Hashed User ID”, to identify the same user consistently across multiple devices. This way, Usage Insights can anonymize users while retaining the ability to connect individual users to their session data consistently. This one-way hash also enables customers to reconnect their Usage Insights data to personally identifiable information available on the sys_user table if they choose.

    The hash isn’t salted intentionally. This way, customers can obtain the ID of a specific user they want to track, apply a SHA256 on that ID (for example, here: SHA256 calculator), and then use the output to filter the data for a specific User ID.

    By default, Usage Insights translates the end user's IP address to a city level location, which is stored. However, the IP address isn’t stored.

    Remarque :
    Geolocation information may be considered personally identifiable information (PII).

    Administrators can configure analytics tracking preferences across all tracked applications via user consent management (UCM). This capability provides the flexibility to customize the consent policy for each country and to select how the location of the user is detected.

    Some of the options available to you with user consent management are:
    • Applying different tracking consent policies to individual countries.
    • Tracking specific users or tracking users with specific roles.
    • Defining how to detect your users’ location.