Usage Analytics Reporting Leading Practices

When managing usage analytics reports, consider the following recommendations and tips to improve report loading time:

  • Reduce the number of cards in the same tab by reorganizing your report (see Manage Tabs). A high number of cards means many API calls at the same time, which can increase the report loading time.

  • Computing statistics such as trends and unique counts (e.g., Unique Visitor ID) takes time, so consider excluding unnecessary metrics and trends from report cards.

  • Select a report period that only includes the data you need. A wider date range (e.g., months vs. weeks) means more data to sort through and compute.

  • Use trend cards with caution. Trend cards are the most costly, in performance terms, so reports containing many cards of this type take a longer time to load.

  • Review the complexity of the report filters

    • Including the Advanced Query Expression dimension in a filter is very expensive, in performance terms. Therefore, it is recommended to use custom dimensions instead since they remove the need for filtering on Advanced Query Expression.

    • Filtering with the Contains or Does not contain operators and a list of values such as usernames or visitor IDs takes a longer time to compute.

    • “Exact match” filters (using the Is or Equals operators) are more performing than “contains” filters (using the Contains or Does not contain operators).

    • Named filters do not improve report performance.

      Applying a named filter that contains five filters is the same as adding those five filters individually on a report.