Page History

...

Once the code has been copied from Google Analytics pages, it should be placed in the  ................ configuration the WEB-INF/components/templates/AnalyticsComponent.vm file as the ................ configuration parameter value. The tracking code should be embedded correctly after the changes have been saved in the configuration file and after the reader application has been restarted. As a result, the tracking code will be visible in the HTML code of the web pages of the reader application, and data will be reported to GA.

...

1. Select the “Behavior > Content analysis” report.
2. In the table, in the “Level 1 of the page path” column, click the “/dlibra/” item.
3. In the table, in the “Level 2 of the page path” column, click the “/publication/” item.
4. The table with publication identifiers is visible; the default sorting order is by page views, in descending order. In this context, a page view is:
   
   1. for a publication with content – an impression of the metadata page or an impression of online content;
   2. for a publication without content (for example, higher-order elements of group publications, like a whole journal) – an impression of the page with the description/structure of an element of a group publication.
5. When a publication identifier in the “Level 3 of the page path” column is clicked, the table about the way of interacting with the publication will be displayed. The table contains should contain two rows:
   
   1. /zip/ – for downloading the publication as a ZIP archive; and
   2. /<main file name> – for displaying the publication online.
6. In step 3 above, additional filtering may be introduced to only display downloads. For that purpose, the user should:
   
   1. add “Additional dimension” (the button over the table) named “Level 3 of the page path”;
   2. enable advanced filtering of table rows (the “Advanced” link on the right, over the table) and select:

...