Skip to main content

About metrics

Metrics provide visibility and quantifiable measures to help you monitor the adoption of, demonstrate return on investment, and track growing impact.

Metrics help you answer questions such as:

  • How is the roll-out going?

  • Is your organization getting what you intended out of

  • How are users joining?

  • What organizations are they a part of?

  • How many user “Real Active Days” (RADs) per time period? (Note: RAD = 11 or more actions by a user in the platform in a given days.

How can you get access to platform metrics? can deliver the platform metrics information to you in two ways:

  • Request a special dataset (ddw-metrics dataset) to be added to your organizations in

  • Customers on single tenant and private instance installations can request the platform metrics data to be delivered to their Snowflake account using Private Marketplace Listing.


    To be able to use this feature, your Snowflake account must be setup as Consumer of listings.

Usage and Governance Reporting Categories

Table 1.  



Most useful metrics


These metrics capture event level details for interactions of users with different parts of the application. For example, you can find list of events that were generated when users created datasets and projects in the organization.


These metrics provide details about members of your organization. You can find information like when a member joined the organization, when did they last login, and how many queries, datasets, projects they have created in the application.


These metrics provide insights for resource such as, organizations, datasets, projects. For example, you can find a list of queries created in the organization, and a list of datasets that are synced with external data sources.


These metrics capture information like the most searched terms, most viewed resources, and the most engaged uses with the application.


These metrics capture details about how often the tool is used and by whom.

Time Zone

All dates and timestamps are based on UTC time zone.


API Event

Customer Real Active Day (CRAD)

  • The technical definition of a RAD (Real Active Day):

    • measured at the level of individual users

    • must be a return day (first day on platform is excluded)

    • ui_events + api_events > 10

  • We use RADs as a measure of engagement. As compared with a regular user day, a RAD requires a slightly higher level of engagement (more than 10 distinct events). RADs purport to measure real active days by excluding user days with very low volume of interactions with the platform.

UI Event

  • A record in the data corresponding to any action executed by a human directly in the app.

  • UI Events occur when a person clicks buttons in

Notes and Caveats Support and Solutions Accounts

  • Support and solutions accounts refer to those owned by team members that have been granted access to resources for purposes of support or solutions engineering.

  • You can identify such accounts with email address. For example,

  • Membership and Visits tables do not contain support and solutions accounts.

  • support and solutions accounts may appear in Events, Resources, and Tops tables.

Refresh Schedule

  • Data in Events and Visits tables is within 24 hours of up-to-date.

  • Data in Membership, Resources and Tops is usually within 24 hours of up-to-date, but may be between 24 and 48 hours behind.

Failed Syncs

  • Occasionally, table may fail to sync. A red dot on the table's icon will indicate that the most recent sync failed.

  • Attempt to sync the table manually by opening the table and then clicking "sync now" where the table's metadata is displayed in the sidebar on the right.

  • If this does not resolve the problem, then please report in a support ticket.