How to Track Internal User Behavior in NetSuite Like Google Analytics?

Building a bundle that replicates Google Analytics' comprehensive tracking of internal user behavior within NetSuite is generally not feasible due to limitations in NetSuite's exposed APIs and page customization capabilities. However, several methods and tools can provide valuable insights into user activity and system performance:

While NetSuite's native analytics capabilities, including SuiteAnalytics, have significantly evolved to offer robust reporting, workbooks, and dashboards for business intelligence, direct Google Analytics-like tracking of internal user behavior faces specific limitations. However, the following Out-of-the-Box (OOTB) information is available for tracking various aspects of user activity:

1. Login Audit Trail

   Provides details on who logged in, when, from which IP address, and with which role.

2. Audit Trail

   Records information on who created, edited, or deleted transactions. This does not track viewing activity.

3. System Notes

   Tracks changes made to any records, though it often excludes modifications within sublists.

   For performance monitoring and some user activity insights, the former Script Performance Monitor bundle (which is no longer installable) has been explicitly replaced by the Application Performance Management (APM) SuiteApp, which is currently available and actively used. The former bundle allowed viewing who accessed records, but required navigating record-by-record, likely needed scripts on the record, and had a limited history (approximately one week).

   A SuiteApp, FLODocs, has been noted to provide some insights into the usage of scripts and custom fields, offering a view of the relationships between customizations (e.g., field A used by Script A, Script B, Saved Search C, Form A, etc.). While powerful, it is not a free solution.

   For highly customized tracking, it may be possible to implement analytics on forms and saved searches using inline HTML fields to embed Google Analytics or other third-party analytics functions. This approach requires adding a specific field to all desired saved searches and either a custom field to each record type or a script to all record types to capture metrics. Suitelets would also require separate implementation, and this method cannot be applied to non-customizable pages. While not an OOTB solution, this approach is technically feasible.