Your first 30 days with Flowpeek: from setup to decisions

1. Pick a question that has a decision behind it.

"I want analytics" is a broad goal. "I want to know whether the drop in sales starts in advertising or in the cart" immediately points to the reports and the expected outcome. Pick one topic: acquiring traffic, getting to purchase, product performance or using customer behavior in your communication.

Write down who will make the decision and what they need. The owner may need a picture of sales, the ads specialist a comparison of sources and costs, and the person running the store pointers to what to check. A shared question makes it easier to get started without opening every module at once. Note other topics for later; they don't have to hold up the first useful review.

2. Hand the configuration over to our team.

The "Try free for 30 days" button takes you to the order form. Next, we agree on your store platform, the tools you use and the scope of the setup. We get Flowpeek running within 48 hours. We configure tracking and the agreed connections for you, so you can start working in a ready-made dashboard.

Prepare information about your domain, e-commerce platform, ad accounts, messaging tool and the person responsible for the store. Share access through the agreed channel, not in a note with your business questions. Together we'll choose whether it runs on your domain or a Flowpeek domain. The scope of a specific integration matters more than its logo appearing on a list.

3. Get to know three types of data.

Browser tracking describes recorded behavior: visits, page views and interactions. The store platform integration supplies the available sales and catalog records. A connection to an ad tool can add costs. These streams answer different questions and don't always show up in the dashboard at the same time.

Once it's live, you start building a history of new behavior. An order import, if the integration offers one, doesn't recreate earlier page views or clicks. Write down the date tracking started and the date of the first successful sync. That way you won't mistake a short history for a lack of customer interest. Also check the messages about incomplete data, currency and unrecognized products.

Start the first acceptance check with the tile descriptions, not just the big numbers. In the main dashboard shown, the summary covers the last 30 days, and the real-time traffic covers the last hour. The orders tile notes that canceled and failed orders are excluded, while the revenue tile mentions returns and cancellations. Write down these definitions along with the tracking start date; only then compare the result with your store's admin panel.

4. In the first few days, check the basic cases.

Open the store and go through a normal journey: landing, product, cart and checkout. Depending on the agreed test method, use a controlled purchase or an existing order. Check that the observations relate to the right store and that the product is recognized. Don't make lots of artificial purchases just to fill the chart.

Pay attention to what the report actually measures. A product view, an add-to-cart and an order are separate events; product units aren't the number of transactions. Compare a few orders with the store, taking status and currency into account. If ad cost isn't available, flag it before evaluating ROAS. A short check like this gives you a more solid basis for later analyses.

In the breakdown shown, phones (mobile) have 5,339 views and 157 purchases, and computers (desktop) have 386 views and 14 purchases. The purchase rate is higher on desktop, but traffic is much lower. That's why it's worth doing your first test purchase on the device most of your visitors use. Check that the steps are recorded and how smooth the process is; a difference in percentages alone won't prove a fault.

5. After each review, pick one thing to check.

In the first week, pick the main dashboard and two reports related to your goal. For a checkout problem, that's the funnel and the journeys. For a marketing question — sources and costs. Use the same completed period and note important changes in the store: a promotion, an unavailable product, a shipping change or a new landing page.

Don't judge an effect just because the chart moved. With little traffic, a single purchase can noticeably change percentages. Look at absolute numbers too. Instead of rebuilding the whole cart right away, note the observation and check a few journeys. If the question is broader, Flowask can help you talk through the available report, and the source of the answer lets you verify the numbers.

6. Come to the consultation with three examples.

In your first month you get a consultation in which we help you use Flowpeek in your store. Prepare a question, a screenshot or report name and whatever seems unclear. "I don't know why the channels add up differently" is a good start; it's even better to include the date range and a few orders to compare.

A good outcome of the meeting is agreed definitions, the next report chosen and a plan for one action. If you're interested in automations, describe the customer's situation, when it should trigger and the expected action in the connected platform. Together we'll also agree on how to check the execution history. Publishing a scenario isn't the end of the work — it's worth confirming that the right recipient goes through it and the right condition applies.

• One question about sources or acquisition costs.
• One example concerning a product, the cart or a journey.
• One idea for an action to evaluate in the next period.

7. Wrap up the trial based on usefulness.

Before the 30 days are up, go back to your opening question. Check whether you can answer it faster, whether you know the data scope and whether the team has agreed on the next action. These are more concrete criteria than the number of screens opened. No clear sales growth over a short period doesn't invalidate a correct diagnosis, just as growth on its own doesn't prove the tool works.

You start with 30 days for PLN 0. Your plan is set automatically based on the number of orders and domains, during the trial and in every following period, and the dashboard shows which subscription you'll move to after the trial. Start costs PLN 589 net per month and covers 1 store / domain and up to 1,000 orders. Two or three domains require at least Growth; separate domains for language versions count separately. You can cancel in the dashboard at any time: it takes effect at the end of the current period, and the next payment won't be taken. By the end of the trial, you should know your next plan and which reports will become part of your daily work.