Tracking User Activity Using JavaScript
To support analysis of detailed user activity within CLM content, content can be coded to capture specific user actions performed on HTML5 content using the updateRecord JavaScript function. These actions can include button selections or certain gestures (clickstream data), or generic data capture, such as updating an HCP’s email address on the Account object. See the CLM JavaScript library for more information on the available functions.
Do not use the createRecord function to create call2_key_message__v records. Doing so interferes with Veeva-defined logic for call key messages.
Who can use this feature?
- iPad, iPhone, Windows users
- Users do not require an additional license
- Content Creator Users, End Users
Configuring User Activity Tracking
End Users
If saving tracked data into a custom object, configure the following for end users:
- Grant CRE object permissions to the custom object for the appropriate object types.
- Grant Edit field permissions to the fields on the custom object where data is saved.
To display the Call Clickstream information captured on the call report, add the clickstream_section__v app section to the call2__v layouts for the appropriate object types. This section displays a table of responses. The following fields from the call_clickstream__v object display in the table:
- answer__v
- key_message_name__v
- presentation_id__v
- product__v
- track_element_description__v
The fields displayed in the table are not configurable.
Creating Content with User Activity Tracking
Content Creator Users
Clickstream data can be used to capture custom information. By building a custom control within HTML5 content, responses can be captured and later displayed directly on the call report.
Additionally, the call_clickstream__v object can automatically populate the following fields each time a record is created for a Call. Manually entered values for the following fields are overwritten:
- call__v - set to the current Call record ID
- product__v - product__v of corresponding key_message__v record
- key_message__v - record ID of corresponding key_message__v record
- clm_id__v - clm_id__v of corresponding key_message__v record
- presentation_id__v - presentation_id__v of clm_presentation__v record
When implementing clickstream capture, content creators must be mindful of the potential amount of data captured as a part of each slide and/or presentation. Creating a large amount of records on each slide increases sync times for users and cause performance degradation on online reports.
