SessionSight: Dashboard
Overview
Use this page to monitor session, visitor, and conversion analytics for a selected application. SessionSight Dashboard is the single-page overview of a tracked web application's engagement: how many sessions and unique visitors it gets, what events they trigger, how they move through your defined goals and funnels, and who is active on the site right now. It solves the problem of having to pull raw analytics data out of the underlying datastore by surfacing it as ready-to-read KPIs and charts for whichever tenant and container you are responsible for.
Before this page shows anything, a tenant and a container (the tracked application) must already exist with a working SessionSight datasource connection, plus any goals and funnels you want to measure, all set up under Configuration: SessionSight: SessionSight and Configuration: Datasources. What you learn here drives other work: an expiring credential sends you to Configuration: Credential Profiles, while a shallow or surprising KPI sends you to SessionSight: Visitors, SessionSight: Heatmaps, or SessionSight: Funnels for visitor-level detail.
On this page itself, you pick the tenant, container, segment, and time range, search by visitor identity, read six KPI and chart cards, and refresh the whole page or retry a single failed card without leaving it.
Key concepts
- Container - the tracked web application whose analytics this dashboard displays; its SessionSight datasource is derived automatically from the container you pick. (related: Configuration: SessionSight: SessionSight)
- SessionSight datasource - the InfluxDB connection that stores and serves a container's session, event, and conversion data; every card on this page depends on it being reachable. (related: Configuration: Datasources)
- Segment - a saved visitor filter you can pick from the Segment dropdown; currently none of this page's cards apply it, so picking one does not change what you see here. (related: SessionSight: Visitors)
- Realtime - the live visitor feed on this page, refreshed every 15 seconds regardless of the Time range you have selected.
When to use it
- Review recent session, visitor, and conversion trends for a specific tenant and container.
- Watch realtime visitor activity during a release, campaign, or load test.
- Confirm goal and funnel conversion rates after a configuration or campaign change.
- Diagnose a "Couldn't load this card." error before escalating it as a datasource outage.
- Catch a SessionSight-related credential before it expires.
Before you begin
- A tenant and at least one container (tracked web application) exist and point to a working SessionSight datasource, set up under Configuration: SessionSight: SessionSight.
- The container's datasource is reachable and its InfluxDB organization name is entered correctly in Configuration: Datasources.
- Any Bearer token or credential the datasource depends on is valid and not close to expiry, managed in Configuration: Credential Profiles.
- Goals and funnels you want to see under Goal Conversions and Funnel Performance have already been defined for this container.
- Your account has the SessionSight module licensed; an unlicensed visit loads no data and starts no realtime feed.
Common workflows
Review session and conversion health for an application
Persona: Load-test operator
- Select the tenant and container you want to review from the Tenant and Container dropdowns.
- Expect: The page reloads all cards for that tenant/container combination.
- Pick a Time range preset, or Custom, that covers the period you want to inspect.
- Expect: Sessions over time, Event Distribution, Goal Conversions, and Funnel Performance reload for the new window; Realtime is unaffected since it always shows its own live feed.
- Read the KPI summary row (Sessions, Visitors, Events, Conversion Rate, Avg Engagement, Active Visitors) together with the charts below it.
- Expect: Each card shows its current value or chart for the selected window, or a "Couldn't load this card." placeholder with a Retry button if its query failed.
Verify: The KPI row and all five chart cards show real values and charts instead of "Couldn't load this card." placeholders for the selected tenant, container, and time range.
Resolve a datasource error shown on the dashboard
Persona: Admin / configuration owner
- Read the red banner stating that SessionSight couldn't load any analytics at the top of the page.
- Expect: You see that every card failed for a datasource/connection reason, not because the data is genuinely empty.
- Click the SessionSight datasource link inside the banner.
- Expect: The relevant datasource configuration opens so you can check the connection and the InfluxDB organization name for exact spelling and case.
- Fix the connection or organization name there, then return to the dashboard and click Refresh.
- Expect: The cards re-query the datasource; if the fix worked, the error banner and the per-card "Couldn't load this card." placeholders are replaced by real KPI values and charts. If not, the same errors reload.
Verify: The top error banner is gone and the KPI summary row plus all five cards show data instead of Retry placeholders.
Steps
Step 1
Open the Dashboard page under SessionSight.
Expected result: The filter row loads with Tenant (LoadGen B.V.), Container (Production Web App), Segment (All segments), and a partly visible time range control, alongside a Credentials expiring notification. Below it, a red banner reports that SessionSight couldn't load any analytics, and every card (summary row, Sessions over time, Event Distribution, Realtime, Goal Conversions, Funnel Performance) shows "Couldn't load this card." with its own Retry button.
This starting state tells you immediately whether the page's analytics are actually usable before you read any KPI as real data.
- The Credentials expiring notification names the expiring token and the Configuration → Credential Profiles page to reissue it.
- The error banner's SessionSight datasource link and the InfluxDB organization-name hint point at the likely root cause.
- Each failed card has its own Retry button in addition to the one on the top banner.
Step 2
Click Refresh.
Expected result: The cards re-query the SessionSight datasource, but the result is unchanged: the same error banner and six "Couldn't load this card." placeholders reload, each with its own Retry button. The Credentials expiring notification closes, which uncovers the full time range row showing 1h, 4h, 8h, 24h, 7d, and Custom, with 24h active.
Retrying confirms this is a persistent datasource/connection problem rather than a one-off glitch, which is the first thing to rule out before troubleshooting individual cards.
- Refresh re-queries every card without navigating away from the page.
- Each failed card keeps its own Retry button so you can retry just one card instead of the whole page.
- The time range row now shows 24h as the active preset; Custom opens a date range picker for a specific window.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Tenant | Selects the customer/organization whose data this dashboard shows. Switching tenants changes which containers and data are available; use it only in multi-tenant deployments. | dropdown | No | LoadGen B.V. |
| Container | Selects which tracked web application's analytics to display. Because the datasource is derived from the container, switching containers reloads every card with a completely different dataset. | dropdown | No | Production Web App |
| Segment | Intended to narrow the dashboard to one saved visitor segment. None of this page's analytics calls currently accept a segment filter, so changing this selector does not change any card's data yet. | dropdown | No | All segments |
| Time range | Sets the lookback window for Sessions over time, Event Distribution, Goal Conversions, and Funnel Performance (Realtime always shows its own live window). Shorter presets (1h, 4h) load faster and show granular near-term activity; longer presets (24h, 7d) show broader trends but take longer and can trigger a view-timeout error if the window is too wide. | preset button group: 1h, 4h, 8h, 24h, 7d | No | 1h |
| Custom | Opens a date range picker so you can set an exact start and end window outside the presets, for example to reproduce a specific incident window. A very wide custom range carries the same timeout risk as 7d. | date range picker | No | - |
| Find by identity | Looks up analytics tied to one specific visitor identity instead of the aggregate data shown across all visitors. | free text search | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Sessions | KPI metric: total count of sessions started within the selected time range for the chosen container. | A falling count versus the prior period can mean fewer visits or a tracking problem; cross-check against Visitors. |
| Visitors | KPI metric: count of unique visitors, deduplicated by identity, within the selected time range. | Compare to Sessions: a high Sessions-to-Visitors ratio means visitors are returning multiple times in the window. |
| Events | KPI metric: total count of tracked interaction events captured in the time range. | A sudden drop usually points at a tracking break on the site rather than fewer visitors. |
| Conversion Rate | KPI metric: percentage of sessions that completed at least one defined goal within the time range. | Read alongside Goal Conversions and Funnel Performance to see which goal or step is driving the rate. |
| Avg Engagement | KPI metric: average engaged time or interaction depth per session in the time range. | A falling average alongside stable Sessions suggests visitors are leaving pages faster, not that fewer people are arriving. |
| Active Visitors | KPI metric: count of visitors currently active, driven by the Realtime feed. | This reflects only the live window and is independent of the Time range selector. |
| Sessions over time | Chart card: a daily time-series of session counts across the selected time range. | Watch the trend line for a sudden drop at a point in time rather than trusting the single aggregate KPI. |
| Event Distribution | Chart card: breakdown of tracked event types over the last 5 minutes, a fixed window independent of the Time range selector. | Compare relative segment sizes to see which event type dominates traffic right now. |
| Realtime | Card: live feed of active visitors, refreshed every 15 seconds, with a green status dot while the feed is connected. | The green dot confirms the feed is live; if it is missing, retry the card rather than trusting the last number shown. |
| Goal Conversions | Card: conversion results for goals defined for this container. | If no goals are defined yet, use the Create a goal in Configure link on this card instead of expecting data. |
| Funnel Performance | Card: step-by-step completion rates for funnels defined for this container. | If no funnels are defined yet, use the Create a funnel in Configure link on this card instead of expecting data. |
Controls reference
Configure
Opens the SessionSight configuration area for this container and tenant (goals, funnels, tracking setup).
When to use: When you need to define or change tracking setup, goals, or funnels, instead of just viewing existing data.
Side effects: Read-only navigation away from the dashboard; nothing on this page's data is changed.
Refresh
Re-runs the data queries for every card on the page using the current Tenant, Container, Segment, and Time range selection.
When to use: After changing a filter, or to check whether a previously failed card has recovered.
Side effects: Re-triggers backend calls for all cards and replaces their contents with the fresh result, whether that is data or the same error.
Retry
Re-queries only the one card it belongs to (summary row, Sessions over time, Event Distribution, Realtime, Goal Conversions, Funnel Performance, or the top error banner).
When to use: When only a single card failed to load while the rest of the page is fine, to avoid re-running every card.
Side effects: Reloads that one card only; no effect on other cards or on the current filters.
SessionSight datasource
Opens the datasource configuration for this container's SessionSight connection.
When to use: When the top banner reports a datasource/connection problem and you need to check or correct the connection, such as the InfluxDB organization name.
Side effects: Read-only navigation; no change happens on the dashboard itself.
Credential Profiles link
Opens the credential profile behind the datasource, such as the Orders API Bearer token, so you can reissue it.
When to use: When the Credentials expiring notification appears, ideally before the stated expiry date.
Side effects: Read-only navigation from this page; reissuing the credential happens on the destination page.
Close (notification)
Dismisses the Credentials expiring notification banner.
When to use: Once you have noted the expiry, or already reissued the credential, and no longer need the reminder visible.
Side effects: Only hides the banner for this session; it does not reissue the credential or stop it from expiring.
Create a goal in Configure
Opens the SessionSight configuration page to define a new goal.
When to use: When Goal Conversions has nothing to show because no goal is defined yet for this container.
Side effects: Read-only navigation; the goal itself is created on the destination page.
Create a funnel in Configure
Opens the SessionSight configuration page to define a new funnel.
When to use: When Funnel Performance has nothing to show because no funnel is defined yet for this container.
Side effects: Read-only navigation; the funnel itself is created on the destination page.
Verify the result
When the dashboard is working, the KPI summary row shows real values for Sessions, Visitors, Events, Conversion Rate, Avg Engagement, and Active Visitors, and the Sessions over time, Event Distribution, Realtime, Goal Conversions, and Funnel Performance cards render charts instead of error text. No red "SessionSight couldn't load any analytics" banner appears above the KPI row, and no individual card shows "Couldn't load this card." with a Retry button. The Realtime card's green status dot next to its live label stays on, confirming the feed is connected. If a single card still shows Retry after clicking Refresh, the problem is isolated to that card's own query (for example, a missing goal or funnel definition) rather than the whole datasource connection.
Troubleshooting
- Symptom: The red banner reports that SessionSight couldn't load any analytics and every card shows "Couldn't load this card." Fix: This is a datasource/connection problem, not an empty dataset; open the SessionSight datasource link in the banner and verify the InfluxDB organization name (exact spelling and case) in Configuration: Datasources, then click Refresh.
- Symptom: A Credentials expiring notification names a Bearer token and a number of days until expiry. Fix: Reissue that token under Configuration: Credential Profiles before it expires; an expired token produces the same datasource-connection failure described above.
- Symptom: Only the Goal Conversions or Funnel Performance card fails to load while the rest of the page is fine. Fix: Use that card's own Retry button first; if it keeps failing, confirm a goal or funnel actually exists for this container using the Create a goal in Configure or Create a funnel in Configure link on the card.
- Symptom: A card reports that the view timed out and asks you to try a narrower date range. Fix: Pick a shorter Time range preset, such as 1h or 4h instead of 7d or a wide Custom range, then retry.
- Symptom: Changing the Segment dropdown does not change any numbers on the page. Fix: This is expected for now; none of this page's analytics cards currently filter by segment, so use SessionSight: Visitors if you need segment-scoped data.
- Symptom: Clicking Refresh reloads the same errors instead of fixing them. Fix: Refresh only re-runs the same queries; it cannot repair a broken datasource connection or an expired credential, so resolve the underlying connection or credential first, then refresh again.
Related articles
- Prerequisite: Configuration: SessionSight: SessionSight - defines the tenant, container, datasource link, goals, and funnels this dashboard displays
- Prerequisite: Configuration: Datasources - the SessionSight datasource connection that must be healthy for any card to load
- See also: Configuration: Credential Profiles - reissue the Bearer token named in the Credentials expiring notification
- Next step: SessionSight: Visitors - drill into individual visitor-level data behind the dashboard's aggregate KPIs
- Next step: SessionSight: Funnels - inspect or build the funnels summarized in Funnel Performance
- See also: SessionSight: Heatmaps - see where visitors interact on the page, complementing the Event Distribution card