SessionSight: Privacy

Overview

Use this page to mask personal-data elements on a tracked site before SessionSight records sessions. Privacy masking is the mechanism SessionSight uses to keep names, account numbers, addresses, avatars and other personal data out of recorded sessions: you identify an element by CSS selector, a pattern that matches one or more elements on a page, and choose whether SessionSight blurs its text or hides it completely in every recording made afterward.

This tab is part of the shared SessionSight configuration page, scoped to the tenant and container you pick at the top. The container must already exist, with its tracking snippet installed and verified, before there is a live site to pick elements from. Rules you add here apply to every future recording for that container, and the masked elements then show up correctly blurred or hidden when you review sessions afterward.

On this page you open a live page of the container's site, click the elements that expose personal data, and set each one to Blur text or Hide completely, or add selectors directly without opening the page at all. The Anonymized elements count tracks how many rules are active against a 100-rule limit per container.

Key concepts

• Tenant - A company or organization boundary in SessionSight that owns one or more containers. (related: Configuration: SessionSight: SessionSight)
• Container - The specific site or app being tracked, identified by its SessionSight snippet and main URL. (related: SessionSight: Install and verify)
• CSS selector - A pattern, such as .account-name, that identifies one or more elements on a page so SessionSight can find and mask them.
• Masking action - The treatment applied to a matched element in recordings: Blur text keeps its shape but makes the text unreadable, Hide completely removes it from the recording. (related: SessionSight: Replay)
• Masking mode - A container-wide setting, configured on Behavior settings, that always masks every input field regardless of the selector rules you add on Privacy. (related: SessionSight: Behavior settings)

When to use it

• Before a new container starts recording sessions, to mask the fields that show personal data.
• When a page or component on the tracked site adds a new personal-data element, such as a profile avatar or account number, that recordings would otherwise capture in the clear.
• When auditing how many masking rules are active for a container using the Anonymized elements count.
• When deciding whether an element should stay visible in shape (Blur text) or disappear entirely (Hide completely) from recordings.

Before you begin

• A tenant (company) exists, created on the Tenants tab of Configuration: SessionSight: SessionSight.
• A container for the site you want to mask exists under that tenant, created on the Containers tab of Configuration: SessionSight: SessionSight.
• The SessionSight tracking snippet is installed and verified on the container's site, confirmed on SessionSight: Install and verify, so Page address can actually load a live page.
• You know which page of the site shows the personal-data elements you want to mask, for example an account page, a checkout page, or a profile page.

Common workflows

Mask a personal-data element with the visual picker

Persona: SessionSight administrator

1. Enter the site page's URL in Page address and select Open here or Open in a new tab.
   • Expect: The page loads in the preview panel or a new tab without being tracked; the link stays usable for one hour.
2. On the loaded page, click the element that shows personal data, such as a name, account number, address or avatar.
   • Expect: A choice to mask the element appears; pick Blur text to keep its shape visible with unreadable text, or Hide completely to remove it from recordings.
3. Confirm the masking action for the element.
   • Expect: The Anonymized elements count on the right increases by one and the new rule is listed as active.

Verify: The Anonymized elements count shows more than 0 of 100, and within about 5 minutes new recordings of the site no longer display that element's real content.

Add a masking rule by CSS selector without the picker

Persona: SessionSight administrator

1. Type a selector such as .account-name into Add a CSS selector.
   • Expect: The typed selector appears in the field, ready to submit.
2. Choose Blur text or Hide completely in Masking action, then select Add.
   • Expect: The rule is saved, the Anonymized elements count increases, and the field clears for the next selector.

Verify: The new selector is counted in Anonymized elements (N of 100); the rule reaches the live site within about 5 minutes and every subsequent recording applies it.

Steps

Step 1

Open the Privacy tab for the selected tenant and container.

Expected result: The page loads the element picker on the left, with Page address defaulted to the container's main site, and the Anonymized elements panel on the right showing 0 of 100 and the message No elements anonymized yet.

This is the tab where you define which elements SessionSight must mask before it records any session.

• Tenant and Container scope everything below to LoadGen B.V. and Production Web App.
• Page address defaults to the container's main site URL.
• Anonymized elements reads 0 of 100 until you add a rule.

Tabs on this page

• Tenants - Lists the companies (tenants) in this SessionSight account; add, edit or delete a tenant here before managing its containers.
  • Tenant ID, Company Name.
• Containers - Lists the tracked sites or apps (containers) under the selected tenant; create, edit or delete a container and link its datasource here.
  • Container ID, Name, Main URL, Datasource Name.
• Keys - Manages the API key that authenticates the tracking snippet for the selected container: generate, cycle or revoke it.
  • Key status; Generate Key, Cycle Key, Revoke Key actions.
• Install - Shows the tracking snippet and verification status for the selected container, confirming the site is sending data.
  • Snippet and verification status.
