Embed Dashboard or Build Widgets Inside Experience Builder

DanielKhuat — Mon, 10 Aug 2026 17:39:47 GMT

Hello! So I'm pretty far into a project for developing a KPI metrics website and I'm at a crossroads. Originally, I built everything within Experience Builder, but I found it really time-consuming to get even the simplest metrics that Dashboard can easily display. I decided to pivot to embedding Dashboards into the Experience Builder site, and although it comes off as more clean, the Experience Builder site sometimes glitches or acts staticky when scrolling through. Could it be a connection issue? Would building everything within Experience Builder improve the performance of the site?

Re: Embed Dashboard or Build Widgets Inside Experience Builder

OlaIHamed — Mon, 10 Aug 2026 18:20:28 GMT

Hi Daniel,

I actually ran into a very similar situation on one of our projects.

We initially tried building KPI-style pages entirely in Experience Builder, but found that creating metric cards, indicators, and dashboard-style layouts required considerably more effort than using ArcGIS Dashboards, which is purpose-built for that type of visualization.

In the end, we also chose to embed Dashboards within Experience Builder.

Regarding the scrolling glitches you're seeing, I don't think embedding a Dashboard is automatically the cause. There are several factors that could contribute, for example:

The complexity of the Experience Builder app (# of widgets, sections, data sources)
The Dashboard itself (number of elements, indicators, charts, map widgets, refresh intervals)
Browser rendering performance
Network latency, especially if the Dashboard is making multiple requests while Experience Builder is loading other resources
Client machine performance

One thing I would recommend is opening the browser's Developer Tools (F12) and checking the Network and Console tabs while reproducing the issue. If requests are taking a long time, failing, or being retried, that can help determine whether it's a network or application issue.

My general recommendation would be:

Use ArcGIS Dashboards for KPI-heavy pages where the primary goal is displaying metrics, charts, and indicators.
Use Experience Builder for the overall application experience-navigation, search, editing workflows, maps, and integrating multiple applications.

That way, each product is being used for what it was designed to do.

If you're seeing the static or jittery scrolling consistently, I'd also be interested to know:

Which browser are you using?
Approximately how many Dashboard widgets/elements are embedded?
Is the Dashboard configured to auto-refresh? If so, what refresh interval are you using?
Are you embedding a single Dashboard, or multiple Dashboards within the Experience Builder page?

Regards,

Ola

topic Re: Embed Dashboard or Build Widgets Inside Experience Builder in ArcGIS Experience Builder Questions

Embed Dashboard or Build Widgets Inside Experience Builder

Re: Embed Dashboard or Build Widgets Inside Experience Builder