Socrata Site Analytics

Overview

Socrata’s Site Analytics datasets give you access to granular data that can then be aggregated, sliced, & diced in the way that suits your business and communications needs. This functionality includes access to several key metrics via three on-platform datasets that are updated by our system on a regular cadence. With these metrics datasets, you can:

  • analyze usage by asset and by user type

  • gain insight into user logins and catalog searches on your site

  • leverage on-platform tools like visualizations, filtered views, and more to analyze your usage data

The Site Analytics data is provided to Admins on the Socrata platform via a special type of asset called a System Dataset. These datasets can be interacted with in the same way that your normal datasets can be, so you can create derived views to filter, sort, and aggregate in the Grid View, create Visualizations and Measures to surface analytics important to your organization, and communicate this information using Stories. All of the Socrata analysis and presentation tools can be used on these assets. The only differences between System Datasets and other assets on your platform is that they:

  • Are automatically generated by the platform

  • Cannot be modified

  • Are always private and hidden from your public Catalog

  • Can only be viewed by admins in the Assets list

Navigating to Site Analytics datasets

Usage data is now available on your site in three system datasets. The easiest way to find these datasets are to navigate to the internal asset manager:

5c438a3a-c253-45fd-904f-7622c662f93f.png

Next, filter the list of assets to only include asset type System Dataset:

2dbc9bb4-b9d0-4073-90be-7c6264a45e58.gif

The result of this filter should be three system datasets:

482271ce-9ecf-4379-b824-667ea8726618.png

Metrics Datasets Metadata

In the table below, you will find additional information about these three system datasets. 

Asset

Description

Site Analytics: Asset Access

This dataset includes usage data for the following on all datasets and derived views:
a) views of an asset in grid view (also known as data table or tabular view)

b) views of an asset’s primer page (also known as the dataset landing page)

c) API read access
d) downloads/exports

The data is presented at an hourly timeslice in UTC, with segmentation by user type and asset ID. Users are segmented into three types:
a) users with roles on the site, 
b) users logged in without roles on the site
c) users that are not logged in

API counts: Any API request results in one incremental count, so paging through an API with multiple requests will result in multiple increments of the counter.

Download counts: The download count increments when a user clicks the download/export link in the application or when they access the download URL directly.

Update cadence: This dataset is updated by a system process at least once a day.

Site Analytics: User Authentications (Logins)

This dataset includes usage data for user logins. The data is presented at an hourly timeslice in UTC, with segmentation by user type. Users are segmented into three types:
a) users with roles on the site
b) users logged in without roles on the site
c) users that are not logged in

Login counts: The user login count increments when a user logs in through the login page using their username and password or using single sign-on (SSO).

Update cadence: This dataset is updated by a system process at least once a day.

Site Analytics: Catalog Search Terms

This dataset includes usage data for catalog searches (not including searches made via API). The data is presented as individual observations of user searches with a timestamp in UTC.

Catalog searches: A catalog search is recorded when a user navigates to the catalog and enters a search term; catalog search using the API is not included in this dataset.

Update cadence: This dataset is updated by a system process at least once a day.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.