flowpeekresources / guides / Analytics
Alerts and e-mail reports: set a working rhythm with your Flowpeek data
You'll set up a useful alert and a recurring report, and plan how your team responds.
Short answer
The key answer
An alert reacts to a condition on a metric, while an e-mail report arrives on a schedule. You'll find both in Settings, on the Notifications tab. Start with one rule, check that the message is delivered and choose the person who will analyze the signal.
- The difference between an alert threshold and a schedule
- The actual metric, frequency and report section options
- Checking delivery and agreeing on the team's response
1. Check the recipient and delivery.
Open Settings → Notifications. Alerts and reports are sent by Flowpeek, and the mail server is managed by the Flowpeek team. You don't need to connect your own server. The recipient address comes from the user's details; check it in the user edit screen before you build your first rule.
In the delivery section, use “Send a test e-mail to my address”. Confirm receipt even if the delivery status shows as active. If the message doesn't arrive, check your spam folder and the address, then report the problem. The mail test confirms the delivery channel but doesn't yet check the logic of the selected alert.
2. Choose one metric and a clear condition.
In Threshold alerts you choose a metric, a condition and a threshold. The options are: conversion, daily revenue, daily visitors, bounce rate, abandoned carts, average order value, active sessions and daily sessions. Conditions include greater than, less than and their or-equal variants. The rule description is optional, but it helps the team recognize its purpose.
Set the threshold based on your own traffic. “Conversion below 2%” is an example configuration, not a universal problem line. Alert metrics have their own ranges: some cover the day, some the last 24 hours, active sessions the last 30 minutes. Don't assume the alert copies whatever period you selected earlier on the dashboard.
3. Set the interval and what happens after an alert.
The “Frequency” field lets you choose an interval of 1 hour, 6 hours, 24 hours or a week. It limits repeat notifications for a given rule; it isn't the time a report is sent. If the condition is still met once the interval has passed, the alert can fire again. Save the rule with the “Add rule” button.
Next to the rule, agree on a simple procedure: who opens which report and when they escalate a problem. A low-conversion alert should lead to checking the scale of traffic, the data and the purchase steps. Don't change the budget automatically just because a message arrived. No alert doesn't confirm that all data is complete either.
4. Add a report to your regular results review.
In the “AI newsletters” section, choose “Add”. This part of the dashboard means a data report for the Flowpeek user, not a campaign for the store's customers. Give it a name, choose the data period and the delivery type: daily, weekly or monthly. Set the time and, for the relevant option, the day of the week or month.
Monthly delivery lets you choose a day from 1 to 28. Delivery frequency and data period are separate settings. For example, a Monday message can cover the last 7 days. Check both fields instead of assuming a weekly report automatically uses the calendar week. The screenshot shows the configuration, not confirmation that the message was delivered.
5. Choose the sections the recipient needs.
A report can include a traffic summary, conversions and revenue, a product report, top products, traffic channels, a device breakdown and page results. Choose the set for your role. Whoever handles the offer needs products, and whoever oversees the purchase process also needs devices and conversion. A shorter, useful report is easier to read regularly.
After saving the schedule, you can use “Send now” and check the message you receive. Look at the period, the selected sections and how amounts are presented. The AI commentary helps name observations, but go back to the source report before making a decision. Mixed currencies and a missing complete value shouldn't be read as a simple sum or as zero.
6. After a week, assess how useful the notifications are.
Check how many messages led to a specific action. If an alert regularly describes the store's normal fluctuation, rethink the threshold or interval. If the report doesn't make it to your team meeting, adjust the schedule. Don't add more rules just because they're available: too many signals make it easier to miss important information.
Keep a note about any threshold change and its reason. Turning rules and schedules on and off lets you adjust your working rhythm without deleting the whole configuration. Agree on a backup for the person responsible for responding. A notification is only useful when everyone knows what to do after it.
Common mistakes
Alert frequency as a report schedule
The rule interval limits repeated signals. A recurring report has its own day, time and data period.
All metrics at once
Start with one rule with an agreed response. Add more only when you know who needs them.
For your next review
Checklist
- The user's address is correct and I've received the test e-mail.
- I understand the metric, its range and the condition.
- I've set the interval between alerts.
- The schedule has the right data period and sections.
- Every message has a recipient responsible for the next step.
Now your store
Set up one alert and one weekly review
- 1
Choose a condition based on your own results and write down why.
- 2
Add a report with three sections useful to your team.
- 3
After a week, note the actions the messages led to.
From report to decision
Sample configuration for the exercise
The settings are illustrative. They don't mean the account shown sent such messages.
- Alert
- Conversion below 2%, 6-hour interval
- Report
- Monday 08:00, last 7 days
- Response
- The store manager checks traffic and the funnel
You're assessing how useful the notification is for the team. Receiving an e-mail alone doesn't explain why the result changed.
Questions and answers
Do I need my own mail server?
No. Flowpeek handles delivery. Check the user's address and run a delivery test.
Does a monthly report have to cover the previous month?
Don't assume it does. The delivery type and the data period are chosen separately; check both settings before saving.
Are AI newsletters for sending promotions to store customers?
In this section you configure data reports for the Flowpeek user. Marketing communication to customers runs through a separately connected platform.
From knowledge to report
Open the right module.
Alerts and reports
Choose which store results should trigger an alert and schedule e-mail reports. You have 8 metrics to work with. You set the conditions, the frequency and what goes into each report.
Conversion funnel
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.
Product analytics
Set interest in your product range against carts and order data. Find products worth giving more visibility to, and ones whose offer is worth improving.
Read the next guide.
All guidesAnalytics / 7 min
How to read the Flowpeek dashboard and pick your first topic to analyze
Learn the difference between a visitor, a page view and an order. Read each result against the period, your own goals and the detailed reports.
Conversion / 7 min
Conversion funnel: how to find the problem with mobile purchases
Pick a purchase step, compare devices and check user journeys. Plan a specific checkout test instead of guessing why conversion is lower.
AI / 10 min
How to ask Flowask about sales, marketing and products
Use questions that match what Flowask can do. Check the sources, periods and AI limitations, and turn the answer into a concrete next step.
Free · 30 minutes · online
GA4, your store and your ads show different numbers? We'll check it with you.
We compare one month of sales across your tools and point out three fixes to your measurement. No strings attached. What we check
30 days on your own data
Link the signal to a specific report.
For your first alert, prepare a short checklist: range, scale, funnel or products. A shared way of responding makes the team's work easier.
- No fixed-term contract
- We set everything up for you in 48 h
- App servers in Germany (EU)
- Cancel anytime
30 days for PLN 0 · first payment after the trial · cancel anytime
See pricing after the trial