Funnel guide

Build conversion funnels.

Instrument funnel steps with pageviews and goal events, then assemble the report in Know.

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

1 Funnels use existing data

A funnel is an ordered report built from automatic pageviews and configured goal events. You instrument the meaningful actions in code, then choose 2–6 steps and a conversion window in Know.

No special funnel call

Do not add window.know("funnel"). It would create an ordinary custom event named “funnel,” not a funnel report.

2 Prepare the steps

Use page paths for navigation milestones and goal events for successful product actions. A later step counts only when the same anonymous visitor completed earlier steps in order.

// Each funnel event is still a normal Know goal event.
window.know?.("signup_completed");
window.know?.("checkout_completed", { plan: "pro" });

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

Example signup funnel

Page visit: /
Page visit: /pricing
Goal: signup_completed
Goal: checkout_completed

3 Build and verify

Confirm every goal step has appeared in Goal and has been promoted to a configured goal.
Open the funnel builder and name the business flow.
Add the ordered page and goal steps, then choose 24 hours, 7 days, or 30 days.
Save the funnel and test the full sequence once in production.

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: Instrument the application for a Know conversion funnel.

Requirements:
1. Map the intended funnel to 2–6 ordered steps. Use stable pathname steps for page visits and custom goal events for completed actions.
2. Reuse these configured goal events where they match: signup_completed, checkout_completed.
3. Add missing window.know?.("event_name") calls only after each underlying action succeeds.
4. Do not invent a funnel(), journey(), or pageview() API. The installed tracker records pageviews automatically; the funnel itself is assembled in the Know dashboard.
5. Report the exact ordered steps I should choose in the funnel builder after the code changes.

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 Funnels use existing data

A funnel is an ordered report built from automatic pageviews and configured goal events. You instrument the meaningful actions in code, then choose 2–6 steps and a conversion window in Know.

No special funnel call

Do not add window.know("funnel"). It would create an ordinary custom event named “funnel,” not a funnel report.

2 Prepare the steps

Use page paths for navigation milestones and goal events for successful product actions. A later step counts only when the same anonymous visitor completed earlier steps in order.

// Each funnel event is still a normal Know goal event.
window.know?.("signup_completed");
window.know?.("checkout_completed", { plan: "pro" });

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

Example signup funnel

Page visit: /
Page visit: /pricing
Goal: signup_completed
Goal: checkout_completed

3 Build and verify

Confirm every goal step has appeared in Goal and has been promoted to a configured goal.

Open the funnel builder and name the business flow.

Add the ordered page and goal steps, then choose 24 hours, 7 days, or 30 days.

Save the funnel and test the full sequence once in production.

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: Instrument the application for a Know conversion funnel. Requirements: 1. Map the intended funnel to 2–6 ordered steps. Use stable pathname steps for page visits and custom goal events for completed actions. 2. Reuse these configured goal events where they match: signup_completed, checkout_completed. 3. Add missing window.know?.("event_name") calls only after each underlying action succeeds. 4. Do not invent a funnel(), journey(), or pageview() API. The installed tracker records pageviews automatically; the funnel itself is assembled in the Know dashboard. 5. Report the exact ordered steps I should choose in the funnel builder after the code changes. 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.