Visitor journeys
Pages, sequence and time, stitched to a contact at conversion.
Journeys & Pulse
AEO gets you into the answer. This shows you who arrived.
See the pages a contact read before they asked for a quote, which AI assistants referred them, and how warm they are now, delivered to your CRM with a note your reps will actually read.
Journeys · contact timelineSample data
Pulse82Hot · follow up
- Day 1Arrived from an AI assistant referral
- Day 1Read HX Series spec page, 4 min
- Day 3Returned, compared two models
- Day 3Submitted quote form → delivered to CRM
History attached only after the person submitted a form.
Short answer
Journeys & Pulse records visitor journeys and Forge-owned form funnels, attaches history to a contact only when they submit, scores engagement with Pulse, and delivers it to The Viking Stack CRM, which stays the system of record for contacts.
Forms that deliver
Forge-owned forms through an idempotent, retrying queue. No submission is silently lost.
AI referral tracking
See which assistants and answer engines sent visitors.
Pulse scoring
Engagement scoring with a next-step note for reps.
WooCommerce checkout stitching
Connect purchase activity to the same journey.
Insight surfaces
People, Pages, Forms and Signals answer what your CRM can't.
Design constraints, not settings
Privacy rules you can't switch off.
- No pre-submit capture: field values are recorded only on submit
- Global Privacy Control is always honored
- Consent resolved first (WP Consent API, GPC, geography, site config)
- IPs hashed, query strings scrubbed to an allowlist
- No anonymous person identification, session replay or heatmaps
- Deletion paths and payload scrubbing after CRM delivery
Ask about Journeys & Pulse
Scripted assistant · demo catalog · not a live AI
Scripted demo · written answers · nothing leaves this page
Questions
Journeys & Pulse.
Does this replace Google Analytics?
No. It answers the questions page-level analytics cannot: which known contact read which pages before asking for a quote, how each form funnel performs, which AI assistants referred visitors, and what a rep should do next. Keep your analytics; Journeys & Pulse adds the per-person and per-form layer.
What does the tracker capture before someone submits a form?
Only funnel events: form viewed, form started, which field names were completed, and abandonment. No keystrokes, no partial values, no email-on-blur. Field values are captured only on submit, and never before. This is a design rule, not a setting.
How is privacy handled?
Consent is resolved before any collection (WP Consent API, then Global Privacy Control, then geography, then site configuration). GPC is always honored and cannot be turned off by the site owner. IP addresses are hashed, query strings are scrubbed to an allowlist, and form payloads are scrubbed after delivery to your CRM. Person-level anonymous identification, session replay, and heatmaps are deliberately not built.
Where does contact data live?
Your The Viking Stack CRM stays the sole system of record for contacts. Forge holds an identity map keyed by contact id and a disposable display cache with a time-to-live. Nothing in Forge treats cached names or emails as authoritative.
Will a quote request ever get lost?
Every delivery goes through an idempotent queue with retries and backoff. Stuck deliveries raise alerts, a fallback sales notification runs on a path independent of the CRM connection, and undelivered payloads are exported before they expire. No submission is silently lost.
Does it work with our consent banner?
On WordPress the tracker registers against the WP Consent API, so banners like Complianz govern it without custom glue. UK visitors run under the first-party statistics exemption; EU visitors without consent are not tracked at all.
Next step
See what AI reads before your buyers do.
Start with a free GEO Report on your own storefront, or book a working session and we will walk through your catalog together.