Visitor journeys
Pageviews, sessions, scroll depth, engaged time, SPA route changes, and an attribution snapshot per session: referrer, classified source, and UTM parameters.
Forge module · Journeys & Pulse
See the whole path from first visit to quote request.
Journeys & Pulse captures form submissions and visitor journeys on your site, stitches anonymous browsing to a known contact the moment they convert, scores engagement, and pushes the signal into your The Viking Stack CRM, which stays the system of record. Your reps open a contact and see every page, session, source, and form behind the request.
Installed by the same ForgeAEO WordPress plugin that publishes your AEO artifacts. A plain script-tag install covers Shopify and standard websites.
AEO gets you into the answer. This shows you who arrived.
Once a catalog is readable to AI buyers, the next question is what happened after the click. Page-level analytics cannot tell a rep which contact read the datasheet, the MOQ policy, and the RFQ page before asking for a quote. Journeys & Pulse can.
Forms that deliver
Forge-owned forms with typed fields, multi-step flows, inline, modal, and popup variants, honeypot and rate limits, and a self-reported "How did you hear about us?" field.
Identity stitching at conversion
On submit or checkout the visitor binds to the resulting CRM contact. Many visitor ids can map to one person, and history is never rewritten, only attributed.
Pulse scoring
Rules-based, per-site configurable scores across Engagement, Intent, Recency, and Fit, rolled into one Pulse score and a Cold, Warm, or Hot level on the contact.
AI referral tracking
Three visibly separate layers: confirmed referrals from AI assistant hostnames and UTMs, self-reported answers, and a labelled estimate that is never merged into the confirmed count.
WooCommerce checkout stitching
Paid orders are captured server-side, deduplicated, and stitched to the journey that preceded them, so a first purchase lands on the contact with its full path.
Inside your CRM
Two fields, a deep link, and a note your reps will actually read.
Journeys & Pulse never floods the CRM. Exactly two values cross over: the Pulse score and the Pulse level, written only when a threshold is crossed or the score moves meaningfully, never per pageview. Journey summaries arrive as batched notes at conversion time, and a signed, expiring insights link opens the full person view in Forge.
Discrete signal tags fire as they happen, so your existing workflows can trigger on "read the pricing page twice" without anyone building a report.
Pulse score and Cold, Warm, or Hot level as CRM custom fields.
First source and last source captured on the contact.
Batched journey notes on the contact timeline at conversion.
Signed, expiring per-contact insight link, refreshed on every sync.
Additive signal tags that trigger your existing automations.
Sales notification email on every quote request from a workflow you control.
Insight surfaces built for the questions your CRM cannot answer.
The module lives in Forge as a set of tabs, each backed by the same event store and rendered in both light and dark themes.
People
The deep-link target: journey timeline, sessions, sources, score history by category, and conversions for one contact.
Visitors
Filter by page and date window. Who visited the datasheet page in the last 14 days is a one-click question here and impossible in a contact search.
Conversion paths
Entry source to page path to conversion, ranked by count and rate.
Pages
Per-page views, engaged time, scroll depth, and assisted conversions.
Forms
View, start, and submit funnel per form and variant, per-field drop-off, and delivery health so a stuck submission is visible before anyone asks.
Signals
Every scoring event and tag as it fired, so you can see why a contact became Hot and tune the rules per site.
Privacy rules that are design constraints, not settings.
Web intelligence for B2B buyers only works if the people being measured can trust it. These behaviors are fixed in the module and cannot be relaxed by configuration.
No pre-submit capture
Funnel events record the form id and field names only. No keystrokes, partial values, or email-on-blur, ever.
Global Privacy Control honored
A GPC signal disables identity stitching and the CRM tracking script. Site owners cannot turn this off, and California visitors see a visible confirmation.
Consent resolved first
WP Consent API, then GPC, then geography, then site configuration. EU visitors without consent are not tracked. UK visitors run under the first-party statistics exemption.
Scrubbed by default
IPs are hashed, query strings are stripped to an allowlist so campaign links never leak emails into the event store, and form payloads are scrubbed after delivery.
No anonymous identification
Person-level identification of anonymous visitors, session replay, and heatmaps are deliberately not built. Company-level enrichment is opt-in per account.
Deletion paths
Delete-by-visitor and delete-by-contact remove every event, session, and identity row for one person.
Installed by the plugin you already run.
On WordPress and WooCommerce the ForgeAEO plugin enqueues the tracker with cache-optimizer exclusions handled, sets the visitor cookie server-side for durability under Safari and Brave, captures paid checkouts, and registers with the WP Consent API. Everything else uses a plain script tag with email re-stitching at the next conversion.
WordPress + WooCommerce: one plugin toggle, same-origin relay, checkout capture.
Shopify and standard websites: script-tag install with the site public token.
Per-site domain allowlist; events from anywhere else are rejected.
Rotatable site token; the plugin pairing secret never reaches a browser.
Shopify app and unified Google connection on the roadmap.
Pairs with Valkyrie Assist.
Form submissions can feed Valkyrie Assist as prospects, and a prospect's detail view shows the journey activity behind it. Research lists and inbound requests end up in one place, and both graduate into the CRM the same way.
Journeys & Pulse questions.
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.
See who is already reading your catalog.
Book a free AI Visibility Audit. We will show what AI answer engines can read on your site today, and how Journeys & Pulse turns the resulting visits into scored, traceable quote requests.