At some point you will might need to know what your end users actually use on your guides. This could be used in an annual review or dossier. This could also be help you make decisions on what's working well on your guides next time you're updating and refreshing the content. From following these steps you might notice some valuable resources being under utilized, which could lead to making slight adjustments in the design of your guide or how you choose to describe the asset on the page.
The very first thing you'll need to have done for this to work, is to build your LibGuide using assets correctly! If you follow the directions on adding assets, you'll be able to track how many users click through to the resources you have shown. This process won't work if you've simply hyperlinked resources using the rich text editor or added an existing database manually.
![]()
Here's what a report will look like
![]()
You'll notice three parts to a report
