Skip to main content

Celonis Product Documentation

Studio Tracking Service


Studio tracking service is a feature that allows tracking of Studio and Apps Assets. In addition, the Studio tracking service helps gain usage and adoption data at the asset level. This feature answers the following questions:

  1. How do I get data that goes deeper than the current user adoption views and shows asset usage?

  2. How can I get Studio / Apps asset-level raw data to build my adoption views?

  3. What Spaces, Packages, and Views are used most, and by who?


Larger EMS teams tend to have many packages, views, and a significant number of users. The team admin needs to be able to govern their team and usage of EMS. This isn’t the problem with smaller EMS teams with multiple packages, views, and fewer users. Governance is more manageable because there is less to manage.


Larger teams with 80 or more users will have a feature within the existing User Adoption View page that will allow them to toggle on / off a Studio tracking service. Once enabled, this service will start tracking asset level usage and capture this in a CSV file. The CSV file can then be downloaded and used by Analysts to create a custom Studio view showing usage and adoption at the Studio asset level.

How to Set Up Studio Tracking Service

The following steps will show you how to set up the Studio Tracking Service.

  1. This feature will be automatically enabled for EMS teams with over 80 users.

  2. Locate the button at the top right of the Adoption Views Page called “Set up tracking service.”

  3. Click on the button, and a UI model will appear with a toggle called Studio.

  4. Enabling this toggle will activate the new service and allow the admin to export the Tracking CSV data.


    Tracking is not retroactive. Data collection will only start once the tracking service is enabled. Therefore, please do not expect to see historical data when first enabling this feature.

  5. Once the CSV downloads, the columns in the CSV will represent the following:

    • User UUID

    • User Email address

    • Date and Time

    • Service (Apps / Studio)

    • Space name and UUID

    • Package name and UUID

    • Folder name and UUID

    • Asset name and UUID

  6. With the CSV, go to data integration and upload the CSV to create a data model and subsequent Studio view.


Why is this only enabled for teams with over 80 users?

  • Teams with over 80 users require a higher level of governance because they have multiple packages and views to manage. Therefore, it is crucial for larger teams to quickly identify which of the numerous packages and views are being used the most.

    This detailed usage tracking is less urgent for teams with less than 80 users and fewer packages. They simply have less content for their users to access and can manage adoption using the existing User Adoption Views in Admin and Settings to manage login behavior.