Configuration: SessionSight: SessionSight
Overview
Use this page to configure SessionSight tenants, containers, and tracking rules. A tenant is the top-level grouping in SessionSight for one customer or property; a container is a tracked site or app nested under a tenant, holding its own API key, allowed origins, privacy-masking mode, and retention setting. Goals, funnels, and channel-grouping rules are defined per container to turn raw visitor activity into measurable conversions and attributed traffic.
This page is SessionSight's setup root: a tenant needs nothing upstream, but a container requires a datasource already created under Configuration: Datasources. Once a container has an API key, you embed its tracker code on the monitored site; the sessions it records, plus the goals, funnels, and channel-grouping rules defined here, feed the SessionSight dashboards, funnel, and attribution views elsewhere in the platform.
On this page you create and edit tenants and containers, issue, rotate, or revoke API keys, define goals and funnels, order channel-grouping rules, group tenants together, connect external sources such as GA4, and run scheduling and maintenance operations like analytics rebuilds and data purges.
Key concepts
- tenant - The top-level grouping in SessionSight for one customer or property; every container, key, goal, funnel, and rule belongs to exactly one tenant.
- container - A tracked website or app nested under a tenant, holding its own API key, allowed origins, privacy-masking mode, and retention setting. (related: Configuration: Datasources)
- goal - A specific visitor action, a page view, a custom event, or a scroll depth, that you define as a conversion to measure.
- funnel - An ordered sequence of steps representing a conversion path, used to see where visitors drop off along the way. (related: SessionSight: Funnels)
- channel grouping - The ordered rules, plus a fallback default channel, that classify a session's traffic source into a marketing channel for attribution reporting. (related: SessionSight: Attribution)
When to use it
- Onboarding a new customer or property into SessionSight by creating its tenant and container.
- Issuing, rotating, or revoking the API key a monitored site's tracker snippet uses.
- Defining or adjusting conversion goals and funnels to measure visitor behavior.
- Correcting how traffic sources are grouped into channels for attribution reporting.
- Connecting an external analytics source like GA4 to pull its data into SessionSight.
- Running maintenance operations such as rebuilding analytics or purging expired session data.
Before you begin
- A SessionSight tenant must exist before you can add containers, keys, goals, or funnels; create one on this page's Tenants tab if none exists yet.
- A datasource must already exist under Configuration: Datasources before you can save a new container, since Datasource Name is required.
- To connect an inbound connector, for example GA4, have the external account's Customer ID or Property ID and credentials ready.
- If the page shows a Credentials expiring banner for a token a related integration depends on, reissue it under Configuration: Credential Profiles first.
Common workflows
Onboard a new tenant and container for tracking
Persona: SessionSight admin
- Select the Tenants tab and select Add Tenant.
- Expect: An Add Tenant form opens for entering Tenant ID and Company Name.
- Enter a Tenant ID and Company Name, then save.
- Expect: The new tenant appears as a row in the Tenants table with an Analytics status chip.
- Switch to the Containers tab and select Add Container.
- Expect: An Add Container form opens, scoped to the tenant you just created.
- Fill in Container ID, Name, Datasource Name, and Allowed origins, then save.
- Expect: The new container appears in the Containers list and becomes selectable in the top Container dropdown.
- Switch to the Keys tab and select Generate Key.
- Expect: A new API key is created for the container.
- Select Get Tracker Code.
- Expect: The embeddable tracker snippet for this container is returned.
Verify: The tenant and container both appear in their respective tables, the Keys tab shows an active key for the container, and Get Tracker Code returns a snippet instead of an error.
Define a conversion goal
Persona: SessionSight admin
- Switch to the Goals tab and select Add Goal.
- Expect: An Add Goal form opens for the selected container.
- Choose a Type and fill in its matching fields, Target URL and URL Match Type, or Event Name, or Scroll Depth %, then set Conditions and a Completion Value.
- Expect: The form fields change to match the chosen goal Type.
- Save the goal.
- Expect: The goal appears in the Goals list for the selected container.
- Select Goal Analytics on the new goal.
- Expect: The goal's completion analytics view opens.
Verify: The new goal is listed under the Goals tab for the selected container, and Goal Analytics shows a completion count once matching sessions arrive.
Steps
Step 1
Open the SessionSight configuration page.
Expected result: The page loads with the Tenants tab active, listing the single loadgen-main / LoadGen B.V. tenant with its Analytics status set to Disabled, and a banner reports that the Orders API credential expires in 4 days.
This is the starting point for every other tab on the page, since containers, keys, goals, and funnels are all scoped to a tenant.
- The Tenant and Container dropdowns default to LoadGen B.V. and Production Web App.
- A Credentials expiring banner points to Configuration → Credential Profiles to reissue the token.
Step 2
Select the Goals tab.
Expected result: The Goals tab will open to list the conversion goals defined for the selected container. This capture still shows the Tenants list, though the expiring-credential banner has been dismissed and a Refresh control is now visible.
Goals are what SessionSight measures as conversions, so defining them here is a prerequisite for goal-based reporting.
- A Refresh control is available in the header to reload tenant data.
- The expiring-credential banner is no longer shown.
Step 3
Select the Operations tab.
Expected result: The Operations tab will open to the scheduler, segment, and data-maintenance controls, including rebuild analytics and purge data. This capture still shows the Tenants list, now with its Edit and Delete row actions visible again.
Operations is where you run rebuilds and purges after changing tracking configuration, so you'd open it once setup changes are in place.
-
Edit and Delete icons are available again on the loadgen-main tenant row.
Tabs on this page
-
Tenants - Create, rename, and remove SessionSight tenants, the top-level grouping each container, key, goal, and funnel belongs to.
- Tenant ID, Company Name, and the Analytics status of each tenant.
-
Containers - Create and edit the tracked sites or apps within the selected tenant, including the API key's allowed origins, timezone, retention window, and privacy masking.
- Container ID, Name, Description, Main URL, Datasource Name, Timezone, Status, Max Sessions/Day, Retention (days), Allowed origins, Privacy masking, and URL normalization rules.
-
Keys - Issue, rotate, or revoke the API key a container's tracker snippet uses to send session data, and retrieve the embeddable tracker code.
- One API key per container, managed with Generate Key, Cycle Key, Revoke Key, and Get Tracker Code.
-
Goals - Define visitor actions, page views, custom events, or scroll depth, that count as conversions for the selected container.
- Type, Target URL, URL Match Type, Event Name, Scroll Depth %, Conditions, and Completion Value.
-
Funnels - Define an ordered sequence of steps representing a conversion path, so you can see where visitors drop off.
- Steps, Max Step Delay (min), and per-funnel Conditions.
-
Channel Grouping - Order the rules that classify incoming traffic sources into marketing channels, plus the fallback channel used when none match.
- Ordered rule list with Move up/down and Remove, and Default channel (used when no rule matches).
-
Tenant Groups - Bundle multiple tenants into a named group for combined reporting.
- Name and a Member tenants checklist.
-
Connectors - Connect and schedule pulls from external analytics sources (inbound) and configure outbound data sinks.
- Source, Display name, Customer ID/Property ID, and Pull schedule (cron, optional).
-
Operations - Run scheduled-job settings and one-off maintenance: analytics rollups, tracker sync timing, IP-cache and retention-purge timing, segment definitions, analytics rebuilds, AI insight generation, and manual data purge.
- Analytics Rollup Interval (min), Session Tracker Sync Interval (min), IP Cache Maintenance Time, Retention Purge Time, Segments, Rebuild Analytics, Weekly AI Insights, and Purge Data.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Tenant | Scopes every tab below to one tenant; switch it to work on a different customer's or property's containers, keys, goals, funnels, and rules. | dropdown | No | LoadGen B.V. |
| Container | Scopes the Keys, Goals, Funnels, Channel Grouping, and related tabs to one container within the selected tenant; switch it to configure a different tracked site. | dropdown | No | Production Web App |
| Tenant ID | Unique identifier for the tenant, used to scope its containers and settings. | text | Yes | - |
| Company Name | Display name shown for the tenant in the Tenants table and in the Tenant selector. | text | No | - |
| Container ID | Unique identifier for the container within its tenant. | text | Yes | - |
| Name | Human-readable name for the container; the same label is reused for naming a goal or funnel on their own forms, where it is required. | text | - | - |
| Description | Free-text notes about the container, for your own reference. | text | No | - |
| Main URL | The container's primary site URL. Combined with Allowed origins, saving it can restrict ingest to that site instead of accepting tracker calls from any origin. | URL | No | - |
| Datasource Name * | The analytics datasource, created under Configuration: Datasources, that this container's session data is written to; pick an existing one or create a new one with the + button. | dropdown | Yes | - |
| Timezone | Localizes session timestamps and scheduled report windows for this container. | dropdown | No | - |
| Status | Controls whether the container actively accepts and processes tracker data. | selector | No | - |
| Max Sessions/Day | Caps how many sessions this container records per day. A lower value limits ingestion volume and cost; a higher value lets more traffic through before the cap is hit. | number | No | - |
| Retention (days) | Sets how many days of session data this container keeps before the retention-purge job deletes it; this container-level value is what governs purging. A lower value frees storage sooner; a higher value keeps more history available for analysis. | number | No | - |
| Allowed origins * | Lists the website origins (scheme://host[:port]) permitted to send tracker data under this container's key. A narrower list stops other sites from sending data under your key; at least one origin is required. | list of URLs | Yes | - |
| Privacy masking | Chooses how aggressively personal data in tracked values is redacted before storage. A stricter mode protects visitor privacy but hides more raw detail in session replays and reports; a looser mode keeps more detail but increases exposure risk. | mode selector | No | - |
| Path discovery: URL normalization | Groups different URLs that represent the same logical page, for example two product pages that only differ by an ID, into one path for reporting instead of counting each separately. | section (toggle plus rule list) | No | - |
| Built-in rules (numeric / GUID / date / hash) | Turns on automatic normalization of common variable path segments: numeric IDs, GUIDs, dates, and hashes. Leave it off if you need those exact values visible in path-level reports. | toggle | No | - |
| Type | Chooses what kind of visitor action completes this goal. The fields shown change with the choice: Target URL and URL Match Type for a page-view goal, Event Name for a custom-event goal, or Scroll Depth % for a scroll-tracking goal. | dropdown | No | - |
| Expression (legacy) | An older free-form matching expression for a goal, kept for goals created before structured Conditions existed. Use Conditions for new goals. | text | No | - |
| Value | The comparison value for a condition, what the condition's field is checked against. | text | No | - |
| Target URL | The page URL that marks this goal as completed when Type is a URL-based goal. | text/URL | No | - |
| URL Match Type | Controls how Target URL is matched against the visitor's actual page URL, for example matching the exact page versus any page under that path. | dropdown | No | - |
| Event Name | The name of the custom tracked event that completes this goal when Type is event-based. | text | No | - |
| Scroll Depth % | The percentage of the page a visitor must scroll to complete this goal when Type is scroll-based. A higher percentage makes the goal stricter, since visitors must read further down the page. | number (%) | No | - |
| Conditions | Additional match criteria narrowing which sessions count toward this goal or segment; add more conditions to require all of them to match at once. | list | No | - |
| Completion Value | A numeric value assigned to the goal when it completes, used for conversion-value reporting; set it higher for conversions you consider more valuable. | number | No | - |
| Max Step Delay (min) | The maximum number of minutes allowed between two consecutive funnel steps for the sequence to still count as one completed funnel. A lower value enforces a faster path through the funnel; a higher value tolerates visitors who pause longer between steps. | number (minutes) | No | - |
| Steps | The ordered list of stages that make up this funnel; a visitor's session is measured against each step in order to find where they drop off. | list | No | - |
| Analytics Rollup Interval (min) | How often raw session data is aggregated into the rollup tables dashboards read from. A lower interval gives fresher numbers at the cost of more frequent processing; a higher interval reduces processing load but delays when new sessions show up in reports. | number (minutes) | No | - |
| Session Tracker Sync Interval (min) | How often container and key configuration is synced out to deployed tracker snippets. A lower interval propagates changes, like a new key, to live sites faster; a higher interval reduces sync traffic. | number (minutes) | No | - |
| IP Cache Maintenance Time (HH:mm) | The time of day the IP-to-location lookup cache is refreshed. | time (HH:mm) | No | - |
| Retention Purge Time (HH:mm) | The time of day the retention-purge job runs, deleting session data older than each container's Retention (days) setting. | time (HH:mm) | No | - |
| Default channel (used when no rule matches) | The fallback marketing channel assigned to a session when none of the ordered channel-grouping rules match its traffic source. Set it to the channel you want unmatched traffic reported under instead of left unclassified. | dropdown | No | - |
| Name * | The tenant group's display name. | text | Yes | - |
| Member tenants | Checklist of tenants included in this tenant group; check a tenant to roll its data into this group's combined view. | checklist | No | - |
| Source | The external platform this inbound connector pulls data from, for example Google Analytics 4. Selecting a source determines which identity field appears next. | dropdown | No | - |
| Display name * | The connector's display name shown in the Connectors list. | text | Yes | - |
| Customer ID / Property ID | The external account identifier the connector pulls from; the field is labeled Customer ID or Property ID depending on the selected Source. | text | No | - |
| Pull schedule (cron, optional) | An optional cron expression controlling how often the connector automatically pulls data from the external source. Leave it blank to pull only when you trigger it manually. | cron expression | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| Tenant ID | The tenant's unique identifier, as shown in the Tenants table. | Match this against the Tenant ID you set when creating the tenant; it's also what the top Tenant filter selects. |
| Company Name | The tenant's display name, as shown in the Tenants table. | Use this to recognize the tenant by its business name rather than its ID. |
| Analytics | Shows whether SessionSight analytics processing is turned on for this tenant. | A Disabled chip means this tenant's sessions aren't being processed into analytics yet; enable it through Edit before expecting data on the SessionSight dashboards. |
| Actions | Row-level controls for the tenant. | Use the pencil icon to edit the tenant and the trash icon to delete it. |
Controls reference
Refresh
Reloads the tenant and container data for the current scope from the server.
When to use: After another admin changes tenants or containers, or after dismissing the expiring-credential banner, to confirm the page reflects the latest state.
Side effects: Read-only: re-fetches data, makes no changes.
Add Tenant
Opens a form to create a new tenant.
When to use: Before you can add containers, keys, goals, or funnels for a new customer or property.
Side effects: Mutating: saving the form creates a new tenant row in the Tenants table.
Edit
Opens the selected row's details pre-filled in an editable form; used on Tenants, Containers, Goals, Funnels, and Segments rows.
When to use: To change an existing tenant, container, goal, funnel, or segment without recreating it.
Side effects: Mutating once saved: updates the existing record.
Delete
Opens a confirmation prompt, then removes the selected row: tenant, container, goal, funnel, or segment.
When to use: To permanently remove an entity you no longer need.
Side effects: Mutating and hard to reverse: deleting a tenant or container also removes the records scoped under it.
Cancel
Closes the open add/edit form without saving.
When to use: When you want to discard in-progress changes.
Side effects: Read-only: no data is changed.
Add Container
Opens a form to create a new container under the selected tenant.
When to use: To register a new site or app to track under an existing tenant.
Side effects: Mutating: saving creates a new container, which then becomes selectable in the Container dropdown.
Add rule
Adds a blank URL-normalization rule row to the container form being edited.
When to use: When the built-in numeric/GUID/date/hash normalization isn't enough to group variants of the same page path.
Side effects: Changes only the in-progress form; takes effect once the container is saved.
Remove
Deletes a single row from a list you're editing: a URL-normalization rule, a goal or segment condition, or a funnel step.
When to use: To take out one rule, condition, or step before saving the form.
Side effects: Changes only the in-progress form; takes effect once saved.
Dismiss
Hides the Credentials expiring banner.
When to use: After you've noted or already reissued the referenced credential.
Side effects: Read-only for this session: does not reissue or extend the credential itself.
Go to Tenants / Go to Containers
Jumps to the Tenants or Containers tab from an empty-state prompt.
When to use: When a tab has nothing to show because no tenant or container is selected yet.
Side effects: Read-only: only changes which tab is active.
Generate Key
Creates a new API key for the selected container.
When to use: The first time you set up tracking for a container that has no key yet.
Side effects: Mutating: fails if the container already has a key; use Cycle Key instead in that case.
Cycle Key
Replaces the container's existing API key with a newly generated one.
When to use: To rotate a key periodically or after a suspected leak, without changing the container's other settings.
Side effects: Mutating: the old key stops working immediately; any tracker snippet still using it will fail to send data until updated.
Revoke Key
Invalidates the container's current API key.
When to use: To stop a compromised or retired key from being accepted, without immediately issuing a replacement.
Side effects: Mutating: trackers using the revoked key are no longer accepted; the container has no key until you Generate Key again.
Get Tracker Code
Retrieves the embeddable tracking snippet for the selected container's current key.
When to use: When you need to embed or re-embed the tracker on the monitored site.
Side effects: Read-only: returns a snippet; fails if the container has no valid key.
Manage
Opens detailed management for a specific key row.
When to use: To inspect or act on an individual key in the key inventory.
Side effects: Read-only until you take an action inside it; availability depends on the key's state.
Add Goal
Opens a form to define a new conversion goal for the selected container.
When to use: When you want to measure a specific visitor action as a conversion.
Side effects: Mutating: saving creates a new goal.
Goal Analytics
Opens the analytics view showing how often the selected goal has completed.
When to use: To check whether a goal is actually matching visitor sessions.
Side effects: Read-only.
+ Add Condition
Adds a new match condition row to the goal or segment being edited.
When to use: To narrow a goal or segment to sessions matching more than one criterion.
Side effects: Changes only the in-progress form.
Add Funnel
Opens a form to define a new ordered sequence of steps.
When to use: To track where visitors drop off along a multi-step process.
Side effects: Mutating: saving creates a new funnel.
Funnel Analytics
Opens the analytics view showing completion and drop-off per step.
When to use: To see which step of the funnel loses the most visitors.
Side effects: Read-only.
+ Add Step
Adds a new step row to the funnel being edited.
When to use: To extend the funnel with another stage in the visitor's path.
Side effects: Changes only the in-progress form.
Add Segment
Opens a form to define a new visitor segment.
When to use: To group sessions by shared conditions for reporting.
Side effects: Mutating: saving creates a new segment.
Move up / Move down
Reorders a channel-grouping rule one position up or down in the evaluation list.
When to use: Channel-grouping rules are evaluated in order, so move a rule up to give it priority over the rules below it.
Side effects: Mutating: changes which rule matches first for ambiguous traffic.
Identity (Phase 1) New
Opens the early-access visitor-identity feature, marked Phase 1.
When to use: To try the newer identity-resolution capability while it's in its first phase.
Side effects: Behavior beyond opening the feature isn't shown in this capture.
Verify the result
After you create a tenant, it appears as a new row in the Tenants table with its Tenant ID, Company Name, and an Analytics status chip. After you add a container under that tenant and generate a key, the container becomes selectable in the Container dropdown, and Get Tracker Code returns a snippet instead of the no-snippet message. If a new tenant or container doesn't appear after saving, confirm you're still scoped to the correct Tenant and Container in the top filters, since each tab only shows data for the selected pair.
Troubleshooting
- Symptom: Saving a new tenant or container does nothing visible. Fix: Check for a missing required field: Tenant ID on the Tenants form, or Container ID, Datasource Name, and Allowed origins on the Containers form; the page names the missing field.
- Symptom: Generate Key reports the container already has a key. Fix: Use Cycle Key instead; a container can only hold one active key at a time.
- Symptom: Get Tracker Code returns no snippet. Fix: Open the Keys tab and generate or cycle a key for the container first; a revoked or missing key blocks the snippet.
- Symptom: Sessions stop arriving right after Revoke Key. Fix: This is expected: the old key is no longer accepted. Generate a new key and update the tracker snippet embedded on the site.
- Symptom: A Credentials expiring banner won't go away. Fix: Reissue the named token under Configuration: Credential Profiles; Dismiss only hides the banner, it doesn't renew the credential.
- Symptom: Clicking a different tab, for example Goals or Operations, still shows the Tenants list. Fix: Refresh the page and reselect the tab.
Related articles
- Prerequisite: Configuration: Datasources - a container requires an existing datasource before it can be saved
- See also: Configuration: Credential Profiles - reissue credentials the expiring-token banner refers to
- Next step: SessionSight: Dashboard - view session data once a tenant and container start reporting
- Next step: SessionSight: Funnels - see performance for the funnels defined here
- Next step: SessionSight: Attribution - see channel attribution driven by the channel-grouping rules here
- See also: SessionSight: GA4 - view data pulled in by a GA4 inbound connector