SessionSight: Visitors

Updated

SessionSight: Visitors

Overview

Use this page to browse and filter visitor profiles tracked by SessionSight. A visitor is a unique individual, identified by an email address, a contact id, or an anonymous device signature, whose sessions SessionSight has recorded for a container (a monitored application or environment). This page turns that raw session data into a searchable, filterable list so you can find one specific visitor or isolate a group matching technical, geographic, or marketing criteria, instead of replaying every session individually.

Visitors only appear here once a SessionSight tracker is installed on a container and is sending session data to its reporting datasource, both set up in SessionSight configuration. From this list you move outward: opening a visitor's detail profile, replaying their last recorded session, or cross-checking conversion drop-off in Funnels.

On this page you select a tenant and container, search directly by identity, and apply filters for date range, country, conversion status, engagement, browser, OS, device, and UTM parameters. Applying filters reloads the visitor list and the summary stat cards; when the underlying datasource is unreachable, the page shows a connection error instead of an empty result.

Key concepts

  • Visitor - A unique individual, identified by an email address, contact id, or anonymous device signature, whose sessions SessionSight has recorded for a container. (related: SessionSight: Replay)
  • Container - A monitored application or environment within a tenant; its underlying reporting datasource is what the visitor list queries. (related: Configuration: SessionSight: SessionSight)
  • Segments - A saved grouping of visitors by criteria. The selector is present on this page but does not currently affect which visitors are returned.
  • Converted - Whether a visitor completed a defined conversion goal, used to separate visitors who converted from those who did not. (related: SessionSight: Funnels)
  • Engagement - A computed per-visitor score reflecting how actively they interacted during their sessions; used both as a filter threshold and as an averaged stat.

When to use it

  • You need to find a specific visitor by email address or contact id to investigate a support case.
  • You want to see who is using a particular container (application or environment) within a given time window.
  • You need to isolate visitors by technical attributes (browser, OS, device) to confirm whether an issue is platform-specific.
  • You need to isolate visitors by marketing attributes (UTM source, medium, campaign) to evaluate a campaign's traffic.
  • You want to check overall visitor volume, conversion rate, and engagement before drilling into individual sessions.
  • You need to jump from a visitor's profile into their last session replay to see exactly what they did.

Before you begin

  • A SessionSight tracker must be installed and sending session data for the container you want to inspect, set up under Configuration: SessionSight: SessionSight.
  • At least one tenant and container with recorded traffic must exist; both are created and configured under Configuration: SessionSight: SessionSight.
  • Your account needs a SessionSight license; without one, the page loads no tenant, container, or visitor data.
  • The container's underlying reporting datasource must be reachable - if it is not, the page shows a connection error instead of visitor data.

Common workflows

Find a specific visitor by identity

Persona: Support operator investigating a customer-reported issue

  1. Select the Tenant and Container that match the customer's environment, or confirm the pre-selected defaults are correct.
    • Expect: The filter bar scopes to that tenant and container.
  2. Enter the visitor's email address or contact id into Find by identity and submit the search.
    • Expect: The platform navigates directly to that visitor's detail profile, bypassing the filtered list.

Verify: You land on the visitor's detail page showing their profile instead of the filtered list.

Filter traffic by campaign and engagement

Persona: Marketing or operations analyst evaluating a campaign

  1. Set UTM Source, UTM Medium, and UTM Campaign to the values of the campaign you're analyzing.
    • Expect: The three UTM fields populate with the typed values; no query has run yet.
  2. Raise Min Engagement to exclude low-engagement visitors, then select Apply.
    • Expect: The visitor list and stat cards reload, now containing only visitors matching the campaign and engagement threshold.

Verify: The stat cards (Total Visitors, Conversion Rate, Avg Engagement) reflect only the filtered campaign traffic, and every row in the list matches the UTM values you entered.

Steps

Step 1

Open Visitors under SessionSight.

Expected result: The page loads with default filters (Tenant LoadGen B.V. (loadgen-main), Container Production Web App, Date Range 1h), but the visitor list and summary stat cards fail to render: a Failed to load visitors message appears because SessionSight cannot reach its reporting datasource, with a Retry link to try again.

This is the entry point for browsing and filtering SessionSight's tracked visitor profiles, so confirming it loads, or diagnosing why it hasn't, is the first step before any filtering task.

  • The Failed to load visitors panel includes a Retry link.
  • The Segments dropdown appears muted, reflecting that segment filtering is not yet applied to results.
  • A Credentials expiring notice flags that the Orders API token needs reissuing under Configuration → Credential Profiles. SessionSight: Visitors - step 1

Field reference

