Find the answer and move on.

Prepare a list of your domains, your store platform, the advertising and marketing tools you use, and the questions you want answered. You share access with our team through an agreed channel. We configure the connections, and then we check the first visit and order together.

Open the Dashboard, the summary screen. Set a completed period and read visitors, orders and revenue. Pick one change to investigate, then move on to products, sources or the purchase funnel.

In the funnel, compare consecutive steps, such as product view, cart and purchase. Check both the number of transitions and the share of people who move on. Then compare phones and computers to narrow down where to look.

In Alerts and reports, choose an alert, a metric and a threshold. Set how often to check and the pause between consecutive notifications. Before turning it on, check the recipient and the mail connection. An alert is a signal to open the report and look for the cause.

Yes. A report schedule lets you set up regular delivery, such as a weekly summary. An alert works differently: it tells you when a chosen condition is met. You can use both, so you don't have to open the dashboard just to check whether something has changed.

Choose “Try free for 30 days” and fill in the order form. We'll agree on the connections and access needed, and our team will take care of configuring Flowpeek.

No. We set it up within 48 hours. We configure tracking and integrations and check the data. You get a ready-to-use dashboard.

Yes. Start includes a consultation in the first month. Growth includes 1 hour with an analytics consultant every month. We help you put Flowpeek to work in your store. It's worth preparing two or three questions, for example about order sources, cart abandonment or interest in products.

On-site tracking collects visitor behavior. Orders, campaign costs and marketing actions also rely on the relevant integrations. We select and configure them as part of the setup.

Your subscription is calculated automatically from the number of orders and domains, during the trial and in every following period. The dashboard shows the plan you will move to after the trial: Start costs PLN 589 net per month, Growth PLN 889 net, and Scale (above 3,000 orders or 3 domains) from PLN 1,689 net. The scope also depends on the number of domains: Start covers one, Growth up to three, Scale more. The pricing page helps you estimate the cost before you start.

Yes, if they run on separate domains. Start covers one store or domain. Growth lets you connect up to three stores or domains, including language versions. If you run more than three domains, we'll agree on the setup scope individually.

Growth covers up to three stores or domains, technical support and one hour with an analytics consultant every month. You can use it to read your reports, assess a problem in the purchase process or choose your team's next step. Start includes a consultation in the first month.

You submit requests in the help panel. We handle them by priority. The 48-hour deadline applies to resolving the request. Describe the problem, point to the report or screen and give the period it concerns, so the team can start investigating right away.

Cancel in the Flowpeek dashboard before the next renewal. You can do this at any time: you keep access until the end of the current period, and the next fee will not be charged. Cancelling before the free trial ends prevents the paid period from starting. Simply logging out or removing Flowpeek tracking from your store's website does not end the subscription.

Yes, for 30 days. After the subscription expires, the dashboard is blocked, and the “Recover dashboard” button starts a new subscription and restores access with your full history. After 30 days, the dashboard and data are deleted; we keep a copy of the database for another 30 days so we can restore the dashboard at your request, and then delete it permanently. Cancelling the renewal leaves you access until the end of the current period.

The store may send an order without a link to a recorded visit. In that case, the source stays unassigned. When verifying tracking, we check visit identifiers and the scope of the integration.

Tools may use different dates, definitions of a sale, rules for attributing sales to ads and lengths of analyzed history. Start by comparing the same period and the way orders are attributed.

Order value and payment status are separate pieces of information. Check the report definition and the statuses passed on by the store integration.

ROAS compares attributed revenue with ad spend. To assess profit, you also need the cost of goods, returns and running the store.

Flowpeek calculates the numbers from the available reports. The AI model explains the results it receives. Next to each answer you'll find the sources, so you can check the period and the data.

Flowask helps you analyze data and choose the next step. Changes to campaigns, budgets and store settings remain with your team.

It means 71 points on a relative 0–100 scale. The score lets you compare signals of interest across visitors. On the Flowpredict page you'll see a real profile scored 71, with its visits, cart and trait radar. The score is not a percentage probability of purchase.

New interactions add context about behavior. The next time the model recalculates, the score may rise, fall or stay the same. Flowpredict doesn't add a fixed number of points for each click. Read the score together with the visit history and the purchase stage.

It's the result of testing a specific model and depends on its sample and evaluation method. A balanced test has different proportions of buyers and non-buyers than your store traffic. So assess the result together with the test information, and check how the model works on your own data.

Identifying a person and their consent are separate pieces of information. A marketing action requires the appropriate consent, a linked contact and an action supported by the connected platform.

A customer record retrieved through the API doesn't recreate earlier history on its own. It needs a link to a visit, and whether that's available depends on the platform and the integration method.

A scenario can start with an event, such as a cart or a purchase, a Flowpredict score, an engagement level, interest in a product or a period without a visit. In the builder, you choose the signal and its conditions.

Yes. You can combine a view of a selected product list or category with a Flowpredict threshold and a check of whether the customer has already purchased. Adding to cart doesn't have to start the scenario. A contact who meets the conditions can receive a tag in the connected marketing platform. The action requires an identified person, a linked contact and the appropriate consent. A high score for an anonymous visitor alone isn't enough to add a tag.

Set up a separate scenario triggered by a purchase that removes the earlier tag. In your marketing platform, use the tag removal or the purchase information to end pre-purchase messaging. A drop in the ML score alone doesn't automatically remove the tag — you need a dedicated rule.

Flowpeek can run a supported action in the connected marketing platform, such as adding a tag or changing a contact field. You then use that information in your own tool. Syncing a segment to an ad system, if needed, requires a separate connection and configuration on that system's side.

In the ready-made template, adding to cart starts a 3-hour wait. The scenario then checks for a purchase in the last 24 hours and picks the right branch. For GetResponse, it can add a tag and change the contact's points (scoring). You can adjust the timing and conditions.

No. Flowpredict calculates a relative intent score from 0 to 100. Scoring means the contact's points in the marketing platform. A scenario can use a Flowpredict threshold to add points to the scoring, but these values describe different things.

Flowpeek passes actions to the connected tool, such as a tag, a field, an event or list membership. Any further sending depends on the scenario set up in that platform.

GetResponse, Klaviyo, MailerLite, ActiveCampaign, Ecomail and ExpertSender ECDP. The blocks match the capabilities of each specific connection. Edrone works separately, as a sync of subscribers and consent changes.

You can choose interactions with a specific category as a condition or the start of a scenario and combine them with a Flowpredict threshold. A dynamic tag or field passes the topic of interest to GetResponse. In the template, the top_category value comes from the most frequent category and brand pair in recorded interactions from the last 30 days; it isn't the total of all views of a given category.

You decide whether entry is one-time, repeated after a break, or repeated each time the condition is met again. The same visitor never has parallel runs of the same scenario.

The history shows executed actions, condition results, skips and errors. Before every action, the system checks the contact link and current consent again.