Product Usage

Product Usage is used to load monthly product and application usage data.

Use this page when you need Yarken to track how users engage with products or applications during a reporting period. This data supports product adoption reporting, SaaS governance, software license intelligence, TBM allocation, mapping, and license usage analysis.

Product Usage sits under Yarken Designer > Consumption > Product.

What Product Usage helps you do

Use Product Usage to:

• Load monthly product usage data

• Track application or product activity by user

• Associate product usage data with a vendor

• Compare assigned licenses with actual product activity

• Support adoption and reclaim analysis

• Feed License Usage analytics and Software License Intelligence

• Provide usage inputs for TBM allocation and mapping

Product Usage helps teams understand whether licensed products are being used, not only whether they are assigned.

When to use Product Usage

Use Product Usage when the data describes activity, engagement, or usage for a product or application.

Typical examples include:

• Application usage by user

• Product activity counts

• User engagement with a licensed product

• Monthly usage snapshots by application

• Product usage records tied to a vendor or tenant context

Use Tenant License Usage when the data summarizes total, consumed, and available licenses at tenant or product level.

Use Individual License Usage when the data identifies assigned or consumed licenses at user level.

How Product Usage fits the consumption model

Product Usage is part of the broader Consumption area in Yarken Designer.

The typical flow is:

1. Select the reporting year

2. Open Consumption > Product

3. Upload product usage for the relevant month

4. Review the upload in Uploaded Files

5. Check any errors or mapping issues

6. Use upload rules where transformation is required

7. Review the data in License Usage analytics and related reporting

The uploaded data becomes available for downstream reporting once the file is loaded and processed successfully.

Page layout

Product Usage includes three tabs.

Use Overview for month-based upload activity. Use Uploaded Files when checking what has already been loaded.

Overview tab

The Overview tab shows the selected year as monthly upload tiles.

Each month represents a reporting period. Use the relevant month tile to upload the product usage file for that month.

Before uploading, confirm that:

• The selected year is correct

• The file represents the month you are uploading into

• The report date in the file matches the selected month and year

• Tenant identifiers already exist in Yarken where required

• User email values are consistent and valid where included

• Product or application names match the expected source structure

This helps avoid failed uploads and improves reporting accuracy.

Uploaded Files tab

The Uploaded Files tab shows the files that have been loaded for Product Usage.

Common columns include:

Use this tab to confirm whether a file loaded correctly and whether the expected number of records was processed.

Uploaded file actions

Each uploaded file can include file-level actions.

Common actions include:

Use Re-map and reload when the field mapping needs correction before the file is processed again.

Upload Rules tab

The Upload Rules tab lets administrators create rules that transform data during upload.

Upload rules are useful when source files need controlled cleanup or standardization before the data is loaded.

Rules can help with tasks such as:

• Assigning default values

• Standardizing field values

• Updating target fields during upload

• Supporting consistent mapping across recurring files

Use upload rules carefully. They affect how uploaded data is transformed and can change downstream reporting results.

Required data checks

Before uploading product usage data, confirm these checks.

Strong source data improves product activity and adoption reporting.

Relationship with License Usage analytics

Product Usage feeds product activity reporting in the License Usage analytics cube.

In Analytics, product usage data can help teams review:

• Report Date

• App Name

• User Email

• Count

• Tenant dimensions

• Vendor context

Use Analytics to compare product activity across users, applications, tenants, vendors, and reporting periods.

Relationship with Software License Intelligence

Product Usage supports software license intelligence by showing whether licensed products are actually being used.

This helps teams:

• Compare license assignment with activity

• Identify products with low adoption

• Review users with licenses but limited product usage

• Support reclaim and reassignment decisions

• Improve renewal planning and SaaS governance

Product usage is most useful when reviewed alongside tenant license capacity and individual license usage.

Relationship with product adoption and unit cost

Product Usage helps teams understand adoption, activity, and utilization.

When usage is combined with license cost, product spend, or allocation data, teams can analyze:

• Cost per active user

• Cost per product activity count

• Usage trends by month

• Adoption by tenant or business group

• Products with high cost and low usage

This supports better renewal, rationalization, and planning decisions.

Relationship with Multi Cube

Product Usage can be combined with other data in Multi Cube when matching fields are available.

Example use cases include:

• Linking product usage to employee records through user email

• Comparing application activity with license assignment

• Connecting product usage with application spend

• Reviewing usage by cost center, entity, or team

• Supporting adoption reporting by business group

Use Multi Cube when the question needs product usage combined with another cube or master data source.

Recommended practices

Use these practices when managing Product Usage:

• Load files consistently for each reporting month

• Confirm the selected year and month before uploading

• Keep product and application names consistent across months

• Keep user email values consistent where included

• Review uploaded file status after each load

• Check loaded records against the expected record count

• Resolve errors before using the data in reporting

• Use upload rules only when the transformation is required and repeatable

• Review product usage with tenant capacity and individual license usage where available

Consistent product usage uploads improve adoption analysis and license governance.

Common issues

If a product usage file does not load correctly, check:

• Whether the Tenant ID exists in Yarken where required

• Whether the report date matches the selected upload month and year

• Whether required fields are populated

• Whether product or application values are formatted consistently

• Whether user email values are valid and consistent where included

• Whether the file has duplicate or incomplete records

• Whether the uploaded file mapping is correct

• Whether upload rules changed the expected field values

• Whether the file status shows an error in Uploaded Files

If results look incorrect in Analytics, start by checking the uploaded file status, record count, product names, user email values, and reporting period.

Next step

• Assets

Related content

• Consumption

• License Usage

• Software License Intelligence

• Tenant License Usage

• Individual License Usage

• Application Usage

• Yarken Designer