Orders, sessions, subscription state and support history are joined into one profile per customer, and flows fire off that profile: the second order that never came, the renewal landing after a bad support month, the cart holding an item that just came back into stock. Every flow ships with a holdout group, so what you read at the end of the month is incremental revenue rather than revenue that would have arrived anyway.
The calendar decides when a customer hears from you, not the customer. Someone abandons a cart on Monday and gets Thursday’s newsletter — the same one everybody else gets.
It has opens, clicks and an email address. It does not know about the two failed deliveries, the open ticket or the plan downgrade last week — so the win-back arrives the day after a complaint.
Attributed revenue is mostly revenue that would have come anyway. Without a holdout the flow looks like it works, the budget follows it, and no one finds out for a year.
We pull orders, product or app usage, subscription state, delivery events and support history into one profile per person. This is the unglamorous half of the project and it is where the personalisation actually comes from.
Not thirty flows — six or eight moments where a message changes the outcome: the missing second order, the pre-renewal risk window, the back-in-stock item, the stalled onboarding, the quiet high-value account.
Each moment gets copy per segment, generated from the profile and reviewed by your team before it goes live. Tone, claims and offers follow rules you set, because a discount offered to the wrong cohort costs more than the email earns.
A share of each audience deliberately gets nothing. The difference between the two groups is the flow’s real contribution, and it is the number we report.
Flows that do not beat their holdout get cut or rewritten. Fatigue rules cap how much any one customer receives, so retention does not quietly become a deliverability problem.
We build in your stack rather than moving you onto ours. The list below is what this solution most often connects to — other systems are a scoping question, not a blocker.
No. We build against the one you have — Klaviyo, HubSpot, Customer.io, most others. What changes is what the ESP knows about each person and what triggers a send.
We use cookies for analytics — to see which pages bring enquiries. Nothing else, and nothing before you agree. Cookie Policy