> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/leverage/insights-and-analytics/impact-analysis.md). # Impact Analysis **Impact Analysis** is a dashboard inside Arcade that shows how your audience engages with your content — both across your whole workspace and for individual accounts. Teams put real work into building and publishing demos; Impact Analysis is where you see what's landing, who's engaging, and where to invest next. > **Availability:** Impact Analysis is available on **Enterprise** plans. Your historical data is backfilled automatically, so there's meaningful data the first time you open it. *** #### How do I open Impact Analysis? Click **Impact Analysis** in the left sidebar of your Arcade workspace. No setup or connection is required — the dashboard populates from your existing demo activity. *** #### What can I see? Impact Analysis works at two levels: an aggregate view across your workspace, and a detailed view for any single account. **Aggregate view** * *Engagement over time* — how demo engagement trends across your workspace, so you can see whether it's growing. * *Most engaged accounts* — which companies are spending the most time in your content, ranked so the most active accounts surface first. **Account view** Click into any account to double-click into that customer's engagement: * *Views and total plays* — how much that account has viewed and played your demos. * *Top demos* — exactly which demos are driving engagement for that account, so you know what that customer cares about. *** #### What do "views" and "plays" mean? Impact Analysis uses the same engagement metrics as the rest of Arcade: * *Views* — a demo being loaded and seen by a viewer. * *Plays* — a viewer interacting with the demo (clicking, hovering, or tapping through steps). For the full definitions, including exactly when a view or play is counted, see Insights & Analytics. *** #### How is engagement attributed to an account? Accounts are identified from the same viewer-identification signals Arcade already uses across Insights. The more of your viewers Arcade can identify, the richer your account-level view will be. To improve identification, see Identifying Viewers. *** #### How should I use it? * **Reps** — see which of your accounts are most engaged, and what content they're spending time on, before a call or follow-up. * **Content teams** — decide where to invest effort by spotting which demos drive the most engagement. * **Everyone** — track engagement over time to understand whether your content is resonating and growing. *** #### Data freshness Engagement data is aggregated on a rolling basis rather than in real time, so very recent activity may take some time to appear. Historical data is backfilled automatically when your workspace gets access. *** #### Troubleshooting **I don't see Impact Analysis in my sidebar.** Impact Analysis is an Enterprise feature. If you're on Enterprise and still don't see it, reach out to your CSM or [support](mailto:support@arcade.software). **An account shows views but few or no plays.** Views count a demo being seen; plays require interaction. An account can view content without clicking through it. **I expected to see revenue or pipeline data.** Impact Analysis focuses on engagement — views, plays, and which demos accounts spend time in. It does not pull in CRM revenue or pipeline data. *** #### FAQ **Do I need to connect a CRM or install anything?** No. Impact Analysis works from your existing Arcade demo activity with no integration or setup. **Does my whole team see the same data?** Yes — Impact Analysis reflects workspace-level engagement, and account detail is available to anyone with access to the dashboard. **Which plans include Impact Analysis?** Enterprise plans. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.arcade.software/kb/leverage/insights-and-analytics/impact-analysis.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.