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.
Event analytics
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.
30 days for PLN 0 · first payment after the trial · cancel anytime. We set it up for you within 48 hours.
With this module
Event analytics in practice
An event is a recorded action in your store. Choose its category, type or label and check how often it occurs. Set the number of actions against the number of people and changes in activity over time.
What you'll see and what to check next
Category and action filters plus label or address search let you narrow the report down to the behavior you're interested in.
Next step
Start with one interaction that matters for your store. Keep the same filters when you come back to the report after a change.
The report counts actions, people and visits (sessions) separately. One person can perform the same action many times during one or more visits.
Next step
Check whether a rise in activity comes with more users or with the action being repeated more often.
The chart shows events and users day by day. It makes it easier to notice a rise, a drop or a gap in recorded activity.
Next step
Match the date of the change with a store release or campaign launch. Also check that tracking still works correctly.
Once you find an interesting event, see what users did before and after it. It's easier to decide which part of the visit is worth improving.
The report covers actions sent by the configured tracking. The value of Purchase events, i.e. recorded purchases, doesn't mean revenue after returns and cancellations here. You'll find that figure in the conversion report.
From report to decision
See actions recorded by on-site tracking and the store connection. The report covers supported product actions and any other interactions you've set up tracking for.
Choose a category and action type, or search for its label or page address (URL). See only the actions you want to assess.
Set the number of actions against the number of people and sessions, i.e. visits. Ten clicks from one person is a different situation from one click each by ten people.
The chart puts events next to users over time. See when activity grows, drops or stops being recorded.
Rankings help you find frequent interactions and labels that need a closer look. Go from the big picture to a narrower question.
After adding a new event, perform a test action and check that it arrives with the expected category and label. Then watch how customers use it.
one interaction, one specific question
A new store element is worth judging by behavior, not just page views. If the interaction is correctly configured as an event, pick its action or label and check how many people use it and how that develops over time.
reach vs repetition
One person can perform the same action many times. Set the number of events against the number of users and sessions before treating growth as greater interest. Check unusual patterns against sample visits and the tracking configuration.
tracking check
After a release, perform the selected actions and check their names in the report. A sudden drop or spike in events can mean a change in behavior or in configuration. The report helps you find the moment to look into, but doesn't settle the cause on its own.
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
Decide what you want to measure: e.g. a recorded add-to-cart or another configured interaction.
02
Choose dates, category and action. If needed, search for a label or page address.
03
Set events against users and the trend. Go back to journeys or the funnel to see how the visit continued.
In your daily work
E-commerce manager
Select the recorded product events for the relevant addresses and check their count, users and trend.
What you gain
You see whether interaction with the offer changes, not just the number of page visits.
E-commerce analyst
Compare user and session counters, narrow down the category, then check repeated actions.
What you gain
You have a specific scope for verifying behavior or the tracking configuration.
Implementation team
Perform it as a test and find it by action, label or page address.
What you gain
You confirm the event is received before the team starts drawing conclusions from the report.
Your plan for the first 30 days
Follow one important store interaction from event receipt to report interpretation.
As part of the 48-hour setup, we check which actions are available in your store.
Confirm the chosen action is received, then check its real scale and trend.
In the consultation during the first month, connect the result with journeys or the funnel and agree on the next step.
You can find a specific interaction, tell its frequency apart from its reach and use the result in your work on the store.
Questions and answers
The report shows the events actually sent by the tracker and integrations. Non-standard interactions need to be configured. During setup, we agree which actions are available and how to check them.
The same person can perform an action several times during one or more visits. That's why the report counts actions, people and visits (sessions) separately. Look at them together to tell more interested people apart from an action being repeated more often.
You can search for a URL in the report and combine it with the category and action filters. The search also covers event labels, so check that your phrase narrows the result accurately.
No. A configured submission-attempt event describes an attempted action, not confirmation that the form was accepted, an identity or marketing consent. This tracking doesn't read what's typed into the fields.
It shows the scale and distribution of recorded actions. To investigate the cause, combine it with journeys, the funnel and a page test. A rise or drop in events alone doesn't explain customer intent.
From description to practice
Basics · 7 min read
Gather your store details, check the first visit and order, agree on the data scope. A simple sign-off checklist — no self-installation needed.
Read the guidePractice · 7 min read
Choose the page, device and map type. Separate clicks from attention, check scrolling and plan one change whose result you can measure.
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
Compare the pages visitors land on and see what they do next. Choose a landing page or product page worth improving based on the data collected.
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 current visits, the pages being viewed and where customers came to your store from. Open the details for a specific person and see what they're doing at this moment.
