SessionSight: Funnels and forms

Updated

SessionSight: Funnels and forms

Overview

Use this page to build and save visitor funnels. A funnel is an ordered sequence of steps, each a condition such as a page view, click, form interaction, goal, or event, that measures how many visitor sessions complete every step in order and exactly where the rest drop off before the last step.

Funnels and forms sits inside SessionSight, which must already be licensed and tracking visitor sessions for a configured container before any step produces data. The steps you define here can be handed to the workload composer through Use as path, turning a real visitor flow into a load test scenario, while a saved funnel stays available in Saved funnels for ongoing conversion tracking.

On this page you choose the tenant, container, time range and base segment, define or edit a funnel's steps, compare a second segment such as synthetic test traffic against the base, read live conversion and drop-off tiles, and switch to the Forms tab for the same context's form analysis.

Key concepts

  • funnel - An ordered sequence of steps, each a condition such as a page view, click, form action, goal, or event, that measures how many visitor sessions complete every step in order and where the rest drop off. (related: SessionSight: Journeys)
  • segment - A named filter over visitor sessions, such as Real users, that sets which sessions count as the base population a funnel is measured against. (related: SessionSight: Dashboard)
  • compare with - A second segment, such as Synthetic (LoadGen runs) or Had a JS error, whose conversion is drawn alongside the base segment so you can see whether that subset of visitors behaves differently.
  • saved funnel - A funnel definition you have named and stored so you can reopen, recompute, or edit it later instead of rebuilding its steps from scratch.
  • step - One stage of a funnel defined by a condition type, an operator, and a value, for example Viewed page is /pricing; a visitor session must satisfy each step in order to still count as converting.

When to use it

  • To find where visitors abandon a multi-step flow, such as a pricing page followed by a signup form.
  • To check whether synthetic load test traffic follows the same path as real visitors, using the Synthetic (LoadGen runs) compare-with chip.
  • After a release, to see whether a drop in conversion lines up with a specific step.
  • To measure typical time-to-convert for a workflow with MEDIAN TIME TO CONVERT.
  • To isolate funnel performance for a specific group, such as visitors who had a JS error or did not reach a goal.
  • To turn a real visitor flow into a load test scenario with Use as path.

Before you begin

  • SessionSight must be licensed for your tenant; an unlicensed tenant shows no context bar, saved funnels, or computed data on this page.
  • A container with visitor session data must exist and be selectable, for example Production Web App; containers are configured in Configuration: SessionSight: SessionSight.
  • Your account needs the SessionSightConfig or SessionSightAdmin role to Save or Delete a funnel; an Analyst role can build and compute steps but is told it cannot save.
  • Decide the base segment and time range you want the funnel measured against before adding steps, since changing either recomputes the result.

Common workflows

Build and save a funnel for a key flow

Persona: SessionSight administrator or analyst with write access

  1. Select the tenant, container, time range and base segment in the context bar.
    • Expect: Saved funnels and the step editor reload scoped to that tenant, container, range and segment.
  2. Enter a name in NAME and set Step 1's condition type, operator and value, for example Viewed page, is, /pricing.
    • Expect: The step row shows the condition; the tiles still read 0% and n/a until a second step completes the funnel.
  3. Add further steps and select Refresh.
    • Expect: CONVERSION THROUGH ALL STEPS, MEDIAN TIME TO CONVERT, BIGGEST DROP and the STEPS bars recompute for the entered steps and current filters.
  4. Select Save.
    • Expect: The funnel is added to Saved funnels under the name you entered, or updated if one was already selected.

Verify: The funnel now appears as a row in Saved funnels, and selecting it reloads the same steps and the same recomputed tiles.

Compare synthetic load test traffic against real visitors

Persona: Load test operator checking whether synthetic traffic follows the same path as production visitors

  1. With the base segment set to Real users, select the Synthetic (LoadGen runs) compare-with chip.
    • Expect: The chip becomes the active comparison; a second series for synthetic sessions is set to be drawn alongside the Real users base.
  2. Select Refresh.
    • Expect: The KPI tiles and STEPS bars recompute, showing the Real users conversion against the Synthetic (LoadGen runs) comparison for the current steps.

