ServiceNow CPQ usage calculation

  • Release version: Australia
  • Updated June 2, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of ServiceNow CPQ usage calculation

    ServiceNow CPQ usage calculation tracks user interactions with the CPQ Configurator and Sales CRM features to provide accurate product usage measurement. Two primary metrics—user count and configuration count—are collected daily and displayed in the Usage Intelligence dashboard under Usage Analytics. These metrics help ServiceNow customers monitor feature adoption and engagement within their instances.

    Show full answer Show less

    Key Features

    • User count metric: Reflects the number of active users with access to ServiceNow CPQ and Sales CRM features. It combines users from CPQ microservices and Sales CRM sysuser table filtered by relevant product roles. Only active Fulfillers and conditionally business stakeholders are counted; requesters and inactive users are excluded.
    • Configuration count metric: Counts each instance of configuration initiation, including those abandoned or completed. This means starting a configuration increments the count regardless of deployment success.
    • ServiceNow CPQ Users table: A remote table consolidating user data from CPQ microservices and Sales CRM, showing usernames, corresponding user records, and subscription roles. This table depends on a configured CPQ microservices connection.
    • Data freshness and caching: The Users table caches data for 24 hours to reduce microservices queries, so recent changes might not appear immediately after updates or deployments. The cache refreshes automatically after expiration.

    Prerequisites and Requirements

    • A configured and available ServiceNow CPQ microservices connection on the instance.
    • Application scope set to CPQ Integration when accessing the CPQ Users table.
    • Users must have appropriate ServiceNow CPQ Sales CRM product roles to be included in user counts.
    • Additional conditions are detailed in the related knowledge base articles for accurate metric population.

    Practical Implications for ServiceNow Customers

    By understanding and leveraging these usage metrics, customers can:

    • Monitor active user engagement with CPQ and Sales CRM features to optimize license usage.
    • Track configuration activity to gauge adoption and process throughput.
    • Use the consolidated CPQ Users table as a single source of truth for user roles and access levels.
    • Anticipate potential data latency due to caching when reviewing recent user or configuration changes.

    ServiceNow CPQ usage metrics track how users interact with ServiceNow CPQ Configurator and Sales Customer Relationship Management (Sales CRM) features. These metrics support accurate usage measurement.

    Usage metrics

    Two usage metrics are collected for ServiceNow CPQ: user count and configuration count. These metrics are visible in the Usage Analytics area of your ServiceNow CPQ instance and are used to measure product usage across ServiceNow CPQ Microservices and Sales CRM.

    Metric data is collected daily and displayed in the Usage Intelligence dashboard. When viewing metrics, select Last full day or Last 7 days to confirm data is available, as a default filter of the current day may return no results if the daily collection has not yet run.

    Prerequsites and Requirements

    For ServiceNow CPQ telemetry metrics to function correctly, the following conditions must be present:

    • A ServiceNow CPQ microservices connection must be configured and available on the instance.
    • The application scope must be set to CPQ Integration when accessing or validating the ServiceNow CPQ Users table.
    • Users must hold the required ServiceNow CPQ Sales CRM product roles to be included in the user count.

    For the full list of conditions required for metrics to populate, refer to the associated knowledge base articles.

    User count

    The user count metric reflects the number of active users who have access to ServiceNow CPQ or Sales CRM features on your instance. This count combines users from two sources:

    • ServiceNow CPQ users fetched from ServiceNow CPQ microservices connected to your instance.
    • Sales CRM users from the Sales CRM sys_user table who hold relevant ServiceNow CPQ or Sales CRM product roles.

    The combined count appears in the ServiceNow CPQ Users table, which provides a single view of all users with access to ServiceNow CPQ and Sales CRM functionality.

    Which users are counted

    Not all users in the sys_user table are included. The user count tracks active Fulfillers as licensed seats. Business stakeholders are counted conditionally, based on their activity. Requesters aren't included in the user count.

    The user count and configuration count metrics are complementary: Fulfillers are measured as seats in the user count, while non-Fulfiller users such as business stakeholders are reflected through configuration records in the configuration count.

    Note:
    Inactive users are excluded from the count.

    ServiceNow CPQ Users table: The ServiceNow CPQ Users table is a remote table that queries both ServiceNow CPQ microservices and the Sales CRM instance to populate user data. The table includes the following fields:

    • CPQ user: the username from ServiceNow CPQ microservices.
    • User: the corresponding record in the Sales CRM sys_user table, populated when a matching user is found.
    • Role type: the subscription role associated with the user.

    The table may be empty if the required ServiceNow CPQ microservices connection is not configured or available on the instance. Several conditions must be met for the metric to populate correctly; refer to the associated knowledge base article for the complete list of requirements.

    Configuration count

    Each initialization of configuration is counted whether it's just initiated, abandoned or completed.

    The act of initiating a configuration is sufficient to increment the count, regardless of whether the deployment completes successfully. After a Blueprint is deployed, it is set to available for use in customer-facing sales scenarios.

    Data freshness and caching

    The ServiceNow CPQ Users table uses a built-in cache to avoid repeated queries to ServiceNow CPQ microservices on every request. The cache has a time-to-live (TTL) of 24 hours. As a result, data in the table may not reflect the most recent changes immediately after a deployment or user update. After the cache expires, the next request reruns the query and refreshes the table data.

    This cache behavior is part of the remote table configuration and is not controlled by a system property.