• Behavior settings - Sets container-wide recording behavior, including the masking mode that always masks every input field regardless of the selector rules set on Privacy.
  • Masking mode and related recording options.
• Privacy - Lets you pick elements on the live site by CSS selector and choose Blur text or Hide completely so recordings never capture their personal data.
  • Page address, Add a CSS selector, Masking action, Anonymized elements.
• Goals - Defines conversion goals that SessionSight evaluates against recorded sessions, matched by target URL, event name or scroll depth.
  • Name, Target URL, URL Match Type, Event Name, Scroll Depth %, Conditions, Completion Value.
• Funnels - Defines ordered step sequences to measure where visitors drop off, with a maximum delay allowed between steps.
  • Name, Steps, Max Step Delay (min).
• Channel Grouping - Defines ordered rules that classify traffic sources into channels, plus the default channel used when no rule matches.
  • Rule order (move up/down), Default channel.
• Tenant Groups - Groups several tenants together under one name for shared reporting or access.
  • Name, Member tenants.
• Connectors - Configures inbound connectors, such as Google Analytics 4, that pull external data into SessionSight on a schedule.
  • Display name, Source, Pull schedule (cron, optional).
• Outbound Sinks - Configures destinations that SessionSight pushes data out to.
  • Sink name and destination settings.
• GA4 - Connects a Google Analytics 4 property or customer ID as a data source for SessionSight.
  • Property ID or Customer ID, Display name.
• Scheduler - Sets the timing for background maintenance jobs: analytics rollups, session-tracker sync, IP-cache maintenance and retention purge.
  • Analytics Rollup Interval (min), Session Tracker Sync Interval (min), IP Cache Maintenance Time (HH:mm), Retention Purge Time (HH:mm).
• Segments - Defines reusable visitor segments by condition, used to filter analytics and reports.
  • Name, Conditions.
• Operations - Runs maintenance actions for the container: rebuilding analytics, generating the weekly AI insights digest, and purging retained data.
  • Rebuild Analytics, Weekly AI Insights, Purge Data actions.

Field reference

Column reference

Controls reference

Refresh

Reloads the tenant, container and Anonymized elements data for the current selection.

When to use: Use after adding rules elsewhere or when the counts on screen look out of date.

Side effects: Read-only; does not change any configuration.

Open here

Loads the page at Page address inside the embedded preview panel so you can click elements on it directly.

When to use: Use when you want to stay on this configuration page while picking elements.

Side effects: Read-only on its own; opens a live, untracked view of the page for up to one hour. Clicking an element inside the loaded page then adds a masking rule.

Open in a new tab

Opens Page address in a separate browser tab instead of the embedded panel.

When to use: Use when the page needs more screen space or does not render correctly inside the embedded panel.

Side effects: Read-only on its own; same untracked, one-hour picking window as Open here.

Add

Saves the typed CSS selector with the chosen Masking action as a new masking rule for this container.

When to use: Use after typing a selector you want to mask directly, without using the visual picker.

Side effects: Mutating: increases the Anonymized elements count; the rule starts applying to the live site within about 5 minutes. Existing recordings made before the rule are not changed.

Verify the result

The Anonymized elements count on the right shows more than 0 of 100 once you have added at least one rule, and the empty-state message No elements anonymized yet. is replaced by the list of active rules. Open a session recorded after the change and confirm the targeted element appears blurred or fully hidden rather than showing real data. If the element still shows personal data, check that about 5 minutes have passed since the rule was added and that the CSS selector actually matches that element on the page. Recordings made before the rule was added keep showing the element blurred in the player, but their originally stored data is not altered.

Troubleshooting

• Symptom: The Add button does not seem to save anything. Fix: Confirm you typed a value in Add a CSS selector first; an empty field has nothing to submit.
• Symptom: Opening Page address does not appear to track the page while you pick elements. Fix: This is expected: picking is explicitly untracked, and the link works for only one hour, so reopen it with Open here or Open in a new tab if it has expired.
• Symptom: A password or payment field looks masked even though you never added a selector for it. Fix: Nothing to do: password, hidden and payment-card fields are always masked, along with every input covered by the container's masking mode on Behavior settings.
• Symptom: An element you just masked still shows real data in a brand-new recording. Fix: Wait for the rule to propagate, about 5 minutes, before recording again, and recheck that the CSS selector matches that exact element.
• Symptom: The Anonymized elements count is already at 100 of 100. Fix: Remove an existing selector rule for this container before adding a new one; 100 active rules is the limit per container.

Related articles

• Prerequisite: Configuration: SessionSight: SessionSight - create the tenant and container this Privacy tab is scoped to
• Prerequisite: SessionSight: Install and verify - the container needs the tracking snippet live on a page before you can pick elements to mask
• See also: SessionSight: Behavior settings - sets the container-wide masking mode that always masks every input regardless of selector rules
• Next step: SessionSight: Replay - masked elements appear blurred or hidden in recorded session playback