Customer data & marketing automation
FlowStack
Co-founder & CTO
FlowStack brings customer data together so marketers can build useful segments and automate relevant messages.
Visit FlowStackA worked example
An invitation is only the beginning.
Imagine a business running photography workshops. A new session is open for booking. The aim is to invite interested people, then send one reminder to those who still need it.
Fictional people and workshop data. This is an interactive explanation of a possible setup, not a live FlowStack account or a product screenshot.
01 / The data
Bring the relevant facts onto the profile.
The signup form supplies an interest and email permission. The booking system supplies whether someone has booked this particular workshop. An integration maps that information into the customer data used by FlowStack.
| Person | Interest | Email permission | This workshop |
|---|---|---|---|
| Maja | Photography | Allowed | Not booked |
| Noah | Photography | Not allowed | Not booked |
| Lea | Photography | Allowed | Booked |
These fields belong to the example’s data model. A booking for another workshop would not count as a booking for this one.
02 / The audience
Make the selection rules explicit.
The invitation audience must meet all three conditions:
- Interest includes photography.
- Email permission is allowed.
- No booking for this workshop.
Maja matches all three. Noah has the right interest, but no email permission. Lea has already booked. The invitation goes to Maja.
03 / The journey
Give the flow a decision to make.
Use the segment for entry, send the invitation and wait three days. Before the reminder, check whether the person still meets the same rules.
Segment entry
A matching profile enters the flow.
Send invitation
Maja receives the workshop message.
Wait three days
Leave time for her to decide or book.
Check again
Use the current data to choose the next branch.
Maja’s data at the check
- Email permission
- Allowed
- This workshop
- Not booked
Send one reminder
Her interest, permission and booking status still match. The reminder branch can continue.
Enable JavaScript to try the other situations. The example currently shows the unchanged profile.
This control changes only the fictional example on this page. It does not run a flow, send email or connect to customer data.
The decisions behind the example
The details change what someone receives.
Which booking matters?
A general “has booked something” field would exclude people who attended a different workshop. I would model the booking against the specific session, so the audience can answer the question we actually care about.
When should the rule be checked?
A person can book or withdraw permission during a delay. I put a fresh decision before the reminder, so the next action uses the data available at that point. The earlier invitation has already happened; the new decision governs what happens next. The three-day pause is an example campaign choice; I would set the timing around the actual booking deadline.
How does the new information get there?
FlowStack can only evaluate the data it has. If a booking update arrives after the decision, that decision cannot take it into account. Choosing the source for each field and making updates reliable is part of the integration.
A company I’m building.
I’m co-founder and CTO of FlowStack, and I’m actively involved in the company and its technical development. Bringing data, APIs and marketing workflows together is a substantial part of my work. The interesting challenge is making that flexibility useful to the person building a segment or a flow.
Explore FlowStack and its features