Skip to content
flowpeek
flowpeek
Try free for 30 daysBook a demo(30 minutes online, opens in a new tab)

30 days for PLN 0 · first payment after the trial · cancel anytime

Automations

Start marketing before the customer adds a product to the cart.

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.

30 days for PLN 0 · first payment after the trial · cancel anytime. We set it up for you within 48 hours.

Use case · before the cart

Browsing the product list

Comes back to the offer. Compares. Hasn't added anything to the cart yet.

FlowpredictHigh intent score

The model scores the available behavior. The cart is one of the signals — not a condition for entering this scenario.

A tag for the identified contact

high_intent_before_cart

A segment for follow-up messaging in your marketing platform.

More remarketing options

The cart isn't the first buying signal.

Someone can browse your product list carefully, keep coming back to the store and still have an empty cart. Flowpeek lets you use a score of that interest to pick the contacts worth helping toward the next step.

It's an extra signal for marketing: behavior + model score + contact context. Your current tool still runs the messaging.

  1. 01 · Behavior

    The customer browses the offer

    Product lists, further page views and return visits build a history of interest. You don't have to wait for an add-to-cart event.

  2. 02 · Flowpredict

    The model ranks intent

    A 0–100 score helps you pick out the stronger signals. Open the journey and see what's behind a specific person's score.

  3. 03 · Automations

    The contact gets tagged

    Combine a score threshold with the scenario's conditions. An identified contact with the right consent gets a tag, a field or another supported action.

  4. 04 · Your platform

    You follow up with a relevant message

    Use the segment in your messaging: help them choose a product, remind them of a collection or clear up doubts before they buy.

You stay in control of who's in the group and what the message is. Your own threshold, a purchase check and re-entry rules let you fit the scenario to your store.

Explore Flowpredict

The Flowpredict score is a relative intent score, not a percentage chance of purchase. Flowpeek passes supported actions to the connected platform; you set up campaigns and any audience sync to an ad platform in your own tools.

Automations in practice

Intent starts the scenario.
The tag goes to marketing.

Go from a product list to a segment of high-intent contacts. See how to combine the Flowpredict score with behavior and a GetResponse action.

Intent you can see before the cart

They're browsing a collection. Give that interest a next step.

A product list view starts the scenario. Flowpeek checks the model score, then whether no cart or purchase has been recorded within the chosen time. Only then does it tag the identified contact in GetResponse.

Start
View of a selected category
Flowpredict score
At least 70 / 100
Cart and purchase
None recorded within 7 days

What you gain

You build a re-engagement group that also includes people who stopped at browsing your offer. Adding to cart is no longer the only criterion.

An example configuration. You match the address fragment to the list in your store, and the threshold and time windows to your strategy. 70 / 100 is a point score, not a 70% chance of purchase.

Before the cartGetResponse scenario

Running it requires a match to a contact and current marketing consent.

Store signal

Product list view

Pageview event, address contains /kolekcja/

Condition

Flowpredict score ≥ 70?

The path continues only for the YES answer

70 / 100

Condition

Was an add-to-cart recorded?

Product interest: any product, add to cart, minimum 1, last 7 days. Continue on: NO.

Condition

Was a purchase recorded?

7-day window. The NO branch continues.

GetResponse action

Tag the contact in GetResponse

A tag to use in segments and messaging

high_intent_before_cart

What the run history shows

  • Passing the ML, cart and purchase conditions
  • Result of sending the tag to the identified contact

Action completed, skipped or failed — together with details of how it ran.

Control over every step

Scenarios do the work.
You set the rules.

Build a contact's path from triggers, conditions and actions. You can connect up to 60 blocks in one scenario.

Draft first. Then activate.

Edit the scenario and publish it when it's ready. Before it runs, Flowpeek checks the block connections, the configuration and whether the selected actions are available.

You set the re-entry rules.

Run the scenario once per visitor, again after a break or each time the conditions are met. The same visitor never goes through it twice at the same time.

A pace that fits the journey.

Add a wait in minutes, hours or days — up to 90 days. Conditions let you split the path into YES and NO answers.

You see what happened.

Review condition results, completed actions, skips and errors. If needed, pause the whole scenario without deleting its definition.

Your tools, connected

Flowpeek passes on the signal.
Your marketing takes the next step.

The available blocks match what the connected platform can do. Sending messages stays with your marketing tool.

