User Journeys
Analyze user paths and session timelines in Behavior Intelligence: top paths, drop-off analysis, recent sessions, and per-session event timelines for debugging.
Path analysis overview
User Journeys reveals how visitors move through your site in sequence. Unlike funnel definitions you configure manually, path analysis discovers actual routes from observed page_enter events. It answers: After landing on /pricing, do users visit /demo or /contact? Which three-page sequences precede conversions?
Paths require sessions with at least two page views. Single-page bounces appear in Traffic and Content but not in top paths lists.
Top paths table
The top paths panel ranks sequences such as Home → Blog → Contact by session count. Each row shows frequency and optional conversion correlation when goals exist. Click a path to highlight contributing sessions in the recent list below.
Long paths truncate with ellipsis after a configurable depth to keep charts readable. Rare paths with high conversion value may still appear in AI Intelligence recommendations even if volume is low.
Path analysis and drop-off
Path analysis goes deeper: for a chosen starting page, see the next-page distribution and where users exit entirely. Drop-off percentages between steps inform UX priorities—if 60% leave after /cart but before /checkout, investigate payment trust signals or page errors.
Compare path drop-off with Funnels when you have defined processes; discovered paths may include detours your funnel model ignores.
Filtering by landing page
From Traffic, open Journeys with a landing page filter to isolate SEO or campaign entry behavior. This is the standard workflow for "what do Google visitors do after this post?"
Recent sessions list
Recent sessions shows the latest visits matching current filters. Each entry links to session detail. Use this during QA after deploying navigation changes—you should see new paths emerge within hours on active sites.
Session detail timeline
Session detail renders every event chronologically with timestamps, component names for clicks, scroll depth markers, and custom event payloads (allowlisted keys only). Support and product teams use this view to settle disputes about user actions without invasive recording.
Practical journey workflows
- Identify top organic landing page on Traffic.
- Filter Journeys from that URL.
- Note dominant next steps and exit points.
- Add missing CTAs or tracking targets on high-exit pages.
- Verify path shift in Journeys after deploy using a 7-day before/after comparison.
Advanced path questions
Do paths include query strings? Paths normalize URLs per module rules—confirm whether campaign query params create duplicate path nodes in your configuration. Consistent UTM hygiene simplifies reading.
Cross-domain journeys: External domains appear as exit unless subdomains are configured as internal. Checkout on separate domains may truncate paths—supplement with funnel definitions.
Collaboration with content teams
Share screenshot exports of top paths in content planning meetings. Writers see which articles actually lead to product pages versus dead-end informational reads. Update internal links when paths show unexpected detours through legacy URLs.
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.