Session Tracking Settings

Manage Sessions sets up the pages wheremore tracks and configures how visitor sessions are captured — giving the foundation for session replay analysis and CRO insights.

Quick start

1. Select a domain from the dropdown

2. Enter a URL and click Add URL — or click Import from Sitemap to bulk-add pages

3. Click the camera icon on any row to capture screenshots (desktop, mobile, tablet)

4. Open Settings to choose a tracking mode and configure exclusions

5. Review captured pages using the HTML and Screenshot view toggles

Understanding the display

The main table lists every tracked URL for the selected domain. Each row includes a view toggle, capture controls, tier chips (if configured), and a delete option.

View toggle

• HTML (default): shows the live HTML snapshot of the page

• Screenshot: shows desktop, mobile, and tablet captures — available after capture is triggered

Action buttons

• Camera icon: triggers screenshot capture for that page

• Refresh icon: re-fetches the HTML snapshot (and re-captures any tagged tiers)

• Trash icon: removes the URL from tracking permanently

Tracking badge

The tracking badge in the domain header shows whether the domain uses Cookieless or Cookie tracking mode.

Tier chips

If tier credentials are configured under Settings — Gated content, each URL row shows one chip per tier. Chips indicate whether that page has been captured for that tier: solid navy (success), red (failure), grey (pending), or dashed with a + (not yet tagged).

Click a dashed chip to capture the page for that tier. Click any captured chip to remove the tag and delete that tier's captured content. See the Gated Content guide for full setup and usage.

What should I do next?

Situation	Action
No URLs in the table	Add pages manually or import from sitemap
Screenshot button is greyed out	Click the camera icon to capture first
Screenshot toggle is unavailable	No screenshots captured yet — click the camera icon
HTML looks outdated	Click the refresh icon to re-fetch
Settings badge shows wrong mode	Open Settings and change the tracking mode
Need to track many pages quickly	Use Import from Sitemap
Want to see what logged-in users see	Configure tier credentials under Settings — Gated content, then tag individual URLs (see Gated Content guide)

Adding pages

Adding a URL manually

Enter a URL in the input field and click Add URL. The URL must belong to the selected domain. wheremore captures an HTML snapshot immediately after the URL is added.

Importing from a sitemap

Click Import from Sitemap to open the import modal. Select a sitemap, then choose pages by folder or individually.

Structured sitemaps show a folder view first. Select one or more folders to include all pages within them, or switch to the All Pages view to pick individual URLs. Flat sitemaps go straight to the URL list.

Click Import & Capture to begin. wheremore adds the selected pages and queues screenshot capture automatically.

Screenshots

Each tracked page supports three screenshot types: desktop, mobile, and tablet. Screenshots are not captured automatically — they require a manual trigger or an import.

To capture screenshots for a page already in the list, click the camera icon on that row. Once captured, the Screenshot toggle activates and the view switches between HTML and Screenshot modes.

Re-capturing screenshots replaces all three existing captures. If capture fails for some devices, successful captures are saved and existing screenshots for failed devices are preserved.

Settings

Open the settings panel using the Settings button in the domain header. All settings apply to the selected domain only. There is no save button — every addition and removal takes effect immediately.

Tracking mode

• Cookieless (default): session-based tracking without persistent cookies; privacy-first; suitable for most sites

• Cookie: tracks returning visitors using a persistent cookie; switching modes deactivates any active conversion paths to prevent mixing data from the two methods

Tracking status

The toggle enables or disables data collection for the domain. Disabling tracking stops new session data from being recorded. Existing tracked pages and captured content are not affected.

Exclude authenticated users

Platform presets stop data collection for logged-in users. Detection runs on page load — no data is collected for matched visitors.

• WordPress: detects the body.logged-in class used by standard themes

Tap a card to activate or deactivate a preset. WooCommerce sites use the WordPress preset.

Exclude URL paths

Visitors who load a matching path are excluded from tracking entirely.

• Paths must start with /

• Use /* to match all sub-paths (e.g. /admin/* excludes everything under /admin/)

• Up to 20 paths per domain

• Removing a path only affects sessions processed after the change — sessions already excluded from historical data remain excluded

Advanced — custom exclusion rules

Custom rules exclude users by cookie or JavaScript variable for platforms without a built-in preset.

• Cookie name: exact match against a cookie name

• Cookie prefix: matches any cookie whose name starts with the specified prefix

• JS variable: checks for a truthy value at window.*

Up to 10 rules in total across platform presets and custom rules. Multiple rules work as OR logic — a visitor is excluded if any single rule matches.

wheremore automatically recognises all major consent management platforms — including Cookiebot, OneTrust, and CookieYes — and checks their consent signals before collecting any data. No configuration is needed for these platforms.

Register a custom consent cookie only if this site uses a consent system that is not a standard platform. wheremore checks the registered cookie before collecting any data, exactly as it does for recognised platforms.

• Enter the cookie name and the accepted values (comma-separated)

• Matching is case-insensitive

• Up to 10 consent cookies per domain

Gated content

Capture pages as logged-in users — up to 5 tiers per domain, each with its own credentials. After configuring a tier, tag individual URLs to capture them as that user type. Passwords are encrypted at rest.

See the Gated Content guide for full setup and usage. Each tier capture counts as one page scrape.

Danger zone — delete all pages

Permanently deletes all tracked pages for the domain, including HTML snapshots and screenshots. Tracking is disabled on the domain after deletion. This action cannot be undone.

Troubleshooting

URL rejected on entry

The URL must belong to the selected domain. Check the domain dropdown matches the URL, and confirm there are no typos.

Screenshot capture failed

Some pages block automated rendering. Confirm the URL loads in a browser, then retry. If the problem persists, the page is inaccessible to the capture service.

Switching tracking modes shows a warning

The domain has active conversion paths. Switching deactivates them to prevent mixing session data from different tracking methods. Confirm to proceed, or cancel to keep the current mode.

Import from Sitemap shows no sitemaps

No sitemaps are configured for this domain. Add a sitemap in Manage Sitemaps first.

HTML snapshot looks incomplete

wheremore uses JavaScript-enabled browser capture, but pages with heavy client-side rendering may not capture fully. Switch to Screenshot mode as an alternative.

Domains appear here once added to wheremore. Check the correct workspace is selected.

FAQ

How often are HTML snapshots updated?

Snapshots update when the refresh icon is clicked. wheremore does not update them automatically.

Can pages from more than one domain be tracked?

Yes. Use the domain dropdown to switch between domains. Settings and tracked pages are stored separately for each domain.

What happens to existing data if a URL is deleted?

Deleting a URL removes it from the tracked list along with its captured HTML and screenshots. Session replay data already recorded for that URL is not affected.

Cookieless tracking uses session-based logic without persistent identifiers. Cookie tracking stores a cookie to recognise returning visitors across sessions. Both modes capture the same page-level data.

Why is the Screenshot toggle disabled?

Screenshots must be captured before the toggle activates. Click the camera icon to trigger capture for that page.

Does disabling tracking delete existing data?

No. Disabling tracking pauses data collection but does not delete any tracked pages or captures.

Do tier captures (Gated Content) count as scrapes?

Yes. Each tier capture counts as one page scrape. A page tagged with three tiers consumes three scrapes per capture run, in addition to the public capture. See the Gated Content guide for detail.