Verify: The STEPS panel shows two distinguishable series, Real users and Synthetic (LoadGen runs), letting you see at which step the two diverge.

Send a funnel's steps into a load test workload

Persona: Load test operator preparing a new scenario from an observed visitor flow

  1. Open a saved funnel from the Saved funnels list, or finish building new steps.
    • Expect: The editor shows that funnel's steps and condition values.
  2. Select Use as path.
    • Expect: The steps are handed to the workload composer as a starting path, for example to script a scenario against a system under test such as sut-crane-08.

Verify: A new workload draft opens pre-populated with the funnel's steps, while the original funnel in Saved funnels is unchanged.

Steps

Step 1

Open Funnels and forms under SessionSight.

Expected result: The page loads the shared context bar scoped to LoadGen B.V., Production Web App, 7d and Real users, shows an empty Saved funnels panel, and shows a New funnel draft already holding two starter steps, both Viewed page is /pricing.

This is the starting point for building, computing and saving a funnel.

  • Saved funnels reads "No saved funnels yet" until you build and save one.
  • The 7d quick range and Real users segment are the defaults this draft computes against.
  • The Synthetic (LoadGen runs) compare-with chip is selected by default alongside the Real users base. SessionSight: Funnels and forms - step 1

Tabs on this page

  • Funnels - Build, compute and save step-by-step conversion funnels from pages, clicks, forms, goals and events, with compare-with segments and conversion and drop-off KPI tiles.
    • Saved funnels list, NAME, Step condition type / operator / value rows, compare-with chips, and the CONVERSION THROUGH ALL STEPS, MEDIAN TIME TO CONVERT and BIGGEST DROP tiles.
  • Forms - Analyzes how visitors interact with and complete web forms for the same tenant, container, time range and base segment used on the Funnels tab.
    • Not captured in this screenshot; reuses the shared context bar filters from the Funnels tab.

Field reference

Field Purpose Format / Validation Required Default
Tenant selector Scopes every funnel and the Saved funnels list to one tenant (customer account); switch it only if your login has access to more than one tenant, since it also reloads the available containers and segments. dropdown No LoadGen B.V.
Container selector Selects which monitored web application's visitor sessions the funnel and the Forms tab are built from; changing it changes which pages, clicks, forms, goals and events are available as step conditions. dropdown No Production Web App
Segment selector (base) Sets the base population every KPI tile and step bar measures against: choosing a narrower segment reports on fewer, more specific sessions, while a broader segment gives more sessions but a less targeted read; the compare-with chips are always measured against this base. dropdown No Real users
NAME Names the funnel you are building; this label appears in Saved funnels and in the editor header once you Save it. text No New funnel
Step condition type Chooses what kind of visitor action this step measures, such as a page view; each step you add defines one more condition a session must meet, in order, to keep converting through the funnel. dropdown No Viewed page
Step operator Defines how the value below must match for a session to satisfy this step; the only operator visible in this funnel is is, which requires an exact match. dropdown No is
Step value The specific target of the condition, for example a page path for a Viewed page step; a session only satisfies this step if its matched activity equals this value. text No /pricing

Controls reference

Refresh

Recomputes the funnel and its KPI tiles using the current tenant, container, time range and segment filters.

When to use: After changing a filter, or to pull fresh data without changing any filter.

Side effects: Read-only: re-fetches and recomputes; does not change a saved funnel's definition.

Quick range buttons (1h, 4h, 8h, 24h, 7d)

Switches the active time window to one of these preset durations ending now.

When to use: For fast comparisons at common windows, such as checking the last 24h right after a release.

Side effects: Read-only: changes which sessions are counted in the funnel and tiles; does not alter saved funnels.

Custom

Lets you set a time window outside the presets.

When to use: To isolate the exact hours around a reported incident or test run.

Side effects: Read-only: changes only the active time window.

