Sessions
Inspect visits in Behavior Intelligence Sessions: KPIs, segment filters, paginated tables with geo and browser context, timelines, and REST export options.
Session-level analysis
The Sessions page lists individual visits for the selected date range. While Traffic aggregates volume, Sessions lets you audit specific behaviors—long research visits, bounced mobile sessions, or high-value returning users. Each row represents one session ID with summary metadata; open a row to see the full event timeline on Journeys.
Sessions respect privacy settings: IPs are never shown raw unless your configuration explicitly allows diagnostic modes. Geo displays country-level data when the MaxMind database is active.
Session KPIs
Summary cards above the table include average session duration, pages per session, goal completions, and bounce-related counts for the filtered set. These KPIs update when you apply a segment—useful for comparing mobile vs desktop session quality side by side by toggling saved segments.
Applying segment filters
Use the global segment control or build a new segment inline via Segments page. Filters commonly applied here:
- Device type equals mobile
- Channel equals organic search
- Landing page contains a campaign slug
- Country equals a target market
Combine filters with AND logic. Saved segments appear in the toolbar for one-click reuse on Reports and Traffic.
Saved views vs segments
A saved view stores date range + segment + comparison together. A saved segment stores only audience filters. Use views for recurring weekly reports; use segments when the date range changes.
Sessions table columns
- Started — Session start timestamp in site timezone.
- Duration — Time from first to last event.
- Pages — Count of page_enter events.
- Country / browser — Parsed at ingest.
- Entry / exit page — First and last URL in the session.
- Goals — Whether configured conversions fired.
Pagination handles large ranges; narrow the date window or segment before exporting very large lists.
Opening session detail
Click a session to open Journeys with ?session= query showing chronological events: page views, scroll milestones, clicks with component labels, and custom events. This timeline is the ground truth when debugging funnel drop-offs or support tickets about "what the user clicked."
Exporting session data
Authorized users can export via REST report endpoints when building external BI workflows. For ad hoc CSV, use Report Builder with session dimensions or Details → Advanced export panel. Exports omit direct identifiers per privacy mode.
Privacy-aware session review
Session lists intentionally omit raw IPs and form contents. Support teams should use timelines to see sequence of pages and labeled clicks, not typed user input. When logged-in tracking is on, user ID links appear for authorized roles only—never export IDs to unsecured sheets.
Performance at scale
High-traffic sites should narrow date ranges before loading Sessions. Use segments to split workloads—review US mobile and EU desktop separately rather than loading all rows. REST export supports automated pipelines when CSV downloads timeout in browser.
Additional best practices
Behavior Intelligence works best when tracking coverage, funnel definitions, and team review rituals stay aligned. Revisit this guide after major site changes—new theme, consent plugin, or checkout provider—and confirm Realtime, Data Quality, and Tracking Plan still agree.
Share direct help links from the in-app help panel so teammates read the same canonical definitions. Press Ctrl+K in the help center to jump between related guides quickly.
- Align date ranges before comparing metrics across pages.
- Document segment names when sharing screenshots.
- Verify fixes in Realtime before closing Growth Plan items.
- Keep UTM conventions consistent for Marketing and Traffic.
- Schedule AI analysis after enough post-change data accumulates.
Working with the global toolbar
Every major Behavior Intelligence report page shares a global toolbar controlling date range, comparison mode, saved views, and active segments. Understanding this toolbar prevents the most common reporting mistake: discussing metrics that look contradictory because two pages use different ranges or filters.
Date ranges support presets (last 7, 28, 90 days) and custom intervals. Comparison mirrors the prior period of equal length. When comparison is off, KPI deltas hide—do not assume zero change. Saved views capture all toolbar state; teach teammates to check the view name in the header before screenshotting for leadership.
Connecting insights to action
Analytics value appears when insights change behavior. Behavior Intelligence routes findings through Growth Plan, Anomalies, and AI Intelligence into prioritized work. A metric without an owner becomes wallpaper. Assign DRI (directly responsible individual) per Growth Plan card and set verification dates.
Cross-link investigations: Traffic anomaly → Sessions sample → Journeys path → Tracking Plan coverage → Funnel step fix. This sequence resolves most conversion mysteries without external tools.
Data freshness expectations
Raw events ingest in near real time on Realtime. Daily aggregates power most dashboard KPIs and typically finalize after processor cron completes overnight in site timezone. Intraday numbers on Traffic are directional, not audit-final. Export via Report Builder after period close for finance-adjacent reporting.
Security and access control
Report data stays inside WordPress authenticated admin. REST endpoints require configured capabilities. Do not expose API keys or disable capability checks for convenience. View-only roles should not access Settings, Tracking Plan writes, or AI job triggers unless policy explicitly allows.
Module updates and compatibility
After Imaginit Core or Behavior Intelligence updates, revisit Getting Started verification steps: Realtime test, Data Quality health, one saved report run. Release notes may add event types or metrics—refresh Report Builder definitions if preview validation fails. Theme changes always trigger Tracking Plan re-crawl before trusting click metrics.