Usage Tracking Analysis Analytic Subject Area
This subject area is available in all editions of Oracle CRM On Demand. Access to this subject area requires the Usage Tracking privilege. The administrator user role is granted this privilege by default.
This subject area enables users with the Usage Tracking privilege to analyze the usage of Oracle CRM On Demand within their company. Companies can analyze the usage of the following application areas in Oracle CRM On Demand:
This subject area has the following dimensions:
The complete list of metrics for this subject area and the fields for which they are stored is as follows:
The following table shows the Analytics Performance metrics. These metrics represent the performance of queries.
The following table shows the Application Usage metrics in Oracle CRM On Demand. These metrics represent the usage of various application object types, including how many records were created, updated, and deleted. In the table, Yes indicates that the metric is available for the field.
The following table shows the Page View Performance metrics in Oracle CRM On Demand.
The following table shows the Setup and Configuration metrics. These metrics are a snapshot of the latest setup and configuration of Oracle CRM On Demand as it existed at the time of an incremental refresh of your usage tracking data. The setup and configuration metrics are unique because they are not captured at any dimension level.
The following table shows the User Adoption metrics. These metrics allow companies to monitor and analyze the user adoption of the Oracle CRM On Demand application. In the table, Yes indicates that the metric is available for the field.
This topic provides usage notes.
About Usage Tracking Data
The usage tracking data in the data warehouse refreshes weekly from information in your Oracle CRM On Demand application data. Refreshing the usage tracking data happens on weekends and does not follow the nightly, incremental refresh of the rest of the data in Oracle CRM On Demand Answers.
Usage tracking metrics are recomputed only for the current month, and the prior month's data is not recomputed unless the week spans the end of the month. For example, when the incremental refresh for usage tracking runs on Friday, 28 May 2010, the usage tracking metrics are recomputed for the entire month of May starting from May 1, 2010. When the incremental refresh for usage tracking runs on Friday, 4 June 2010, the usage tracking metrics are recomputed for the months of both May and June, because that week spanned the months of May and June.
Usage tracking metrics are summarized by calendar months. Even though it is possible to analyze these metrics by a company’s fiscal calendars, they are not aligned with the fiscal calendar for companies with nonstandard calendars. There might be some oddity in a fiscal calendar definition especially if you are using a 4-4-5 or 5-4-4 or a custom calendar where two calendar months start in one fiscal period or no calendar month starts in a fiscal period. In situations like this, the usage tracking metrics might be inflated or missing for a given fiscal period.
Most usage tracking data is captured at the week level. Some user adoption metrics are not captured at the week level. All setup and configuration metrics are not captured at the week level. Because the usage tracking data is captured at the week level, it can be aggregated by month, quarter, and year. However, it might not produce any results if it is run at levels lower than the week level.
About User-Login History
The user-login history data that is older than 90 days is continuously purged from the Oracle CRM On Demand application. Hence, the Usage Tracking feature can support approximately 90 days of user adoption metrics when the Oracle CRM On Demand application is first upgraded to this release. However, the user adoption history data is retained in the data warehouse to support the historical trend analysis of user adoption metrics in the Oracle CRM On Demand Analytics. This data is retained until the next full refresh even after the data is purged from Oracle CRM On Demand.
Usage Tracking Metrics
Usage tracking metrics are collected by calendar week. If you are using a nonstandard calendar, such as 5-4-4, 4-4-5, or a custom fiscal calendar, then it is possible that one fiscal month or quarter might have more or fewer weeks compared to other fiscal months or quarters. So, your metrics might appear slightly inflated or deflated for a given month or quarter. This behavior is expected where your company’s metrics are not fully aligned with its fiscal calendar definitions when they are analyzed by fiscal calendar months and quarters.
The Content dimension is common to both the Analytics Performance metrics and Page View Performance metrics.
To report on Analytics Performance metrics, use the Content Category field to filter for the following condition:
Content Category = Analytics
To report on Page View Performance metrics, use the Content Category field to filter for the following condition:
Content Category = Page View
When analyzing Page View Performance metrics, the only Content dimension fields available are: Content Category and Content Name. For Page Views Performance, the Content Name value represents the title of the screen. For Analytics Performance, the Content Name value represents the report or dashboard name.
Analytics Performance Metrics
You cannot combine Analytics Performance metrics with any other metrics. You cannot combine the Page View Performance metrics with any other metrics. These two performance-related metrics are stored using different levels of detail, which are different from each other and from all the other metrics. The Analytics Performance metrics are captured at the content, user, and week level. These metrics are collected as each report is executed every time by each user, and they are summarized at the week level. The average response time is measured in seconds.
In contrast, the Page View Performance metrics are captured at the page and week level. These metrics are collected as each page is viewed each time, and they are summarized at the week level. The average response time is measured in milliseconds.
Analytics performance metrics can report metrics by individual users. However, page view performance is only at the company level. Most page views have a title, but for page views with missing titles the usage performance metric is reported as Others. Analytics performance metrics are included for shared and personal dashboards, but they are not included for dynamic queries. Both page view and analytics content names display metrics that are based on the company default language and standard object naming. They do not support user language or object renaming.
|Published 5/4/2012||Copyright © 2005, 2012, Oracle. All rights reserved. Legal Notices.|