Build highly scalable dashboards

When a dashboard is shared with everyone, there is a chance that it will experience high demand and generate a large amount of traffic. High-demand activity can happen when a dashboard gets picked up by social media, a news feed, or other outlets.

The following best practices ensure that the traffic generated by a dashboard leverages ArcGIS Online's scalable infrastructure and scales effectively in high-demand situations.

Dashboard data sources

Data sources are the web maps and web layers stored within your ArcGIS Online organization. Follow these guidelines for optimizing the layers in your dashboards.

  • Ensure that your dashboard and all referenced web maps and layers are shared with everyone.
  • Ensure that all layers used in the dashboard are a hosted feature layer, feature layer view, or hosted tile layer.
  • Ensure that editing, sync, and ownership-based access control are all disabled.

    Ownership-based access control might still be enabled (even after sync is disabled). Follow the steps in this article to disable ownership-access control on the layer.


    If your data requires editing, avoid sharing it with the public. If sharing is required, create a feature layer view and ensure it follows these best practices.

  • Hosted feature layers and feature layer views should have their cache control duration set to a value that reflects how often the data is actually updated (the default is 30 seconds).
  • For hosted feature layers with a large number of features, create attribute indexes on any fields that are queried often.
  • Layer filters and view definitions should not include relative date conditions. These are the in the last or not in the last operators.

Dashboard configuration

When authoring and sharing a dashboard, the following configuration options ensure that your dashboard makes the best possible use of the platform's scalable infrastructure and that changes to a dashboard's sharing do not negatively impact your organization.

  • If your dashboard has one or more map elements that include map extent filters, ensure the target layer is based on a map's operational layer.
  • When configuring a filter action, and the target is based on a different data source, do not use the Spatial method. Instead, use the Field method.

    Note: You may need to pre-process your data to add additional fields before configuring your dashboard.

  • If your dashboard uses embedded content to include other apps that use ArcGIS Online content, ensure that they follow best practices for scalable apps.
  • When sharing a dashboard URL or using a URL to embed your dashboard into another page, use the generic URL starting with instead of your organization-specific URL.
  • When configuring dashboard elements and selectors, avoid using relative date filters with the following operators:
    • is within the last
    • is before the last
    • is within the next
    • is after the next
  • When using is before or is after operators, do not use the default period Now.