New (Saved funnels panel)

Clears the editor and starts a fresh, unsaved funnel named New funnel.

When to use: After saving or reviewing a funnel, to start another without touching the saved one.

Side effects: Mutates only the in-progress draft; does not delete or change any saved funnel.

Delete step (trash icon)

Removes that row's step from the funnel currently open in the editor.

When to use: To drop a stage you no longer want to measure.

Side effects: Mutates only the open draft, renumbering the remaining steps; a saved funnel is unaffected until you Save again.

Compare-with chips (Everyone, Synthetic (LoadGen runs), During a load test, On a slow monitoring window, Identified, Reached a goal, Did not reach a goal, New, Returning, Frustrated, Had a JS error)

Overlays a second segment's conversion on top of the base segment.

When to use: For example, select Synthetic (LoadGen runs) to check whether a load test's traffic follows the same path as real visitors, or Had a JS error to see if script errors block conversion.

Side effects: Read-only: changes only the comparison line shown; the base segment is unchanged.

Save

Writes the open funnel definition: creates a new saved funnel the first time, or updates the selected one on later saves.

When to use: Once the steps represent a funnel you want to reuse or reopen later.

Side effects: Mutating: adds or updates an entry in Saved funnels. Only available to the SessionSightConfig or SessionSightAdmin role.

Use as path

Hands the current funnel's steps to the workload composer as a starting path for a load test scenario.

When to use: After a funnel reveals a real visitor flow you want to replicate as synthetic load.

Side effects: Read-only on this page: it does not alter the funnel or Saved funnels. Only offered to a session permitted to compose workloads.

Delete (funnel)

Deletes the selected saved funnel after you confirm the prompt.

When to use: To retire a funnel you no longer track.

Side effects: Mutating and destructive: asks for confirmation first, then removes it from Saved funnels and opens a fresh draft in its place.

Saved funnel list item

Loads that funnel's steps into the editor and recomputes its tiles and step bars.

When to use: To review or edit an existing saved funnel.

Side effects: Read-only: replaces the editor's contents with the selected funnel's definition.

Retry

When to use: When the Saved funnels panel shows a load failure instead of your list.

Side effects: Read-only: re-attempts the fetch; does not change any funnel.

Verify the result

A successfully saved funnel appears as a row in Saved funnels, labeled with the name you entered and its chain of step labels. Selecting that row reloads the same steps into the editor and recomputes CONVERSION THROUGH ALL STEPS, MEDIAN TIME TO CONVERT and BIGGEST DROP for the current time range and segment. If Save produced no new row, confirm you are still viewing the same tenant and container you saved under, since Saved funnels is scoped to the context bar's current selection. If the tiles still read 0% and n/a after saving, check that real sessions matching Step 1's condition exist in the selected time range and segment.

Troubleshooting

  • Symptom: Save does not appear, and a message says your role can build and compute funnels but not save them. Fix: Ask a SessionSight administrator to save the funnel; Save requires the SessionSightConfig or SessionSightAdmin role.
  • Symptom: Selecting a saved funnel shows "This funnel no longer exists." Fix: Rebuild the steps you need and select Save again; the original was deleted, and saving creates it fresh.
  • Symptom: The context bar reports "This container was not found, or your account cannot see it." Fix: Switch to a container you have access to, or ask an administrator to grant access in Configuration: SessionSight: SessionSight.
  • Symptom: CONVERSION THROUGH ALL STEPS stays at 0% with "0 of 0 sessions." Fix: Widen the time range with Custom, or confirm Step 1's condition, such as a page path, actually matches traffic in the selected container and segment.
  • Symptom: Saved funnels shows a Retry button instead of your list. Fix: Select Retry; this means the list failed to load, not that you have zero saved funnels.
  • Symptom: The STEPS panel shows no second line after choosing a compare-with chip. Fix: Select Refresh after changing the chip, and confirm the comparison segment, such as Synthetic (LoadGen runs), has sessions in the current time range.
Was this article helpful?
0 out of 0 found this helpful