You do not build Lightning Experience Insights, you turn on its pieces and read them. Here is how an admin opens the Lightning Usage App, switches on a live EPT readout for spot checks, and builds a custom report when the packaged views are not enough.
- Open the Lightning Usage App
Click the App Launcher, search for Lightning Usage, and open the app. Confirm you are in Lightning Experience, because the app does not appear in Classic.
- Review Activity, then Usage
Start in the Activity section to read daily active users, most-visited pages, and the count of users switching to Classic. Move to the Usage section to see EPT broken down by page and by browser.
- Turn on a live EPT counter
To spot-check one page, enable Lightning Component Debug Mode for your user, or append eptVisible=1 to the page URL. The current EPT then shows in the header as you click around.
- Build a custom usage report
When you need a tailored trend, create a report on a Lightning Usage object such as LightningUsageByBrowserMetrics, choose your fields and date grouping, and save it to a dashboard for ongoing review.
Per-user setting in Setup that, among other things, lets the live EPT counter render in the header for diagnosis.
Quick toggle appended to a Lightning URL that displays the running EPT without changing any org setting.
Objects such as LightningUsageByBrowserMetrics that expose the same data the app charts, so you can build custom reports and dashboards.
Add-on that provides the Lightning Page View event type for row-level performance records when you need per-session detail.
- The Lightning Usage App shows only the recent few months of data, so it is for trends and current health, not long historical analysis.
- The app is read-only and not deeply customizable inside itself; build custom reports on the usage objects when you need a different cut.
- An EPT counter on one machine reflects that device, browser, and network; always confirm a pattern in the Usage App before acting.
- Salesforce Optimizer is being retired, so do not build new maintenance routines around it; use the Usage App and Event Monitoring instead.