| Print Open PDF Version of Online Help

##### Usage Tracking Analysis Historical Analytics Subject Area ### Availability 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. ### Business Purpose 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: Application usage User adoption Setup and configuration ### Relationship Type Simple ### Dimensions This subject area has the following dimensions: Analytics Object Content Date Object Type User User Sign In History ### Metrics 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 Object metrics.
Metric | Description
Number (#) of Objects | Number of Analytics objects.
The following table shows the Analytics Performance metrics. These metrics represent the performance of queries. In the table, Yes indicates that the metric is available for the field.
Metric | User | Date (Week) | Content | Description
Number (#) of Requests | Yes | Yes | Yes | Number of requests by report name and dashboard name by week. If a report is also available on a dashboard, then the number of requests for the report reflects only the requests where it was run as a report. Because a dashboard often contains more than one report, requests run within a dashboard are not included in the count that calculates for reports.
Number (#) of Times Failed | Yes | Yes | Yes | Number of times requests failed by report and dashboard names by week.
Average (Avg) Response Time (s) | Yes | Yes | Yes | Average response time (in seconds) for requests.
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.
Metric | User | Date (Month) | Object Type | Description
Number (#) of Records Created | Yes | Yes | Yes | Number of records created by object by user by month
Number (#) of Records Updated | Yes | Yes | Yes | Number of records updated by object by user by month
Number (#) of Records Deleted | Yes | Yes | Yes | Number of records deleted by object by user by month
The following table shows the Page View Performance metrics in Oracle CRM On Demand. In the table, Yes indicates that the metric is available for the field.
Metric | User | Date (Week) | Content | Description
Number (#) of Requests | Yes | Yes | Yes | Number of requests by page by week
Average (Avg) Response Time (ms) | Yes | Yes | Yes | Average response time (in milliseconds) for page views
Max Response Time (ms) | Yes | Yes | Yes | Maximum response time (in milliseconds) for page views
Min Response Time (ms) | Yes | Yes | Yes | Minimum response time (in milliseconds) for page views
NOTE: The Max Response Time and Min Response Time values are available only for the page view records that have been loaded since this feature became available. Page view records loaded in Oracle CRM On Demand Release 25 and earlier have NULL values because this data was not recorded in those releases. 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.
Metric | Description
Number (#) of Administrators | Number of administrators granted with any of the following privileges: Manage Company, Manage Company - Define Currencies, Manage Company - Reset All Passwords, Manage Themes, Manage Content, Manage Content - Manage Attachments and Detail Page Images, Manage Books, Manage Territories, Manage Users, Manage Roles and Access, Manage Users and Access - Manage Delegated Users
Number (#) of Assignment Rules | Number of assignment rules defined in Oracle CRM On Demand
Number (#) of Books | Number of books defined in Oracle CRM On Demand
Number (#) of Currencies | Number of currencies activated in Oracle CRM On Demand
Number (#) of Custom Fields | Number of custom fields used in Oracle CRM On Demand
Number (#) of Custom Objects | Number of custom objects deployed in Oracle CRM On Demand
Number (#) of Custom Tabs | Number of custom Web tabs used in Oracle CRM On Demand
Number (#) of Groups | Number of groups set up in Oracle CRM On Demand
Number (#) of Languages | Number of languages enabled in Oracle CRM On Demand
Number (#) of Products | Number of products defined in Oracle CRM On Demand
Number (#) of Sales Process | Number of sales processes defined in Oracle CRM On Demand
Number (#) of Territories | Number of territories set up in Oracle CRM On Demand
Number (#) of Web Applets | Number of Web applets used in Oracle CRM On Demand
Number (#) of Web Links | Number of Web links used in Oracle CRM On Demand
Number (#) of Workflows | Number of workflows set up in Oracle CRM On Demand
The following table shows the User Adoption (Monthly) 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. NOTE: Any session record that does not have a value in the Sign Out Time field is excluded from the calculation of the Number (#) of Login Seconds and Average (Avg) Login Seconds metrics for both monthly and weekly metrics, because the duration of that session cannot be calculated.
Metric | User | Date (Month) | Description
Number (#) of Active Users | No | Yes | Number of active users existing in the application per month
Number (#) of Days Since Last Login | Yes | No | Number of days since the last login by the user
Number (#) of Delegated Users | No | Yes | Number of delegated users existing in per month
Number (#) of Licenses | No | No | Number of licenses defined in the company profile
Number (#) of Login Seconds | Yes | Yes | Number of seconds a user was logged in during a given month
Number (#) of Total Logins | Yes | Yes | Number of times a user logged in during a given month. If a user logs in three times a day, it is counted as 3 logins and added to the current month's value.
Number (#) of Unique Logins | Yes | Yes | Number of unique times a user logged in during a given month. If a user logs in three times a day, it is counted as 1 unique login and added to the current month's value.
Number (#) of Unsuccessful Logins | Yes | Yes | Number of unsuccessful logins by user by month
Percentage (%) Logged In | No | Yes | Number of users logged in that month divided by the number of active users.
Average (Avg) Login Monthly Frequency | No | Yes | Number of unique logins for a given month divided by the number of users logged in for that month.
Average (Avg) Login Seconds | Yes | Yes | Number of seconds a user was logged in during a given month divided by the number of times the user logged in during that month.
The following table shows the User Adoption (Weekly) 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.
Metric | User | Date (Week) | Description
Number (#) of Active Users | No | Yes | Number of active users existing in the application per week
Number (#) of Delegated Users | No | Yes | Number of delegated users existing in per week
Number (#) of Login Seconds | Yes | Yes | Number of seconds a user was logged in during a given week
Number (#) of Total Logins | Yes | Yes | Number of times a user logged in during a given week. If a user logs in three times a day, it is counted as 3 logins and added to the current week's value.
Number (#) of Unique Logins | Yes | Yes | Number of unique times a user logged in during a given week. If a user logs in three times a day, it is counted as 1 unique login and added to the current week's value.
Number (#) of Unsuccessful Logins | Yes | Yes | Number of unsuccessful logins by user by week
Percentage (%) Logged In | No | Yes | Number of users logged in that week divided by the number of active users.
Average (Avg) Login Seconds | Yes | Yes | Number of seconds a user was logged in during a given week divided by the number of times the user logged in during that week.
Average (Avg) Login Weekly Frequency | No | Yes | Number of unique logins for a given week divided by the number of users logged in for that week.
### Usage Notes 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. 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. #### Analytics Object Dimension You can combine fields from the Analytics Object dimension with fields from the User dimension only and with the Analytics Object metrics only. You cannot combine fields from the Analytics Object dimension with fields from any dimension other than the User dimension or with any metrics other than the Analytics Object metrics. To report on the user information for the user who created an object, add fields from the Analytics Object and fields from either the User dimension, or the Created By dimension under the Analytics Object dimension. To report on the user information for the user who last modified an object, add fields from the Analytics Object and fields from the Last Modified By dimension under the Analytics Object dimension. The weekly refresh of the usage tracking data overwrites the existing data for the Analytics objects. You must export the data each week if you want to compare the data from week to week. Usage tracking data is collected for the following types of Analytics objects: Action, Analysis, Condition, Filter, Dashboard, Dashboard Page, and Dashboard Prompt. When you extract and review the data for Analytics objects, consider the following points: Data is collected for the Analytics objects under Shared Folders only. Data is not collected for Analytics objects that are stored in personal folders. Data about deleted objects is not collected. If an object was deleted from the catalog during the week before the data was refreshed, then the data does not include any information about that object. If an object was modified more than one time during the week before the data was refreshed, then only the details for the most recent modification are available. If an object was created during the week before the data was refreshed and then later deleted during the same period, then the object is not included in the data for the period. If an object was created during a given week, and if that object was then deleted during the following week and a new Analytics object with the same name was created during the same week, then an object with that name appears as a newly created object in the data for two consecutive weeks. #### Analytics Objects Metrics You can combine the Analytics Object metrics with fields from the Analytics Object and from the User dimension only. You cannot combine the Analytics Object metrics with any other metrics or with fields from any other dimension other than Analytics Object or User dimension. #### Content Dimension 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 V3 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. To display the path of the analyses and dashboards in your usage tracking analysis, use the Content Details field within the Content dimension. Content Details appear only for content for which the Content Category is set to Analytics V3. The format for the paths for analyses and dashboards is as follows: Path for the personal folder of a user: /users/UserRowID where UserRowID is the Row ID of the user who is the owner of the folder. For example: /users/1QA4-HQOAD Path for the Company Wide Shared Folder: /shared/CompanyNumber_Shared_Folder where CompanyNumber is the number of your company's instance of Oracle CRM On Demand. For example: /shared/9999_Shared_Folder Path for the Migrated Company Wide Shared Folder: /shared/Company_CompanyNumber_Shared_Folder where CompanyNumber is the number of your company's instance of Oracle CRM On Demand. For example: /shared/Company_9999_Shared_Folder NOTE: In releases earlier than Release 38, usage for custom dashboards stored in folders under the Migrated Company Wide Shared folder was not tracked. The path for an analysis that is embedded in a record-type Homepage in the standard application has the suffix /_Emb. Some analyses that are run from the prebuilt dashboards under the Pre-Built Analyses folder in the catalog have the suffix /_DB. The subfolders that correspond to the /_Emb and /_DB suffixes, and the analyses in these subfolders, are not visible in the catalog. The following is an example of the path for an analysis that is embedded in a record-type Homepage by default in the standard application: /shared/Pre-built Analysis/Customers Analytics/_Emb The following is an example of the path for an analysis that is run from a prebuilt dashboard: /shared/Pre-built Analysis/Customers Analytics/_DB Starting with Release 38, the Content Details field is populated as follows: For custom dashboards stored in folders under either My Folders or Shared Folders, the Content Details field is populated with the path to the dashboard as it appears in the catalog. For example, if a dashboard is stored in a custom folder named My Custom Dashboards directly under My Folders for a user whose user ID is 1QA4-HQOAD, then the Content Details field contains the following: /users/1QA4-HQOAD/My Custom Dashboards Each custom folder level is included in the path. As another example, if a dashboard is stored in a custom folder named Custom Account Dashboards directly under Company Wide Shared Folders for a company whose instance number is 9999, then the Content Details field contains the following: /shared/9999_Shared_Folder/Custom Account Dashboards NOTE: In releases earlier than Release 38, usage for custom dashboards stored in folders under My Folders was not tracked. Usage for custom dashboards stored in folders under Shared Folders was tracked, but the Content Details field was not populated. For analyses that are run from a dashboard, the Content Details field is populated with the path to the dashboard, including the name of the dashboard. The Content Name field is populated with the name of the embedded analysis. NOTE: In releases earlier than Release 38, the Content Details field was not populated for analyses embedded in a dashboard. For My Dashboard, that is, each user's personal dashboard, the Content Details field is populated with the following path: /users/UserRowID/_portal For example: /users/1QA4-HQOAD/_portal NOTE: In releases earlier than Release 38, usage for My Dashboard was not tracked. For dashboards stored in the system-generated Dashboards folder under Company Wide Shared Folder, the Content Details field is populated with the following path: /shared/CompanyNumber_Shared_Folder/_portal For example: /shared/9999_Shared_Folder/_portal For dashboards stored in the system-generated Dashboards folder under Migrated Company Wide Shared Folder, the Content Details fields is populated with the following path: /shared/Company_CompanyNumber_Shared_Folder/_portal For example: /shared/Company_9999_Shared_Folder/_portal NOTE: Starting with Release 38, the suffix for the path for the system-generated Dashboards folders is /_portal. In earlier releases of Oracle CRM On Demand, the suffix was /Dashboards. #### 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. #### User Sign In History Restrictions The User Sign In History dimension specifies the source of the user sign in, such as Interactive, Web Services, Mobile, and so on. This dimension has the following restrictions: The only metrics that can be used with User Sign In History are the following User Adoption metrics: Number of (#) Total Logins Number of (#) Unsuccessful Logins Only the current month of data is updated by an incremental refresh. History data for the Sign In Type columns is not updated through an incremental refresh. NOTE: The Sign In Type values are available only for the User Sign In records that have been loaded since this feature became available. User Sign In History records loaded in Oracle CRM On Demand Release 29 and earlier have NULL values because this data was not recorded in those releases. ### User Adoption Weekly and Monthly Metrics Weekly data does not roll up to monthly data. Monthly data is calculated separately, based on the number of days in the month.

Published 5/23/2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.