Open Data Portal Web Analytics Dashboard

This interactive dashboard showcases the City of Austin Open Data Portal (data.austintexas.gov) web traffic and search-term performance metrics.

How To Use the Dashboard

  • View larger dashboard: Click here to open an enlarged view of the dashboard in a new window.
  • Reports: There are four reports available in the dashboard view — Top DatasetsTop Data StoriesTop Search Terms, and Top Referral Sites. Click on the arrows ('Previous Page' or 'Next Page') located at the bottom of the dashboard to navigate through the reports. 
  • Filters: Use the filter options in the reports to select attributes such as asset type, access type, user segment, or to change the date range. All the visualizations in a report will dynamically change when non-default filters are applied. You can reset the report elements back to their original settings by clicking the 'reset' icon (curved back arrow or 'undo' icon).

About the Data

The following datasets utilized in the dashboard are provided by Tyler Technologies and sourced from the portal’s enterprise data management platform. The data is updated daily by a system process to sync any changes or if there is new data to record. Visit the dataset primer (overview) pages below for more information or to export or view source data.

Descriptions

  • Catalog Search Terms – A word, phrase, or characters entered by users into search bars that look through the data catalog for relevant information. (Note: Catalog searches using the Discovery API are not included in the data.)
  • Primer Page– A dataset’s principal landing-page experience providing an overview for uploaded datasets and filters.
  • Referral Site (or Referrer) – The external source (website or link on another domain) that users were on immediately before redirecting to our domain.
Asset Type: The type of asset hosted on the domain.
  • Dataset – Datasets (collection of data) uploaded into the data management platform.
  • Filter – Also called Filtered Views or Derived Views, these are saved filtered datasets obtained from an original dataset. Filtered Views are linked to the initial dataset through the ‘More Views’ tab on its primer (overview) page.
  • Story – These are web pages created for data storytelling purposes (data analysis insights and findings based on datasets, visualizations, etc.).
  • Measure – A measure is a metric card containing a timeline visualization that can be embedded in a Story page. It tracks performance data over time and can aggregate by time increment (year, quarter, etc.) and a variety of computations (rate, average, etc.).
  • Map – Maps created from geolocation or geospatial data (shapefile, kml, or kmz file).
  • Visualization – Assets that are a visual representation of data such as a bar chart, column chart, pie chart, histogram, scatter chart, timeline diagram, etc.
Access Type: Also referred to as an interaction, this is how all assets on the domain are being used (e.g., views, downloads, API reads).
  • API read– This represents all API requests to datasets or derived filtered views and is defined by a request that accesses the SODA or '.../resource' endpoint. Paging through the SODA endpoint results with multiple requests will result in one record for each request made.
  • Download – This represents downloads and exports of assets and covers the following actions: a) when a user clicks the download/export link from the data table or primer page; b) when a user accesses the download URL link directly.
  • Primer pageview – This represents the number of views for Primer or overview pages of a given dataset or filtered view over a period of time.
  • Grid pageview – This represents the number of views for the data preview page (commonly called the data table or tabular view page) of datasets and filtered views.
  • Story pageview– This represents the number of views of published data stories over a period of time. It does not track draft or preview pageviews. (Note: When loading a story page, the assets (measures, visualizations, maps, etc.) that are embedded on the story page are not tracked as separate views. The loading of a story page is tracked as one view of the story page itself.)
User Segment: The type of users accessing domain assets grouped by user segment (site member, community users, or anonymous user).
  • Anonymous user – This represents users that have not logged in on the domain.
  • Community user – This represents logged-in users who do not have an assigned role on the domain.
  • Site member – This represents logged-in users who have an assigned role on the domain allowing them to create and manage datasets and perform other tasks.