Data from your own platform
Reading uses information provided by PrestaShop. The sync fills in the order register and product context.
Flowpeek + PrestaShop
PrestaShop. Store data and customer observations ready for analysis.
Use journeys and the funnel to decide what to improve on the product page or in your PrestaShop theme. We'll connect orders, the catalog and customer data, and check on-site tracking. You start with a question about your store, not with configuring a tool.
Try free for 30 daysBook a demo · 30 min(online meeting, opens in a new tab)See what the connection covers
30 days for PLN 0 · first payment after the trial · cancel anytime. We set everything up for you in 48 hours.
01What your team gains
From store data
to a concrete task.
A specific problem to fix
Journeys and events help you choose the part of your offer or page that deserves your developer's time.
Profiles even before an order
The customer read covers accounts and newsletter sign-ups if the key has access to that resource. Flowprofile organizes the person's identification and the available consent information.
See a report from the app
Which channels bring in new visitors?
It's one of the questions you can start with once site tracking is running. The sources report shows your traffic mix along with new and returning users.
- 1Compare the share of new and returning visitors across your main sources.
- 2Pick a channel worth a closer look and check what visitors do after they land.
- 3Prepare a question for your next analysis: about the ad, the landing page or the offer copy.
02Integration scope
What does
PrestaShop send?
See what information reaches Flowpeek and how you can use it. The connection scope is part of the setup plan.
- Order import
- Reading order status and its updates via the Webservice API. Amounts and currencies come from the data provided by the store.
- Catalog
- Products and combination identifiers used as variants. The import doesn't automatically cover categories or the descriptive labels of all combinations.
- Customers and subscribers
- A separate read of the customer resource feeds Flowprofile and the available newsletter status. It requires permission to read customers in the Webservice API. The import alone doesn't link earlier anonymous visit history.
- Updates and tracking
- Store data refreshes according to the read schedule. The tracker in the theme separately collects recorded on-site behavior.
An order import doesn't replace tracking of confirmed purchases.
The PrestaShop connection retrieves order statuses into the sales register. Reading alone doesn't create a confirmed purchase event or attribution to a visit. A report from the browser alone doesn't confirm that link either. During configuration, we clearly separate analysis of imported sales from observation of visitor behavior.
03In your daily work
What will you bring
to the report?
The best start is a specific question about your store. Pick one of these scenarios and use the trial to prepare your next action.
The product page needs polishing
Check events and journeys on the product page and whether customers move on to the cart.
What you leave the analysis with
You'll prepare a narrow, well-justified layout fix.
Campaign traffic ends visits early
Open the journeys after entry on the promoted page and compare repeated steps.
What you leave the analysis with
You'll separate questions about traffic targeting from questions about page content.
A newsletter sign-up gains visit context
Consent retrieved from PrestaShop and a link between the current visit and the GetResponse contact, e.g. through a click from an e-mail, let you prepare a behavior-based rule. Combine viewing a selected product with a Flowpredict threshold and adding a tag. A profile import doesn't add earlier anonymous visits.
What you leave the analysis with
After testing the rule, you'll verify the tag in GetResponse — the basis for a segment of people interested in the selected product.
From sign-up to working with data
You start the trial.
We handle the setup.
You get 30 days to try Flowpeek in your store. We set up the connection in 48 hours, and in the first month we help you fit the reports into the way you work.
- 01
We check the store configuration
We determine the address, platform version, time zone and the data needed for the first review.
- 02
We connect the Webservice API
We configure the required resources for reading and start the sync. We set up Flowpeek within 48 hours.
- 03
We prepare tracking in the theme
We install the tracker in the right place and go through a test visit. We check order and catalog data separately.
- 04
We start with one question
In the consultation during the first month, we choose a page, offer or behavior that will help you assess how useful Flowpeek is.
04Plan a good trial
One question.
A first useful answer.
During the consultation we'll choose the reports and the criteria for judging the trial. The outcome can be a well-described problem, a hypothesis for a change or a plan for further analysis: something your team can work on.
Start with the setup
What should you prepare, and how do you check the first data?
A list of information for our team plus a check of the first visit and order, step by step.
Open the guideFlowpeek guide
How do you start with a specific question?
Prepare a plan for your first 30 days of working with reports.
Flowpeek guide
Are you comparing the same sales?
Check definitions, dates and data scope in your reports.
Questions and answers
Good to know before you start.
Does the integration require an additional PrestaShop module?
Reading orders and products uses the Webservice API. We place the behavior tracker separately on the site, in a spot suited to your theme and store configuration.
Can the integration edit orders or stock?
The connection is designed for reading. It doesn't manage inventory, documents or order statuses in PrestaShop.
Does data arrive via webhooks?
The current connection uses scheduled API reads. How fresh the sales data is depends on the sync runs, not on instant webhook delivery.
Will a historical import rebuild purchase sources?
No. It fills in order status, but doesn't rebuild missing visit tracking. The connection doesn't create a confirmed conversion or exact attribution from the import.
What's needed to retrieve customers and consents?
The Webservice API key must have permission to read the customer resource. We configure it during setup. This way, accounts and newsletter sign-ups without an order can also reach Flowprofile. Reading doesn't automatically connect earlier anonymous visits with that profile.
What data do you help check at the start?
We go through the configuration of permissions, dates, currencies and reading of products and orders. We also check on-site tracking, and in the first month we help you use it during the consultation.
30 days on your own data
Try Flowpeek in your PrestaShop store.
Start 30 days for PLN 0. We set up Flowpeek in 48 hours and help you use the first month to work on a specific question about your store.
- No fixed-term contract
- We set everything up for you in 48 h
- App servers in Germany (EU)
- Cancel anytime
Try free for 30 daysBook a demo · 30 min(online meeting, opens in a new tab)
30 days for PLN 0 · first payment after the trial · cancel anytime
See pricing after the trial