Journey guide

Reveal customer journeys.

Turn automatic pageviews and meaningful goal events into aggregated customer paths.

Generic examplesSign in for exact instructionsKnow will replace the domain, site ID, and goal names in every code sample and ChatGPT instruction.

1 Journeys are assembled automatically

The tracker records the current pathname and observes browser history navigation. Know groups repeated routes into aggregate journeys and hides paths followed by fewer than three visitors.

No special journey call

Keep normal routing intact. Adding a custom event named “journey” would not create a journey report.

2 Enrich paths with goal events

Pageviews explain where visitors went. Goal events explain what they successfully did on those pages, making funnels and journey conversion counts more useful.

// Pageviews are automatic. Add goal events only for meaningful actions.
window.know?.("onboarding_step_completed", { step: "profile" });

// There is no separate window.know("journey") call.

Keep routes useful

Prefer stable paths such as /pricing and /checkout/success.
Know stores pathnames without query strings.
Avoid manually firing pageviews; the tracker already handles initial loads and SPA navigation.

3 Verify the journey

Navigate through the intended route in production without forcing full page reloads.
Confirm one pageview is sent for each changed pathname.
Complete the meaningful action and confirm its goal event appears once.
After enough real traffic follows the same path, open Journey and inspect the aggregated route.

Give this task to ChatGPT

Work in the codebase for https://YOUR_WEBSITE_DOMAIN.

Know configuration:
- Registered domain: YOUR_WEBSITE_DOMAIN
- Site ID: YOUR_SITE_ID
- Tracker: https://www.know.am/t.js
- Event collector: https://collect.know.am/e
- Configured goal events: none configured yet

Task: Prepare the application for useful Know customer journeys.

Requirements:
1. Confirm the Know tracker is installed once in the global layout and observes client-side route changes.
2. Review the important customer path and keep stable, human-readable pathnames without query strings.
3. Add goal events for meaningful successful actions that cannot be represented by a page visit. Reuse onboarding_step_completed where appropriate.
4. Do not manually send pageviews and do not invent a journey() call; Know builds aggregated journeys from the existing pageviews and goals.
5. Verify the intended path in production and report the expected ordered route and event sequence.

Privacy and implementation rules:
- Inspect the project and find the real successful application state before editing.
- Keep the existing Know tracker installed exactly once; do not add another analytics package.
- Never send names, e-mail addresses, credentials, authorization data, payment-card data, health data, cookies, raw IP addresses, query strings, or request bodies.
- Preserve the current design, authentication, redirects, middleware, and server/client boundaries.
- Run the existing tests and production build, then report changed files and exact verification steps.

Make the code changes now.

1 Journeys are assembled automatically

The tracker records the current pathname and observes browser history navigation. Know groups repeated routes into aggregate journeys and hides paths followed by fewer than three visitors.

No special journey call

Keep normal routing intact. Adding a custom event named “journey” would not create a journey report.

2 Enrich paths with goal events

Pageviews explain where visitors went. Goal events explain what they successfully did on those pages, making funnels and journey conversion counts more useful.

// Pageviews are automatic. Add goal events only for meaningful actions.
window.know?.("onboarding_step_completed", { step: "profile" });

// There is no separate window.know("journey") call.

Keep routes useful

Prefer stable paths such as /pricing and /checkout/success.
Know stores pathnames without query strings.
Avoid manually firing pageviews; the tracker already handles initial loads and SPA navigation.

3 Verify the journey

Navigate through the intended route in production without forcing full page reloads.

Confirm one pageview is sent for each changed pathname.

Complete the meaningful action and confirm its goal event appears once.

After enough real traffic follows the same path, open Journey and inspect the aggregated route.

Work in the codebase for https://YOUR_WEBSITE_DOMAIN. Know configuration: - Registered domain: YOUR_WEBSITE_DOMAIN - Site ID: YOUR_SITE_ID - Tracker: https://www.know.am/t.js - Event collector: https://collect.know.am/e - Configured goal events: none configured yet Task: Prepare the application for useful Know customer journeys. Requirements: 1. Confirm the Know tracker is installed once in the global layout and observes client-side route changes. 2. Review the important customer path and keep stable, human-readable pathnames without query strings. 3. Add goal events for meaningful successful actions that cannot be represented by a page visit. Reuse onboarding_step_completed where appropriate. 4. Do not manually send pageviews and do not invent a journey() call; Know builds aggregated journeys from the existing pageviews and goals. 5. Verify the intended path in production and report the expected ordered route and event sequence. Privacy and implementation rules: - Inspect the project and find the real successful application state before editing. - Keep the existing Know tracker installed exactly once; do not add another analytics package. - Never send names, e-mail addresses, credentials, authorization data, payment-card data, health data, cookies, raw IP addresses, query strings, or request bodies. - Preserve the current design, authentication, redirects, middleware, and server/client boundaries. - Run the existing tests and production build, then report changed files and exact verification steps. Make the code changes now.