Account Usage

The "account_usage" tab gives you transparency over the people you should care about most: your organization's Adobe Analytics users!

• How popular is Adobe Analytics at my organization and how has this developed over time? For example, are logins and workspace views trending up or down?

• Who are my power users?

• Which users are at risk (less active recently compared to earlier)?

For questions like these, there is the account usage tab.

To update the tab, simply go to "Adobe Component Manager -> Other -> Get Account Usage Stats" and enjoy the insights.

Shed light on the activity of your organization's Adobe Analytics users

Updating the tab for the first time can take a while, usually between 5 and 45 minutes, depending on how much is going on in your Adobe Analytics account.

To see email addresses or login names instead of hashes, uncheck the "no personal data" checkbox in the "config" tab.

Copy the stats to your own Google Cloud Storage bucket

If you want the raw account usage data outside of Google Sheets — for example to feed it into your own data warehouse or BI pipeline — the Component Manager can automatically write a CSV copy of the account usage stats to a Google Cloud Storage (GCS) bucket in your own Google Cloud project.

To enable this, set the gcs_bucket key in the "config" tab to the name of your target bucket (e.g. my-company-component-manager). From then on, every account usage update writes a copy of the stats CSV to that bucket.

The bucket must grant Storage Object Admin (roles/storage.objectAdmin) permission to the Component Manager service account [e-mail] so it can create and overwrite the file.

See the config tab reference for all available config keys.

Frequent Questions

Are views from technical users (e.g. via API) counted?

No. Account Usage Stats and Workspace Stats filter out all operations by technical users (via the "*@techacct.adobe.com" email address).

Does the moment a Scheduled Project is generated count as a Workspace view?

Adobe Analytics does generate a project_view event (= a Workspace view) for the respective project and the user that created the schedule at the time of dispatch. It can't be distinguished from a regular project_view. The opinions on this differ: Some people see this as beneficial - this way, getting a Workspace PDF to your mailbox can be seen as a way to "view" a Workspace.