GetResponse
Adding and removing tags, fields, scoring, adding to or moving between campaigns.
Klaviyo
Profile properties, adding to a list and events that can trigger flows in Klaviyo.
MailerLite
Adding to and removing from groups and updating contact fields.
ActiveCampaign
Adding and removing tags, updating fields and adding to a list.
Ecomail
Adding tags and subscribing contacts to a list.
ExpertSender ECDP
Updating customer attributes that you use to build segments and scenarios in ECDP.

edroneUsing edrone? A separate integration syncs subscribers who give marketing consent at purchase, as well as consent withdrawals. It doesn't add blocks to this builder.

Explore integrations

Automation with purchase context

Already bought?
Change the next message.

On this profile you see three visits, 22 page views and a purchase of PLN 669. This is the moment when reminders about an unfinished decision stop being relevant.

Set up a separate scenario: purchase → remove the intent tag. The connected marketing platform can use this change to end pre-purchase messaging and start the right customer care.

Flowpeek customer profile after a purchase: 3 visits, 22 page views, one order worth PLN 669 and the status Purchase completed
App view after a purchase · 3 visits, 22 page views and a PLN 669 order. The app shows the customer status instead of an intent score. Identifying data is hidden.

Removing the tag requires a configured automation. The screenshot shows the purchase and the customer status, not confirmation that a specific scenario ran.

Back to scenarios

From report to decision

See more.
Choose your next step.

  • Respond to intent even before the cart
  • Combine prediction with the offer and behavior
  • Pass context on to your marketing
01

An earlier moment to respond

A view of a product listing can start a scenario. Check the Flowpredict score and act on the interest before the contact gets as far as adding a product to the cart.

02

Topic and level of interest

Combine the page, category, brand or product being viewed with a prediction threshold. Prepare tags that show what the interest is about and how strong the signals behind it are.

03

More context in your existing database

In the connected tool, you can add a tag, update data or change the contact's score. That score is separate from the Flowpredict score. Use the tags to choose an audience and prepare your communication.

04

Control over timing and the next step

Add a wait, a purchase check or a re-evaluation of a condition. The run history and re-entry rules help keep the scenario in order.

01

marketing before the cart

Act on interest while the customer is still choosing.

Product listings, repeat visits and returns to an offer give signals your marketing can use. Combine them with the Flowpredict score and prepare a rule for recognized contacts. That way, communication doesn't have to wait for an abandoned cart to begin.

  • A listing or category view as a trigger
  • A prediction threshold as the condition for the next step
  • A tag or field to use in follow-up communication
02

from report to scenario

Start with high interest that has no recorded purchase.

In the Top users report, check high Flowpredict scores and open the journeys. Find the behavior you want to use in marketing: browsing a listing, repeated views of an offer or returning to a brand. Then recreate that condition in a scenario for contacts who are recognized and eligible for action.

  • Prediction points to visits worth a closer look
  • The journey shows the topic and course of interest
  • The automation passes the chosen signal on to the contact
03

intent and topic

Prepare a group based on what the customer is interested in.

Someone comparing a particular category needs a different topic than someone returning to a specific product. Choose a page URL or an interest condition from the catalog, add an ML threshold and pass the right tag on to your platform.

  • Listing pages recognized by URL
  • Category, brand or product from observed interactions
  • ML conditions combined with activity in a selected period
04

actions in your tools

Deliver intent where you run your communication.

Choose an action available in the connected tool: adding a tag, changing data or a score, adding to a list or passing on an event. Use it to choose audiences and trigger further rules. Your team prepares the content of the communication.

  • GetResponse: tags, fields, contact scoring and campaigns
  • Klaviyo: profile properties, lists and events
  • MailerLite: groups and fields
  • ActiveCampaign, Ecomail and ExpertSender: scope in line with the integration
05

different next steps

Split the scenario by the contact's situation.

YES and NO conditions let you prepare different actions for different levels of interest. You can wait, check for a purchase within a chosen window and re-read a condition before an action. Abandoned cart remains one of the available scenarios, alongside actions triggered much earlier.

  • ML and engagement thresholds
  • Purchase and offer interest conditions
  • Traffic source and device type
  • Waits in minutes, hours or days
06

keeping things under control

See the tag in your platform and the run in the history.

Prepare a draft, check it and publish it. The history covers executed conditions and actions, skips and errors. Re-entry rules control returns, and checking the contact and consent before every action takes into account changes that happen during a wait.

  • Draft and validation before publishing
  • Single entry or re-entry according to a rule
  • No parallel runs for the same visitor
  • Visible executions, skips and errors

Getting started

Start with your own store.

