All dashboards
Neo4j · Path Analytics
Landing → conversion journeys
Sign in for live data
Window 🤖 Filter on
A
user@neo4j.com
Path Analytics is under active construction WIP · expect caveats
Treat the numbers as directional, not definitive. GA4's Data API can't give us true ordered page sequences (that needs BigQuery), so the Sankey approximates paths via session-level co-occurrence. The "By section" toggle, the "Hide direct conversions" filter, and the Channel layer all help separate signal from tautology — but multi-page chains beyond a single mid-page hop remain a real architectural limit. Use this dashboard for direction-of-travel insights, not exact attribution.

Path Analytics

How visitors actually move from a landing page to a key event — form submissions, sign-ups, contact and demo requests. Approximates GA4's Path Exploration via session-level aggregates, with a sankey for the dominant flows and a table for the long tail.

Setup check: Looking for conversion events in GA4…
Overview · last 30 days
Sessions
—
Total inbound
Engaged sessions
—
Engagement rate
Key events
—
Sum of active conversion events
Converting sessions
—
Sessions w/ any key event
Conversion rate
—
Converting / total sessions
Top entry to convert
—
Highest converting landing
Conversion events tracked
Active:
Conversion funnel · session-level
Stages from session → key event
Sessions move left-to-right. The drop between any two steps is your biggest opportunity. Width is proportional to session count.
Session funnel
Path flow · landing → mid-page → key event
Sankey: top 3-hop journeys ending in a key event
Ribbon thickness = converting sessions on that landing → mid-page → event route. Use the controls below to suppress trivial paths and focus on what's actually informative.
3 hops
Granularity
Focus event
Discovery paths · indirect conversions only
Which content actually drives conversions?
Sessions where the landing page is not a conversion surface — so the visitor discovered the conversion path through your content rather than walking straight in. These are the routes worth investing in. Auto-grouped by section so /blog/post-a and /blog/post-b roll up.
—
Landing section Mid section Key event Conv. sessions Share
Top paths to conversion · full long tail
Landing → mid → event sequences, ranked by converting sessions
Mid-page is the most-visited intermediate page in the same session that ended in the listed event. Read top-down to see which entry routes convert and via which surfaces.
Top 50
Path (landing → mid → event) Conv. sessions Share
Top landing pages by conversion rate
Landings with at least 100 sessions. Sort by CVR to find efficient entry points; sort by conversions to find sheer volume.
Top 20
Landing page Sessions Conversions CVR
Last page before conversion
The page where the key event fired. Heuristic: it's the "decision-moment" page.
Top 15
Last page Events Share
Where converters come from
Conversion sessions by acquisition channel
Default GA4 channel grouping. Compare against the same channel split in Marketing Analytics to see which channels punch above their weight.
All channels
LLM & AI-driven discovery · coming soon
LLM citations as a discovery channel
Once Gauge is wired up, we'll treat ChatGPT / Claude / Perplexity / Gemini / Grok citations as a first-class acquisition channel — visible alongside organic search and paid in the channel split above, and stitched into the Sankey as another front-of-funnel column.
Pending Gauge
How this works · methodology & caveats

The fundamental limit

GA4's Data API does not expose its native Path Exploration. There is no endpoint that returns ordered page sequences per session. To approximate paths we run three layered session-level aggregates and stitch them in the browser. Results are directionally correct for the most-trafficked routes, but the long tail is necessarily lossy.

What "conversion" means here

On load the dashboard asks GA4 for every event marked as a key event in your property settings (Admin → Events → "Mark as key event"). Any event with a non-zero keyEvents metric in the last 90 days becomes a candidate, and the toggle chips above let you turn individual events on and off.

If no key events are configured in GA4 — which is unusual but possible — the dashboard falls back to a heuristic list (form_submit, sign_up, contact, demo_request, generate_lead, lead_form_submission) intersected with whatever's actually firing. The setup banner at top flags this case so you know to fix the GA4 configuration.

How the funnel is built

Five session-level stages:

  • Sessions — every inbound session in the window
  • Engaged sessions — GA4's engagedSessions metric (10s+ engaged, 2+ pageviews, or any key event)
  • Multi-page sessions — sessions with screenPageViews ≥ 2
  • Reached a conversion surface — sessions that viewed a path matching /contact, /signup, /demo, /aura, or /talk-to-sales (heuristic; tweak in code)
  • Fired a key event — sessions where any active conversion event count > 0

How the Sankey is built

Three queries, stitched:

  • Hop 1 → 2: dims=[landingPagePlusQueryString, pagePath] with eventName IN (active events). Gives "for converting sessions starting at landing X, which mid-pages were visited?"
  • Hop 2 → 3: dims=[pagePath, eventName] with the same event filter. Gives "for converting sessions, the event fired on which page?"
  • Stitching: top-8 landings × top-10 mids per landing × the event firings on those mids, weighted by event count.

The "mid page" is a representative interior page, not a strict sequence position — GA4 doesn't give us ordering via the API. Read it as "pages that frequently co-occur in converting sessions starting here."

Filters applied

This dashboard is a metrics dashboard, so the suite-wide geo block (🌍) and bot filter (🤖) apply. Excluding problem-traffic countries and bot-flavoured sessions tightens conversion attribution. Both filters are in the header.

Loading…