SessionSight: Dashboard
Overview
Use this page to monitor session, visitor, and funnel analytics for a web application. The Dashboard is SessionSight's analytics landing page: it aggregates sessions, unique visitors, tracked events, goal conversions, and funnel completions for one application into a single view, so you can judge how real users are behaving without querying raw tracking data yourself.
Before this page can show anything, a SessionSight datasource connection and the application's tracking configuration must already exist, and any goals or funnels you want to measure must be defined first. The Dashboard reads from that configuration: changing the Tenant or Application selector switches which underlying datasource it queries. From here, the Realtime card and Find by identity results point you toward the more detailed Visitors, Heatmaps, Funnels, and Replay pages when you need to drill into a specific session or step.
On this page you choose the tenant, application, date range, and an optional visitor identity to scope every card; refresh the whole page or retry a single failed card; and open Configure to fix tracking, datasource, goal, or funnel setup without leaving the flow.
Key concepts
- Tenant - The organizational account whose SessionSight data you're viewing. Each tenant's sessions, events, and goals are kept separate from other tenants.
- Application - A tracked web site whose visitor sessions SessionSight collects. The Dashboard's datasource is automatically derived from the selected application's configuration. (related: Configuration: SessionSight: SessionSight)
- SessionSight datasource - The underlying connection SessionSight queries for session, event, goal, and funnel data. Every card on this Dashboard depends on it being reachable and correctly configured. (related: Configuration: Datasources)
- Goal - A defined conversion event, such as a completed purchase or form submission, that the Goal Conversions card measures over the selected date range. (related: Configuration: SessionSight: SessionSight)
- Funnel - An ordered sequence of steps a visitor is expected to complete. The Funnel Performance card shows how many visitors reach each step. (related: SessionSight: Funnels)
When to use it
- Check current session, visitor, and engagement volume for an application.
- Watch active visitors in real time during a launch, campaign, or load test.
- Review goal conversion rate and funnel completion over a chosen date range.
- Diagnose a SessionSight datasource or connection failure before escalating it.
- Compare shorter and longer date ranges to spot traffic anomalies.
- Look up a specific visitor's activity by identity.
Before you begin
- A SessionSight datasource connection exists and its organization name is set correctly (configured in Configuration: Datasources).
- The web application you want to monitor is set up as a SessionSight application so it appears in the Application selector (configured in Configuration: SessionSight: SessionSight).
- At least one goal or funnel is defined for the application if you want the Goal Conversions or Funnel Performance cards to show data (created via Configure on this page, or in Configuration: SessionSight: SessionSight).
- You belong to a tenant with SessionSight data; the Tenant selector only lists tenants you have access to.
Common workflows
Review session and engagement trends for an application
Persona: Load-test or web operations admin
- Select the application you want to review from the Application selector.
- Expect: The Dashboard reloads every card (KPI row, Sessions over time, Event Distribution, Realtime, Goal Conversions, Funnel Performance) scoped to the selected application's SessionSight datasource.
- Choose a date range, such as 24h, from the toolbar.
- Expect: The chosen button switches to its active/highlighted style and every card's query reruns for that window.
- Click Refresh to confirm you're viewing the latest data.
- Expect: All cards re-query and update in place without changing any filter.
Verify: The KPI row and charts populate with numeric values instead of "Couldn't load this card." messages, and the Realtime card's Live indicator keeps counting.
Recover from a datasource connection error
Persona: Admin troubleshooting SessionSight
- Read the red banner at the top of the Dashboard to confirm every card failed with the same backend error.
- Expect: The banner names the probable cause, a datasource or connection problem, and surfaces a SessionSight datasource link and a page-level Retry button.
- Click SessionSight datasource to open its configuration and verify the organization name.
- Expect: SessionSight configuration opens so you can check and correct the connection.
- Return to the Dashboard and click the page-level Retry.
- Expect: Every card re-queries; if the connection is now correct, the error banner and per-card "Couldn't load this card." messages are replaced with live data.
Verify: The red page-level banner is gone and each card shows data (or its normal empty-state prompt) instead of a load error.
Steps
Step 1
Open the Dashboard.
Expected result: The Dashboard loads with the LoadGen B.V. tenant, Production Web App application, and 24h date range selected by default. In this capture, every card reports a backend load failure, with a red page-level banner pointing to a datasource or connection problem.
Confirming which tenant, application, and date range are active is the starting point before you investigate data or adjust filters.
- Tenant defaults to LoadGen B.V. and Application defaults to Production Web App.
- The 24h date-range button is highlighted as the active selection.
- A red banner reports every card failed and links to SessionSight datasource.
Step 2
Click Refresh in the toolbar.
Expected result: The Dashboard re-queries every card for the current tenant, application, and date range. Because the underlying datasource connection problem hasn't been fixed yet, the page-level banner and each card's "Couldn't load this card." message reappear.
Refreshing confirms whether a failure was transient or whether the SessionSight datasource connection still needs to be fixed before any card shows data.
- Refresh immediately re-runs every card's query without changing tenant, application, date range, or identity filter.
- Each card keeps its own Retry control if only that one card fails next time.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Tenant | Choose which tenant's SessionSight data to view. Switching tenants reloads every card for the newly selected organization, so use it to move between accounts you manage. | dropdown, one entry per tenant you have access to | No | LoadGen B.V. |
| Application | Choose which tracked web application to view analytics for. Because each application's SessionSight datasource is derived from its own configuration, changing this field also changes which backend data source the Dashboard queries. | dropdown, one entry per configured application | No | Production Web App |
| Find by identity | Search for one visitor's analytics trail by identity instead of viewing aggregate traffic. Use this when investigating a specific user's journey rather than overall trends. | free-text search box, placeholder "Find by identity..." | No | - |
| Date range | Set the time window every card queries. Shorter windows (1h, 4h, 8h) show fresher, more granular activity and are useful for watching an in-progress event; longer windows (24h, 7d) smooth out noise to reveal trend but hide per-minute detail. Custom lets you pick an explicit start and end. | preset buttons (1h, 4h, 8h, 24h, 7d) or Custom | No | 24h |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Sessions | Reports how many sessions were started on the selected application within the chosen date range. | A rising count indicates more site visits within the selected window; compare it against Visitors to see how many sessions come from repeat visitors. |
| Visitors | Reports how many unique visitors, deduplicated by identity, were active in the date range. | A Sessions count much higher than Visitors means visitors are returning for multiple sessions rather than most traffic being new. |
| Events | Reports how many tracked interaction events (such as clicks or page views) were recorded across all sessions in the date range. | A high Events count relative to Sessions suggests visitors are interacting heavily within each session rather than bouncing. |
| Conversion Rate | Reports the percentage of sessions that completed at least one defined goal in the date range. | Track this alongside Goal Conversions to see which goals are driving or dragging the overall rate. |
| Avg Engagement | Reports the average engagement per session for the selected date range. | - |
| Active Visitors | Reports how many visitors are on the application right now, independent of the selected date range. | This pairs with the Realtime card's live feed rather than the historical Date range selector. |
| Sessions over time | Plots session volume per day, in UTC, across the selected date range. | Look for spikes or drops that line up with deployments, campaigns, or incidents. |
| Event Distribution | Breaks down tracked event types recorded in the last 5 minutes. | Use it to see which interaction types are currently most common, independent of the Date range filter. |
| Realtime | Shows currently active visitors and live activity, refreshing automatically. | The green "Live" indicator confirms polling is active; it keeps updating even if the card's own data failed to load, since the indicator reflects connection status, not data success. |
| Goal Conversions | Lists each defined goal with how many sessions completed it in the selected date range. | If no goals are defined yet, this card prompts you to create one instead of showing data. |
| Funnel Performance | Shows how many visitors reached each step of a defined funnel in the selected date range. | The step with the largest drop from the previous one is where the most visitors are abandoning the funnel. If no funnels are defined yet, this card prompts you to create one instead. |
Controls reference
Configure
Opens SessionSight's configuration area for the current application, covering datasources, goals, funnels, and tracking settings.
When to use: Use it to set up goals or funnels, or to fix a datasource or application configuration issue referenced in an error banner.
Side effects: Read-only navigation: it leaves the Dashboard and opens the configuration page without changing any data itself.
Refresh
Re-runs the queries behind every card on the Dashboard for the current tenant, application, date range, and identity filter.
When to use: Use it to pull in the latest data, or to re-check whether a card that previously failed now loads.
Side effects: Re-executes backend queries and replaces the on-screen data for every card; it does not change any stored configuration or filter value.
Retry (page-level)
When to use: Use it after the red banner reports every card failed, once you've addressed the underlying datasource or connection problem.
Side effects: Re-runs all card queries; if the underlying problem isn't fixed, the same page-level errors and per-card "Couldn't load this card." messages reappear.
Retry (per-card)
When to use: Use it when only a single card shows "Couldn't load this card." while the others loaded successfully.
Side effects: Re-runs that one card's query only; other cards, filters, and the page-level banner are unaffected.
SessionSight datasource
Opens the configuration page for the SessionSight datasource connection named in the error banner.
When to use: Use it when the page-level error banner reports a datasource or connection problem, to inspect or correct the connection and its organization name.
Side effects: Read-only navigation; opens the datasource configuration page and does not change the Dashboard.
Create a goal in Configure
Opens SessionSight configuration to define a new conversion goal for the current application.
When to use: Use it when the Goal Conversions card has no goals defined yet for this application (not the error state shown when a datasource fails).
Side effects: Read-only navigation from the Dashboard; the goal itself is created on the configuration page, not here.
Create a funnel in Configure
Opens SessionSight configuration to define a new funnel for the current application.
When to use: Use it when the Funnel Performance card has no funnels defined yet for this application (not the error state shown when a datasource fails).
Side effects: Read-only navigation from the Dashboard; the funnel itself is created on the configuration page, not here.
Verify the result
When the Dashboard is working normally, the red page-level banner is gone and the KPI row shows numeric values for Sessions, Visitors, Events, Conversion Rate, Avg Engagement, and Active Visitors instead of an error. Sessions over time, Event Distribution, Goal Conversions, and Funnel Performance show charts or lists instead of "Couldn't load this card.", and the Realtime card's Live indicator keeps updating every 15 seconds. If a single card still fails while the rest load, the problem is isolated to that card's own query. If every card fails together, check the SessionSight datasource connection and its organization name first.
Troubleshooting
- Symptom: The red banner reports every card failed and mentions a datasource/connection problem. Fix: Open SessionSight datasource from the banner, verify the connection's organization name matches exactly (including case), then use the page-level Retry.
- Symptom: Only one card, such as Goal Conversions or Funnel Performance, shows "Couldn't load this card." while the rest of the page loads. Fix: Click that card's own Retry; if it keeps failing, the goal or funnel definitions behind it may be missing or broken rather than the datasource connection.
- Symptom: A card or the whole view times out instead of showing a clear error. Fix: Pick a narrower date range, such as 1h or 4h instead of 24h or 7d, and retry; wide ranges on high-traffic applications are more likely to time out.
- Symptom: Goal Conversions or Funnel Performance stays empty even though the rest of the Dashboard loads. Fix: Use Configure to create a goal or funnel for this application; the card has nothing to show until at least one is defined.
- Symptom: Switching the Application selector doesn't show the data you expect. Fix: Confirm you selected the correct application; each application's datasource is tied to its own container configuration, so analytics do not mix between applications.
Related articles
- Prerequisite: Configuration: SessionSight: SessionSight - defines the application, goals, and funnels this Dashboard reads
- Prerequisite: Configuration: Datasources - the SessionSight datasource connection and organization name must be configured before any card can load
- Next step: SessionSight: Visitors - drill into individual visitors found via Find by identity or the Realtime card
- Next step: SessionSight: Funnels - review or edit the funnels summarized in the Funnel Performance card
- See also: SessionSight: Heatmaps - visualize on-page engagement behind the session and event metrics