Go from setup to a specific question. During the trial, you'll see how this module helps in your day-to-day work.

  1. 01

    Choose the signal and intent

    Start with a listing view, interest in an offer or a Flowpredict score. Add a threshold and conditions that match your goal.

  2. 02

    Pass on the contact's tag

    Choose to add a tag, fill in a field, change the score or another available action. Set the wait time and when a visitor can start the scenario again.

  3. 03

    Use the group and check how it runs

    Prepare follow-up communication in your marketing platform. Check the Flowpeek history, the result of the action and the audience's later behavior.

In your daily work

From question to action.

Viewing a listing. High intent. No cart yet.

A recognized contact visits the “Dresses” category.

The scenario responds to its URL, checks the Flowpredict threshold and adds an interest tag in the connected platform.

What you gain

You have a group for follow-up communication about this offer while the customer is still choosing a product.

Returning to a brand. Tailor the topic of the next message.

A contact views products from a selected brand several times.

Set the window, the number of interactions and an ML condition, then pass on a tag or field available in the integration.

What you gain

You use recognized interest in a specific offer in segmentation and a win-back scenario.

Same topic. Different level of interest.

You split contacts interested in a category by their Flowpredict score.

Each branch adds a different tag, which the next process in your marketing platform uses.

What you gain

You can plan different next steps for audiences showing different strengths of interest.

Your plan for the first 30 days

Check the value.
On your own data.

Prepare a group for follow-up communication based on interest and prediction before the cart.

  1. 01

    Connect your store and platform

    We set up Flowpeek within 48 hours. We configure tracking and the connections needed for the chosen use case.

  2. 02

    Choose a signal before the cart

    Review the Flowpredict score and journeys. Decide on the product listing, category or behavior you want to respond to.

  3. 03

    Build the rule and the tag

    In the consultation, we'll go through the trigger, the ML condition, the action, any wait and the rules for re-entering the scenario.

  4. 04

    Check the finished group

    Verify the history and the tag or field in your platform. Prepare follow-up communication and a way to assess its results.

How will you know it's worth it?

You have a tested flow from behavior and prediction to a contact tag you can put to work in your marketing.

Try free for 30 days

Questions and answers

Good to know before you start.

We already have GetResponse or Klaviyo. What does Flowpeek add?

Flowpeek provides information about behavior in your store and the interest score from Flowpredict. You combine them into rules, e.g. returning to a product and a score above a chosen threshold. The tags go to your tool, where they'll help you choose an audience for follow-up communication.

Can I follow up with an offer to someone who only viewed a product listing?

Yes, if the visit was recorded, is linked to a contact with the right consent and meets the conditions you set. Visiting the listing URL can start the scenario; that's its trigger. You can then check the Flowpredict score and tag the contact. An earlier add-to-cart isn't required.

Will a scenario recognize interest in a category or brand?

You can use a view of a specific page URL or a separate product interest condition. The latter is based on recorded interactions with products and their catalog data, with a chosen window and number of events. A listing view alone doesn't mean every product shown on it was viewed.

Which platforms does the builder work with?

Actions are available for GetResponse, Klaviyo, MailerLite, ActiveCampaign, Ecomail and ExpertSender ECDP, within the scope of each integration. edrone has a separate sync for subscribers and consent withdrawals; it doesn't provide blocks in this builder.

Does Flowpeek send messages and create Meta audiences on its own?

Flowpeek performs the actions made available by the connected platform, e.g. adding a tag or updating a field. You configure the content, sending and any further ad connections on the platform's side. Creating Meta audiences directly is not a feature of this builder.

Can I tag an anonymous visitor?

Tagging or updating data requires a recognized contact linked to the visit and current consent. The system checks both when admitting a contact to a scenario and before every action. An anonymous visit's score can still be used to analyze behavior.

Do I need code, and can a contact re-enter a scenario?

You put scenarios together from ready-made blocks in a visual builder. You choose single entry, re-entry after a break or entry each time the condition is met again. The same visitor never has parallel runs within one scenario.

Where should I start the 30-day trial?

With one group: e.g. recognized contacts viewing a selected category and meeting a Flowpredict threshold. We set up Flowpeek within 48 hours, and in the consultation during your first month we help you choose the condition, the action and how to check the process.

From description to practice

See how to use it in your store.

30 days on your own data

Work with your own store's data for 30 days.

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.

  • No fixed-term contract
  • We set everything up for you in 48 h
  • App servers in Germany (EU)
  • Cancel anytime