Flowpeek in your store.
Works with any store. See the ready integrations, the data and how setup works.
WooCommerceOrders, events and visit context.See the integration
ShopifyConnect store data with Flowpeek analytics.See the integration
ShoperCheck what the store connection covers.See the integration
IdoSellSee the data and how the integration works.See the integration
PrestaShopFrom integration to reports.See the integrationLooking for marketing tool connections? See the full integrations catalog.
Set up in 48 hours. We configure everything for you.
Devices and browsers
See which devices and browsers customers use to visit your store and how often they buy. Pick the setup where you should test checkout first.
30 days for PLN 0 · first payment after the trial · cancel anytime. We set it up for you within 48 hours.
With this module
Devices in practice
A phone and a computer can deliver a completely different experience. Line up orders, revenue and conversion to pick the device and browser to examine closely.
What you'll see and what to check next
The device table shows orders, revenue, average order value and CR — the share of visitors who bought. You see both the number of purchases and how often visitors buy.
Next step
Pick a device with a significant share of sales and go from the product page to payment on it.
The second table shows the same set of metrics by browser. It makes it easier to narrow down what to check.
Next step
Check forms, product variants and available payment methods in the selected browser. Write down the specific obstacle.
Revenue and average order value help you assess a difference that the number of purchases alone doesn't explain.
Next step
Compare the offer and how visits unfold. Determine whether the difference comes from the type of products bought, the traffic or the purchase process.
The report points to where to look. The user journey shows the recorded steps that help you prepare a task for your store team.
The sales report uses verified orders available in tracking. A conversion difference helps you form a hypothesis; on its own, it doesn't prove a store bug.
From report to decision
See the devices, browsers and operating systems your visitors use. That tells you what to test your store on first.
Compare confirmed orders, revenue, average order value and CR — the share of visitors who bought. Lots of visits from a device doesn't have to mean lots of purchases.
Conversion charts let you spot when results change for either group. That's your starting point for checking a release, a campaign or an offer change from that period.
Combine traffic volume with weaker results. Test the purchase flow in the setup that matters for your store first, instead of spending the same time on every configuration.
Pick a device or browser. Review the purchase steps in the funnel and sample visit histories. Point out where the problem may be and how to reproduce it.
The order breakdown covers sales reliably linked to a Flowpeek visit. An order without such a link doesn't get a guessed browser or device.
from report to test
When mobile accounts for a large share of traffic, its weaker results deserve attention. The report points to the group to analyze; the funnel helps narrow down the step, and a test on the device lets you check how easy the form, cart and payment are to use.
before and after a change
After changing your store's design or checkout form, compare the daily share of buyers on phones and computers. If results changed on the day of the release, test a purchase on those devices. Also account for new campaigns, promotions and the number of visitors.
clear interpretation
Mobile customers may come from different campaigns and be at a different stage of buying. Treat the difference as a reason to look closer, not as an automatic technical diagnosis.
Getting started
Go from setup to a specific question. During the trial, you'll see how this module helps in your day-to-day work.
01
Choose a period and check the devices, browsers and systems used in your store.
02
Compare the size of each group with its orders, CR and average order value. Check the mobile and desktop trend as well.
03
Reproduce a purchase in the chosen setup. After the release, come back to the report and assess the change together with traffic volume and type.
In your daily work
E-commerce manager
Check the number of visitors and the share of buyers on phones. Review the purchase steps in the report, then go through the checkout form on a phone yourself.
What you gain
You pick a specific step to test instead of rebuilding the whole mobile version.
Development team
Check the conversion trend after the change and the browser table, then reproduce a purchase in the most important setups.
What you gain
You have an organized post-release checklist and data to decide the order of testing.
UX / CRO specialist
Check which devices, browsers and systems most of your visitors use.
What you gain
You match test environments to your store's real traffic.
Your plan for the first 30 days
Build a store testing list based on real devices and purchase results.
We configure Flowpeek within 48 hours and check which links between visits and orders are available.
Check traffic volume, conversion and orders. Pick one device or browser to analyze.
Prepare a purchase scenario and discuss your observations in the consultation during the first month.
You know which setups to test your store in and have a concrete hypothesis to check.
Questions and answers
Yes. You see their share of traffic. Sales tables show devices and browsers separately, and daily conversion charts compare mobile with desktop.
CR shows what share of visitors in a given group and period made a purchase. It counts buyers with a confirmed link between the order and the visit, each person only once. It doesn't divide all orders by page views. When comparing reports, check whether they calculate this metric the same way.
Not necessarily. Traffic sources, visit intent, the offer and group size also matter. The report helps you decide what to test; you find the cause in the funnel, the journeys and a hands-on purchase test.
The report needs a reliable link between the order and a visit. Importing an order from the store alone doesn't provide browser history.
Pick a setup that matters for your store, go through the purchase flow and write down one improvement hypothesis. In a consultation during the first month, we'll help you set the result against the funnel and decide how to test that hypothesis.
From description to practice
Basics · 11 min read
Calculate your store's conversion rate, check the denominator and see what public averages really say. Set your own baseline split by device and source.
Read the guidePractice · 7 min read
Pick a purchase step, compare devices and check user journeys. Plan a specific checkout test instead of guessing why conversion is lower.
Read the guide30 days on your own data
Start a 30-day trial. We set up and configure Flowpeek in 48 hours. You get a ready-to-use dashboard and a consultation in the first month.
30 days for PLN 0 · first payment after the trial · cancel anytime
See pricing after the trialReports that complement each other
The conversion funnel shows each step of the purchase: product, cart, checkout form and purchase. See how many visits reach each one and choose where to start making improvements.
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.
See how often customers add products to the cart, click key elements and submit forms — how many people do it and how that changes day by day.
