See what leads up to a purchase. And what stops a customer.
Open a visit's history and follow the path from the first page to the cart or order. See where the visitor came from, which products they viewed and what they did, step by step.
30 days for PLN 0 · first payment after the trial · cancel anytime. We set it up for you within 48 hours.
User journeysFlowpeek
Path to an order
Today · 10:42
10:42
Visit from Google Ads
Campaign · fall collection
10:43
Product viewed
Product A
10:45
Added to cart
1 product · PLN 249
10:48
Order
Confirmed by the integration
Page views, interactions and entry sources line up in a single timeline.
From report to decision
See more. Choose your next step.
Follow a visit step by step
Compare the paths of buyers and everyone else
Pinpoint the moment that needs fixing
01
A clear visit history
Visited pages and recorded actions are laid out in order. You can see what happened from the moment someone entered the store.
02
Products next to the visit history
In the visitor card, switch between the overview, products, sessions (that is, visits) and orders. Check which offers they kept coming back to and how they found the store.
03
Product, cart, order
See the shopping events recorded one after another. When the integration links a visit to an order, you'll find it in the same history.
04
A starting point for improvements
Find recurring drop-off points in the journeys and pick a page or purchase step to examine more closely.
01
value in everyday work
Fewer fixes based on guesswork.
Every change to the store takes up your team's time. Journeys help you prepare a narrower, better-described task: you point to the moment the visit broke off, show examples and agree on what to check before rolling it out.
A concrete example for your web designer or developer
Separating an ad problem from a site problem
A hypothesis you can verify in the funnel
02
from entry to decision
Read a visit like a story, not a pile of separate events.
A customer may look at several products, go back to a category and only later open the cart. The timeline lets you see the order of those steps and the point at which the recorded visit ends.
Page views and events on a timeline
Separate sessions you can expand
Entry source and device context
03
campaigns in the context of the store
See what happens after someone clicks an ad.
A popular link doesn't necessarily lead to interest in your offer. Review visits from a campaign and see whether visitors land on the right products, move on to the cart and reach the next step.
The page where the visit started
Products and next steps after entry
The linked order, when available
04
from observation to improvement
Find a pattern worth checking at a larger scale.
A single story suggests a question. Several similar journeys help you choose an area to check in the funnel before you spend time changing the store.
Comparing visits with and without a purchase
A starting point for page analysis
A concrete hypothesis to test
Getting started
Start with your own store.
Go from setup to a specific question. During the trial, you'll see how this module helps in your day-to-day work.
01
We set up tracking
We launch tracking on your site, connect the store and check a test visit. You start with a ready-to-use dashboard.
02
Open a specific visit
Choose a visitor and expand a session. Follow the pages, events and any available links to an order.
03
Compare several journeys
Put visits with and without a purchase side by side. Treat a recurring pattern as a hint for a test.
You'll see the history collected by Flowpeek and linked through available identifiers. Installing the tracker or importing orders does not recreate visits from before the setup.
Is this a recording of the customer's screen?
It's a chronological record of page views and events, not a video of the session. The tracker does not record what people type into forms. Session recordings with AI analysis are in the works (beta testing).
How is a journey different from a funnel?
A funnel shows how many recorded visits reach each step of the purchase. A journey shows how one specific visit unfolded. Start by finding the step where many visits end, then look at examples.
Will I see which campaign a visit came from?
Yes, if the link contains a recognizable campaign or click tag, or if the browser passes on the page the visit came from. Flowpeek shows the information that's available; it doesn't guess a missing source.
Is a single journey enough to decide on rebuilding the store?
It's good material for spotting a problem, but check its scale across more visits and in summary reports. Then choose the change and how you'll measure its effect.
We already track conversions. Why do we need individual journeys?
A conversion shows the outcome, while a journey lets you look inside the visit. Use it when you need to explain a step flagged by the funnel or prepare an example of a problem for your team.
Do I have to go through every visit?
No. Start with a question and a selected group of examples, e.g. visits that end at the cart. Then check the pattern from the journeys in a summary report. It's analysis of a specific problem, not an obligation to watch all your traffic.
How can I test this module in my own store?
During the trial, review a few journeys with and without a purchase. In the consultation during your first month, we'll help you read them in the context of your store.