Field Purpose Format / Validation Required Default
Find by identity Jumps directly to a known visitor's detail profile by exact email address or contact id, bypassing the filter bar. Use this when you already have an identifier from a support ticket or CRM record rather than browsing the filtered list. Free text search box No -
Tenant Scopes every other filter and the visitor list to one tenant (top-level account). Switch this to inspect visitor data for a different customer or business unit. Dropdown, single-select No LoadGen B.V. (loadgen-main)
Container Scopes the visitor list to one monitored application or environment within the tenant. The reporting datasource queried for visitor data is tied to this choice, so selecting the wrong container returns the wrong dataset. Dropdown, single-select No Production Web App
Segments Intended to narrow the list to a saved group of visitors matching defined criteria. In the current release this selector does not filter results, so leave it on All segments until it is restored. Dropdown, single-select (shown muted/disabled) No All segments
Date Range Limits the visitor list and summary stats to activity within the selected window. Shorter windows (1h, 4h) load faster and suit checking current traffic; longer windows (24h, 7d) give a broader trend but take longer to query and are more likely to time out, so narrow the range if a search is slow. Segmented button group (1h, 4h, 8h, 24h, 7d, and additional options) No 1h
Country Filters visitors to those whose recorded location matches this value. Use it to isolate traffic from a specific region, for example when investigating a regional outage or campaign. Free text No -
Converted Filters visitors by whether they completed a defined conversion. Choose a specific value instead of All to isolate converting visitors (to study what worked) or non-converting visitors (to investigate drop-off). Dropdown, single-select No All
Min Engagement Excludes visitors whose computed engagement score falls below this threshold. Raise it to focus on highly engaged visitors, useful when prioritizing follow-up; lower it or leave it blank to include light or single-page visits. Number No -
Browser Filters visitors by browser name. Use this to isolate a browser-specific issue, for example when a bug report mentions a particular browser. Free text No -
OS Filters visitors by operating system. Use this to narrow down platform-specific behavior, such as comparing engagement across desktop and mobile operating systems. Free text No -
Device Filters visitors by device type. Use this to check whether an issue or conversion drop is isolated to one device class. Free text No -
UTM Source Filters visitors by the recorded UTM source, letting you isolate traffic from one acquisition source such as a search engine or newsletter. Free text No -
UTM Medium Filters visitors by the recorded UTM medium, letting you compare traffic delivered through different channel types, such as paid versus organic. Free text No -
UTM Campaign Filters visitors by the recorded UTM campaign, letting you isolate visitors driven by one specific marketing campaign to measure its traffic and conversion. Free text No -
Sort By Controls the order of the visitor list. The default, Last Seen (newest), surfaces the most recently active visitors first; switch it when you need the earliest visitors or a different ranking instead. Dropdown, single-select No Last Seen (newest)

Controls reference

Apply

Runs the visitor query using the current values in every filter field.

When to use: After changing one or more filters, to refresh the list and stat cards to match.

Side effects: Read-only: re-queries and replaces the visitor list and stat cards; does not change any stored data.

Clear

Resets every filter field back to its default value (default tenant and container, All segments, 1h date range, blank text filters, Converted set to All, default sort).

When to use: When you want to start a new search from a clean filter state instead of adjusting each field individually.

Side effects: Read-only: resets the filter bar inputs; does not by itself delete or modify stored data.

Retry

Re-attempts to load the visitor list and stat cards after a failed load.

When to use: When the page shows Failed to load visitors, to confirm whether the reporting datasource is reachable again.

Side effects: Read-only: re-runs the same query with the current filters; does not change filters or stored data.

Close (credentials notice)

Dismisses the credential-expiry notification banner.

When to use: Once you've noted the expiring credential, or after reissuing it, to clear the banner from view.

Side effects: Read-only: hides the notice for this session; does not reissue or extend the credential itself.

Open (visitor row)

Opens the selected visitor's detail profile.

When to use: When you want to inspect one visitor's full history, sessions, and attributes instead of just their summary row.

Side effects: Read-only: navigates to the visitor's detail page; does not change the visitor list.

Replay last session

Opens the visitor's most recently recorded session in SessionSight: Replay.

When to use: When you need to watch exactly what the visitor did, rather than reading aggregated attributes.

Side effects: Read-only: navigates away to the replay viewer; does not modify the visitor record.

Previous / Next

Moves the visitor list one page backward or forward.

When to use: When the filtered visitor list spans more rows than fit on one page.

Side effects: Read-only: changes which page of results is displayed; filters and sort order are unchanged. Next is disabled once you reach the last page.

Configure / SessionSight configuration

Links to the SessionSight configuration page to set up tenants, containers, and tracker installation.

When to use: When no tenant, container, or tracker exists yet, or when you need to adjust tracking setup rather than just browsing visitors.

Side effects: Read-only: navigates away to the configuration page; makes no changes by itself.

Verify the result

When the primary task succeeds, the Visitors page replaces the results area with a row of summary stats (Total Visitors, Converted, Conversion Rate, Avg Engagement, Avg Sessions, Countries) and a list of visitor rows matching your current filters, ordered by the chosen Sort By value. Each row lets you open that visitor's detail profile or jump to their last session's replay. If the list is empty, the page shows a No Visitors Found heading instead of rows; check that Tenant, Container, and Date Range aren't too narrow before assuming there's no traffic. If instead you see Failed to load visitors, the problem is connectivity to the reporting datasource, not an empty result; start with Retry, then check the container's datasource configuration.

Troubleshooting

  • Symptom: The page shows "Failed to load visitors: SessionSight cannot reach its reporting datasource." Fix: Select Retry; if it fails again, confirm the selected container's reporting datasource is online before assuming there's no visitor traffic.
  • Symptom: A search with a wide Date Range (such as 24h or 7d) seems to hang. Fix: Narrow the date range and add more filters (tenant, container, UTM, or engagement), then retry; wide, unfiltered ranges are more likely to exceed the query time limit.
  • Symptom: Changing Segments does not change the visitor list. Fix: This is expected in the current release; the Segments filter does not yet affect results, so use the other filter fields (Country, Converted, Browser, OS, Device, UTM) to narrow the list instead.
  • Symptom: The visitor list shows No Visitors Found even though you expect traffic. Fix: Check that Tenant and Container match the environment you're investigating, then widen the Date Range before concluding there's no traffic.
  • Symptom: A Credentials expiring banner covers part of the filter bar. Fix: Dismiss it with its close control, then reissue the named token under Configuration: Credential Profiles before it expires.
Was this article helpful?
0 out of 0 found this helpful