Where is our Stats Dashboard?

The Stats Dashboard provides statistics and a log console for Library.Link Network members. The dashboard provides information about the number and type of agents accessing the library catalog from the "borrow it" buttons on item pages. The Stats Dashboard is behind a username and password. The data is only available to library staff, and no personal identifying information is collected about those using library data.

Find your Stats Dashboard at https://stats.library.link/[your base url]/

For example: https://stats.library.link/link.trl.org/​

How often are Stats updated?

Statistics are refreshed once per month for the prior month's activity, between the 6-9th of each month. The activity of each previous month is summarized and the Detail Logs are available in CSV format for additional processing.

What is the retention schedule for Stats?

​

How do I get a Stats account?

​

To request an account, go to: https://manage.library.link/organizations/[your link domain].html

For example: https://manage.library.link/organizations/link.dallaslibrary.org.html​

On this page, you will see this box on the right hand side. Select "request access". Another way to get to this page is by going to Services > Stats and clicking on "cancel" when prompted to log in.

​​​​

Complete all fields on the next screen and submit:

What is an Embed impression?

Statistics are refreshed once per month for the prior month's activity, between the 6-9th of each month. The activity of each previous month is summarized and the Detail Logs are available in CSV format for additional processing.

An embed impression counts each time that embedded Library.Link Network data is viewed by a user outside of the Network, such as on the library’s blog, or Facebook page, etc.

For example, Allison embeds three widgets into a blog post. 1 with all the items written by an author, 1 with all the items related to a topic, and 1 with all the items in a series. Each time the blog post is rendered, or opened via a browser, 3 embed impressions are counted.

The Library.Link Network team actively maintains an ongoing list of crawlers and bots (agents that don’t appear to be humans) on Github. If you see a crawler or bot in the agent list in your detailed log, please report it to support@library.link.We will research the agent and if needed, add it to the list of agents that are filtered out from embed impression data.

You can find the number of impression for your embeds by going to Services > Stats > Embed Statistics

What is the cause of an empty referrer field in the detail logs for Embed Stats?

The Stats Dashboard provides statistics and a log console for Library.Link That means that the visitor did not send a referrer for the request. Referrer is optional and cannot be guaranteed to be provided or accurate. Blank referrer fields can happen if:

• The user was a direct visitor, and typed the URL into the browser bar or used a bookmark.

• The user followed a link from outside the browser (for example from an email or mobile app.)

• The user came to your non-secure http site from a secure https site and the browser hid the referrer for security reasons.

• The user modified their browser not to send a referrer (such as using a browser extension to hide the information.)

• The user is using a proxy server that removes referrer headers.

• The clicked link has an HTML5 rel=noreferrer attribute.

• A site uses JavaScript to link to your site. Many browsers don't send a referrer when JavaScript uses window.open or location.href to open or set a URL.

• A page redirects to yours with a meta refresh. Browsers either reset or remove the original referrer with this type of redirect.

• The request was made by a robot that is not programmed to send referrer information. Sometimes legitimate robots such as Googlebot do not send a referrer. Please note that we have filter bots from detailed stats on an on-going basis.

For more information, see: https://webmasters.stackexchange.com/questions/88481/what-causes-an-empty-referrer-field-in-a-webserver-log-file​

​