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.
Flowprofile
A card for each recognized customer: visits, purchases and consents in one place. Check the context before you choose an audience or plan your communication.
30 days for PLN 0 · first payment after the trial · cancel anytime. We set it up for you within 48 hours.
Customer profile
Identified via: store integration
Linked sessions
4
Last purchase
PLN 249
Interest
Product A, fall collection
Latest activity
Viewing a product
Marketing consent
Checked separately
From report to decision
Find a profile, check its source and go to the details. You can also open the card from a linked visit or journey.
Combine information about a person with their behavior wherever the integration has provided the right identifiers. A profile from an account or newsletter sign-up may appear even before the first order.
Supported store connections can pass on data from customer accounts or newsletter sign-ups. In WooCommerce, a customer can also be recognized after logging in or using a supported form.
Keep information about recognizing a person separate from permission to send marketing communication. Assess which actions are backed by the available data.
value in everyday work
Scattered information makes it harder to prepare a well-targeted communication scenario. The profile organizes the recognition source, history and consents, so your team can go straight to the question of what to do next.
customer context
The profile list leads to the source of a person's recognition and their linked history. Instead of piecing context together from separate places, you start from one customer card.
recognition before purchase
A store account, a newsletter sign-up or a supported form can provide data for recognition. The scope depends on the platform; during setup, we check what information and links your store passes on.
preparing for communication
Knowing a customer and being allowed to send them marketing are two different things. The profile card helps you read the available context and choose a scenario in the connected tool with consents taken into account.
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
We check which customer data, events and consents your platform makes available.
02
Find a recognized person on the list or go to them from a linked visit.
03
Read the available context and the consent status. Use them when planning supported marketing scenarios.
In your daily work
CRM specialist
Open Flowprofile and check the available links to their visit history.
What you gain
You prepare communication based on the customer context you've collected.
Marketing automation specialist
Check recognition, the contact link and the consent status before launching it.
What you gain
You can verify whether the planned action has the right recipient and a basis for running it.
E-commerce manager
Check the recognition source and the scope of the integration.
What you gain
You understand what data the platform provides and where an additional link is needed.
CRM team
Open sample profiles and check which behaviors and consents actually help describe the audience.
What you gain
The automation brief is based on specific customer context and communication conditions.
Your plan for the first 30 days
Prepare a communication scenario based on a recognized customer's context.
Within 48 hours we set up Flowpeek and the store platform integration. We check how customers get recognized.
Go from the list or a linked visit to the card. See information about the person, their history and consents.
In the consultation, we'll discuss which behavior or data will be useful in the communication you're planning.
Prepare a scenario definition and an action that can be carried out in the connected marketing tool.
You can describe the audience, their context and a sensible next step in communication.
Questions and answers
Recognition requires data from an integration or another supported link. An anonymous visit doesn't automatically mean you know the customer.
Simply pulling customer data from the store doesn't link it to earlier anonymous visits. A confirmed link is needed, e.g. recognizing the customer during a visit or through a supported form.
It differs in how recognition works, the history available and the consent data. That's why we check the scope for your specific platform before launching a scenario.
You can start from the list of profiles. The linked card is also available for a recognized person in the traffic, visitors and user journey views.
No. A customer record identifies a person, while consent describes a specific purpose of communication. Before taking action, check the current consent status and what the integration supports.
Flowprofile collects the available information from the store and recorded visits. It isn't meant for running a sales process manually. It helps you check a recognized customer's history before planning marketing activities.
It helps connect recognizing a person with the context of their visits and purchases, wherever a confirmed link is available. That way a scenario can take into account behavior in the store, not just being on a list.
Start a 30-day trial. We'll check the scope of data from your platform, set up the connection and show you how to use the available profiles.
From description to practice
Advanced · 8 min read
Combine the intent score with an identified contact and tagging. Plan the conditions, re-entry and how communication ends after a purchase.
Read the guideAdvanced · 14 min read
Set up the event, the delay and contact tagging. Tell pre-cart intent apart, test both branches and remove the earlier tag after a purchase.
Read the guideAdvanced · 10 min read
Check customer identification, the link to a visit and whether consent is current. See how to test Flowprofile and actions triggered after a delay.
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
Flowpredict scores every visitor's interest in buying on a scale of 0–100. Find people with a high score before they add a product to the cart, and pass them on to marketing automation.
Combine the Flowpredict score with the offer being viewed and the visit history. Automatically tag recognized contacts who have the right consent in your marketing tool, even before they add a product to the cart.
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.
