Funnels connect the visitor signals that matter to your business into one readable path. Start with everyone, narrow each stage with a Trigger, and see where visitors continue, drop away, or reach the outcome you care about.
A Funnel does not replace Triggers. It composes them. Each stage is a question about a visitor: did this person arrive from the campaign I care about, show the behavior I expect, carry a label, or reach the next business milestone? Put those questions in order and the result becomes a journey your whole team can understand.
Use page activity when it answers the question, but also combine the other visitor filters and labels your Triggers can identify: acquisition context, device, location, browser, campaign, custom data, or a meaningful product action.
Require exact order when every step is mandatory. Use forward order when visitors may skip an optional stage while still moving from the beginning toward the final outcome.
A stage count is only the beginning. Click a stage to open the visitors behind that label or trigger, then inspect the individual path and context that explains the number.
The example above starts with Everyone, narrows to Add to cart, and ends at Payment Page. The width of the path makes the loss visible; the text beside each stage gives the count and the rate needed to decide what to improve.
Use Everyone when the journey begins with all visitors, or choose an entry Trigger when only a specific source, audience, or behavior should enter the measurement.
Chain the existing labels and Triggers in the order that represents progress: an intent signal, an important action, a qualification step, or any other milestone your site can record.
Compare each stage with the one before it and with the original entries. A large drop-off identifies where to investigate; a completed journey shows the outcome reached by the chain.
Click a stage when the aggregate view raises a question. The dashboard opens that specific visitor label so you can connect the funnel result to real sessions and context.
이미 보유한 트래픽을 중심으로 라이브 방문자 맥락, 실용적인 설치 경로, 행동 도구가 필요할 때 사용하세요.
Hitsteps는 웹사이트 플랫폼, 브라우저 변화, 분석 환경 변화, 스토어 워크플로 전반에서 계속 발전해 왔습니다.
WordPress, Shopify, Wix, Google Tag Manager, HTML, CMS, 커머스, 브라우저, 데스크톱 설치 경로가 하나의 허브에 문서화되어 있습니다.
추적 설치 후에도 라이브 대시보드, 방문자 프로필, 히트맵, 채팅, 트리거, 가동 시간, 보고서, 알림이 연결되어 있습니다.
The Funnel builder shows a recent sample so you can validate the chain before saving it. Once saved, the history fill runs in the background and the dashboard reports its progress. New Triggers begin recording only after they are created, while the saved Funnel can backfill eligible recent history without freezing the site for other users.
Everyone → Add to cart → Payment Page → Thank you. Add a source or campaign condition when you want to compare the journey for a particular acquisition channel.
Visitors from a campaign → product engagement → qualified label → conversion. The path can focus on visitor attributes and labels even when the pages are shared with other audiences.
A visitor arrives from a referral, returns on another device, reaches a key action, and becomes a qualified lead. Use the conditions your tracking setup can distinguish at each step.
Enable desktop or email notifications when a Funnel reaches its final step, so a completed journey can become a follow-up task instead of another number waiting in a report.
No. A Funnel is made from your existing Triggers, so each step can use whatever visitor condition that Trigger supports. Page views are one useful example, but source, campaign, device, location, browser, custom labels, and other visitor signals can also be part of a journey.
Exact order requires a visitor to reach every stage in sequence. Forward order keeps the sequence but allows a visitor to skip a stage, which is useful when a step is optional or not recorded for every visitor.
Yes. Funnel stages are actionable. Select a stage to open the visitor list for that specific label or trigger result, so the aggregate number can lead directly to an investigation.
A Trigger starts recording after it is created. A newly saved Funnel can show the available recent sample immediately, while its saved history is filled in the background without blocking the dashboard.
Create the Triggers first, chain them into a Funnel, validate the recent sample, and let the background history process fill in the saved view.