Maximising sessions in Adora

Overview

Guidance for getting the most value from a limited monthly session allotment by focusing capture on the journeys that matter and controlling where the snippet runs.

How Adora counts a session

A session starts when the snippet loads on a page or view where it is installed. A session ends after 30 minutes of inactivity. When a session ends, Adora syncs it and counts it toward your monthly quota.

Plan your capture strategy

Start from outcomes, not coverage. Identify the highest-value, most linear journeys and capture those first. Linear flows concentrate signal and reduce wasted sessions.

Prioritize:

• Sign up and onboarding

• Upgrading subscriptions and payments

• Experiment-heavy funnels with many variants (A/B, multivariate, rollouts)

Ways to control which sessions are captured

Use the levers below to steer sessions toward your priorities. Combine them as needed.

Scope where the snippet loads

Install the snippet only on product areas you care about. Avoid blanket installation across marketing sites, help centers, or low-value admin sections unless those areas are under study.

You can:

• Install on a subset of apps, domains, or sections to hard-gate non-priority traffic

• Expand coverage later and revisit sampling to avoid diluting high-value areas

Target which people load the snippet

Gate snippet load by audience, such as signed-in customers, specific account tiers, beta cohorts, or internal testers.

You can:

• Include only authenticated users or specific plans

• Create cohorts for trials, enterprise accounts, or testers and route them to capture

• Document inclusion logic so downstream analyses understand who is represented

Use sampling and bypass sampling together

Sampling reduces how often the snippet fires for eligible traffic; bypass sampling ensures specific traffic always captures.

You can:

• Define bypass rules for priority cohorts (for example, trialers, enterprise, experiment participants)

• Keep bypass lists focused to avoid starving other areas

Control firing frequency

Throttle how often a new session can start for the same person within a time window to prevent spending quota on rapid, repetitive visits.

You can:

• Cap repeats for sticky internal tools or auto-refreshing dashboards

• Balance caps so you do not miss meaningful revisit behavior

Allow or block by URL scope

Include or exclude by page, path, domain, or subdomain. For single-page applications, consider route-based rules that map to view changes.

You can:

• Allow-list only the paths that belong to priority journeys (for example, /signup, /checkout, /billing)

• Block-list non-priority or noisy paths (for example, /admin, /status, /legal)

• Treat subdomains explicitly so cross-subdomain navigation behaves as intended

Learn more: Access control

Where to focus first

Anchor capture to the steps that change customer value or conversion state.

Focus areas:

• Sign up and onboarding: from account creation through first-value milestones

• Upgrade and billing: price selection, payment entry, confirmation, receipts, and failure states

• Experiments: every variant path and dynamic interstitials (modals, upsells, paywalls) that affect progression

Example allocation patterns

Use these starting points and adjust based on volume and quota.

Low quota, high-stakes funnel

• Install only on /signup, /onboarding/*, and /checkout/*

• Bypass sampling for new visitors and anyone entering checkout

Medium quota, product discovery + monetization

• Install on core product and billing

• Bypass sampling for active trials and users who hit upgrade prompts

• Throttle repeat sessions from the same person within short windows

High quota, experiment-heavy org

• Install across product and key marketing landers feeding priority funnels

• Bypass sampling for experiment participants and churn-risk cohorts

• Allow-list experiment routes and modal surfaces; block low-signal utilities

FAQs

Does a paused user or idle tab keep a session alive? No. If no activity is detected for 30 minutes, the session ends and is synced to Adora.

Do sessions from blocked paths count? No. If the snippet does not load or capture due to your rules, those visits do not start sessions.